From mirageos-devel-bounces@lists.xenproject.org Mon Sep 01 07:33:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 01 Sep 2014 07:33: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 1XOM6y-0007MS-5P; Mon, 01 Sep 2014 07:33:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOM6w-0007MN-J8 for mirageos-devel@lists.xenproject.org; Mon, 01 Sep 2014 07:33:10 +0000 Received: from [85.158.139.211:6008] by server-14.bemta-5.messagelabs.com id 98/C8-12422-53124045; Mon, 01 Sep 2014 07:33:09 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1409556788!11610272!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25417 invoked from network); 1 Sep 2014 07:33:08 -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; 1 Sep 2014 07:33:08 -0000 Received: (qmail 10729 invoked by uid 634); 1 Sep 2014 07:33:08 -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 Unknown (HELO [172.25.41.238]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 01 Sep 2014 08:33:07 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 1 Sep 2014 09:33:05 +0200 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] conduit + vchan X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8523427808179644159==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8523427808179644159== Content-Type: multipart/alternative; boundary="Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC" --Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Dave, The conduit merge required quite a few different patches across = repositories, so I've opened up an OPAM remote to track all the branches = required here: https://github.com/mirage/mirage-dev There's a Travis file to check that the overall set of packages are = working. Since it's a sequence of git remotes, we'll need to = occasionally push dummy commits to the mirage-dev repository to trigger = a recompile with the latest sub-repositories. I'm tracking the overall feature in : = https://github.com/mirage/mirage/issues/287 So far, the Conduit API is settling down and works with Lwt_unix, Async = and Mirage, including client DNS lookups and HTTP requests. Before = merging, I'd like to: - add sexp accessor functions - switch to V2 interfaces (required for previous) - get OCaml TLS hooked in Once this is all done, Conduit can be released independently of the rest = of the Mirage libs (which in turn unblocks a Cohttp 1.0 release). I'm = just holding back releasing it too early so that we don't have to keep = revving the Lwt_unix interfaces all the time. Regarding vchan, the biggest difference in the new APIs is that Conduit = creates a V1_FLOW interface that abstracts across all the connection = mechanisms (currently TCPv4 and vchan). Previously in Mirage 1.0, this = was hardcoded to TCPv4, and I've had to modify those interfaces in the = development repository to bring TCPv4 in compliance with the FLOW = interface (it's slightly odd that we didn't do that before!). -anil On 23 Aug 2014, at 00:43, David Scott wrote: > In the last weekly call I agreed to work on conduit + vchan. >=20 > = https://github.com/mirage/mirage-www/pull/219/files#diff-ad18f4983a07ffe4c= 757b33c537226a1R70 >=20 > Looking at the Lwt_unix conduit API >=20 > = https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lwt_unix_conduit.ml >=20 > It seems to be using Lwt_io input/output channels. So my plan is to = implement Lwt_io channels on top of the FLOW exposed by vchan. I've got = a prototype of that here: >=20 > = https://github.com/djs55/ocaml-vchan/blob/improve-lwt/lwt/vchan_lwt_unix.m= l >=20 > Does this general approach seem sensible? Since the conduit code is = quite new and under heavy development I thought I'd better ask :-) >=20 > A side-benefit is that Lwt_unix apps which use vchan can decide to use = either the Mirage FLOW interface or the Lwt_io interface. >=20 > It looks like the Mirage conduit interface is FLOW based, so I can = expose the existing vchan implementation there. >=20 > Cheers, > --=20 > Dave Scott > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Dave,

The conduit = merge required quite a few different patches across repositories, so = I've opened up an OPAM remote to track all the branches required here: = https://github.com/mirage/mi= rage-dev

There's a Travis file to check = that the overall set of packages are working.  Since it's a = sequence of git remotes, we'll need to occasionally push dummy commits = to the mirage-dev repository to trigger a recompile with the latest = sub-repositories.

I'm tracking the overall = feature in : https://github.com/mi= rage/mirage/issues/287

So far, the Conduit = API is settling down and works with Lwt_unix, Async and Mirage, = including client DNS lookups and HTTP requests.  Before merging, = I'd like to:

- add sexp accessor = functions
- switch to V2 interfaces (required for = previous)
- get OCaml TLS hooked = in

Once this is all done, Conduit can be = released independently of the rest of the Mirage libs (which in turn = unblocks a Cohttp 1.0 release).  I'm just holding back releasing it = too early so that we don't have to keep revving the Lwt_unix interfaces = all the time.

Regarding vchan, the biggest = difference in the new APIs is that Conduit creates a V1_FLOW interface = that abstracts across all the connection mechanisms (currently TCPv4 and = vchan).  Previously in Mirage 1.0, this was hardcoded to TCPv4, and = I've had to modify those interfaces in the development repository to = bring TCPv4 in compliance with the FLOW interface (it's slightly odd = that we didn't do that = before!).

-anil

On 23 Aug = 2014, at 00:43, David Scott <scott.dj@gmail.com> = wrote:

In the last weekly call I agreed to work = on conduit + vchan.


Looking at the Lwt_unix conduit = API

https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lwt_unix_condui= t.ml

It seems to be using Lwt_io input/output channels. = So my plan is to implement Lwt_io channels on top of the FLOW exposed by = vchan. I've got a prototype of that here:


Does this general approach seem sensible? = Since the conduit code is quite new and under heavy development I = thought I'd better ask :-)

A side-benefit is = that Lwt_unix apps which use vchan can decide to use either the Mirage = FLOW interface or the Lwt_io interface.

It looks like the Mirage conduit interface is FLOW = based, so I can expose the existing vchan implementation = there.

Cheers,
--
Dave Scott
_______________________________________________
MirageOS-devel = mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC-- --===============8523427808179644159== 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 --===============8523427808179644159==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 01 07:33:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 01 Sep 2014 07:33: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 1XOM6y-0007MS-5P; Mon, 01 Sep 2014 07:33:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOM6w-0007MN-J8 for mirageos-devel@lists.xenproject.org; Mon, 01 Sep 2014 07:33:10 +0000 Received: from [85.158.139.211:6008] by server-14.bemta-5.messagelabs.com id 98/C8-12422-53124045; Mon, 01 Sep 2014 07:33:09 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-206.messagelabs.com!1409556788!11610272!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25417 invoked from network); 1 Sep 2014 07:33:08 -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; 1 Sep 2014 07:33:08 -0000 Received: (qmail 10729 invoked by uid 634); 1 Sep 2014 07:33:08 -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 Unknown (HELO [172.25.41.238]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 01 Sep 2014 08:33:07 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 1 Sep 2014 09:33:05 +0200 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] conduit + vchan X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8523427808179644159==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8523427808179644159== Content-Type: multipart/alternative; boundary="Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC" --Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Dave, The conduit merge required quite a few different patches across = repositories, so I've opened up an OPAM remote to track all the branches = required here: https://github.com/mirage/mirage-dev There's a Travis file to check that the overall set of packages are = working. Since it's a sequence of git remotes, we'll need to = occasionally push dummy commits to the mirage-dev repository to trigger = a recompile with the latest sub-repositories. I'm tracking the overall feature in : = https://github.com/mirage/mirage/issues/287 So far, the Conduit API is settling down and works with Lwt_unix, Async = and Mirage, including client DNS lookups and HTTP requests. Before = merging, I'd like to: - add sexp accessor functions - switch to V2 interfaces (required for previous) - get OCaml TLS hooked in Once this is all done, Conduit can be released independently of the rest = of the Mirage libs (which in turn unblocks a Cohttp 1.0 release). I'm = just holding back releasing it too early so that we don't have to keep = revving the Lwt_unix interfaces all the time. Regarding vchan, the biggest difference in the new APIs is that Conduit = creates a V1_FLOW interface that abstracts across all the connection = mechanisms (currently TCPv4 and vchan). Previously in Mirage 1.0, this = was hardcoded to TCPv4, and I've had to modify those interfaces in the = development repository to bring TCPv4 in compliance with the FLOW = interface (it's slightly odd that we didn't do that before!). -anil On 23 Aug 2014, at 00:43, David Scott wrote: > In the last weekly call I agreed to work on conduit + vchan. >=20 > = https://github.com/mirage/mirage-www/pull/219/files#diff-ad18f4983a07ffe4c= 757b33c537226a1R70 >=20 > Looking at the Lwt_unix conduit API >=20 > = https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lwt_unix_conduit.ml >=20 > It seems to be using Lwt_io input/output channels. So my plan is to = implement Lwt_io channels on top of the FLOW exposed by vchan. I've got = a prototype of that here: >=20 > = https://github.com/djs55/ocaml-vchan/blob/improve-lwt/lwt/vchan_lwt_unix.m= l >=20 > Does this general approach seem sensible? Since the conduit code is = quite new and under heavy development I thought I'd better ask :-) >=20 > A side-benefit is that Lwt_unix apps which use vchan can decide to use = either the Mirage FLOW interface or the Lwt_io interface. >=20 > It looks like the Mirage conduit interface is FLOW based, so I can = expose the existing vchan implementation there. >=20 > Cheers, > --=20 > Dave Scott > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Dave,

The conduit = merge required quite a few different patches across repositories, so = I've opened up an OPAM remote to track all the branches required here: = https://github.com/mirage/mi= rage-dev

There's a Travis file to check = that the overall set of packages are working.  Since it's a = sequence of git remotes, we'll need to occasionally push dummy commits = to the mirage-dev repository to trigger a recompile with the latest = sub-repositories.

I'm tracking the overall = feature in : https://github.com/mi= rage/mirage/issues/287

So far, the Conduit = API is settling down and works with Lwt_unix, Async and Mirage, = including client DNS lookups and HTTP requests.  Before merging, = I'd like to:

- add sexp accessor = functions
- switch to V2 interfaces (required for = previous)
- get OCaml TLS hooked = in

Once this is all done, Conduit can be = released independently of the rest of the Mirage libs (which in turn = unblocks a Cohttp 1.0 release).  I'm just holding back releasing it = too early so that we don't have to keep revving the Lwt_unix interfaces = all the time.

Regarding vchan, the biggest = difference in the new APIs is that Conduit creates a V1_FLOW interface = that abstracts across all the connection mechanisms (currently TCPv4 and = vchan).  Previously in Mirage 1.0, this was hardcoded to TCPv4, and = I've had to modify those interfaces in the development repository to = bring TCPv4 in compliance with the FLOW interface (it's slightly odd = that we didn't do that = before!).

-anil

On 23 Aug = 2014, at 00:43, David Scott <scott.dj@gmail.com> = wrote:

In the last weekly call I agreed to work = on conduit + vchan.


Looking at the Lwt_unix conduit = API

https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lwt_unix_condui= t.ml

It seems to be using Lwt_io input/output channels. = So my plan is to implement Lwt_io channels on top of the FLOW exposed by = vchan. I've got a prototype of that here:


Does this general approach seem sensible? = Since the conduit code is quite new and under heavy development I = thought I'd better ask :-)

A side-benefit is = that Lwt_unix apps which use vchan can decide to use either the Mirage = FLOW interface or the Lwt_io interface.

It looks like the Mirage conduit interface is FLOW = based, so I can expose the existing vchan implementation = there.

Cheers,
--
Dave Scott
_______________________________________________
MirageOS-devel = mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_0D4462BC-0CF7-41E0-AC6C-64C2D10CC3FC-- --===============8523427808179644159== 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 --===============8523427808179644159==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 01 19:44:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 01 Sep 2014 19:44:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXWP-0006aa-GW; Mon, 01 Sep 2014 19:44:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXWO-0006aV-8q for mirageos-devel@lists.xenproject.org; Mon, 01 Sep 2014 19:44:12 +0000 Received: from [85.158.139.211:57242] by server-17.bemta-5.messagelabs.com id 90/D5-08943-B8CC4045; Mon, 01 Sep 2014 19:44:11 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1409600650!11767812!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27439 invoked from network); 1 Sep 2014 19:44:10 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Sep 2014 19:44:10 -0000 X-IronPort-AV: E=Sophos;i="5.04,444,1406592000"; d="scan'208";a="24429501" From: Dave Scott To: Anil Madhavapeddy Thread-Topic: [MirageOS-devel] conduit + vchan Thread-Index: AQHPvlqGaUV79hNJ/0Ob3/JviDyOYJvrz7OAgADMMAA= Date: Mon, 1 Sep 2014 19:43:58 +0000 Message-ID: <0ADC5AE0-7C36-48D1-8986-2E834DCFA12A@citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <28A1ECE6754F5D42AED7DBED44B40321@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] conduit + vchan X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 1 Sep 2014, at 08:33, Anil Madhavapeddy wrote: > Hi Dave, > = > The conduit merge required quite a few different patches across repositor= ies, so I've opened up an OPAM remote to track all the branches required he= re: https://github.com/mirage/mirage-dev Great, this repo is working for me. I=92ve added the latest, greatest vchan= library=97 I=92d like to get that working with conduit too. > There's a Travis file to check that the overall set of packages are worki= ng. Since it's a sequence of git remotes, we'll need to occasionally push = dummy commits to the mirage-dev repository to trigger a recompile with the = latest sub-repositories. > = > I'm tracking the overall feature in : https://github.com/mirage/mirage/is= sues/287 > = > So far, the Conduit API is settling down and works with Lwt_unix, Async a= nd Mirage, including client DNS lookups and HTTP requests. Before merging,= I'd like to: > = > - add sexp accessor functions > - switch to V2 interfaces (required for previous) > - get OCaml TLS hooked in > = > Once this is all done, Conduit can be released independently of the rest = of the Mirage libs (which in turn unblocks a Cohttp 1.0 release). I'm just= holding back releasing it too early so that we don't have to keep revving = the Lwt_unix interfaces all the time. Sounds good. > Regarding vchan, the biggest difference in the new APIs is that Conduit c= reates a V1_FLOW interface that abstracts across all the connection mechani= sms (currently TCPv4 and vchan). Previously in Mirage 1.0, this was hardco= ded to TCPv4, and I've had to modify those interfaces in the development re= pository to bring TCPv4 in compliance with the FLOW interface (it's slightl= y odd that we didn't do that before!). IIRC we designed the FLOW from scratch and it ended up different to TCPv4. = Since we wanted V1 to remain stable I think it made sense to postpone TCPv4= -as-FLOW to V2. It=92s definitely the right time to fix it now though! That= reminds me, I wanted to make CONSOLE into a superset of FLOW also. Cheers, Dave > = > -anil > = > On 23 Aug 2014, at 00:43, David Scott wrote: > = >> In the last weekly call I agreed to work on conduit + vchan. >> = >> https://github.com/mirage/mirage-www/pull/219/files#diff-ad18f4983a07ffe= 4c757b33c537226a1R70 >> = >> Looking at the Lwt_unix conduit API >> = >> https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lwt_unix_conduit.ml >> = >> It seems to be using Lwt_io input/output channels. So my plan is to impl= ement Lwt_io channels on top of the FLOW exposed by vchan. I've got a proto= type of that here: >> = >> https://github.com/djs55/ocaml-vchan/blob/improve-lwt/lwt/vchan_lwt_unix= .ml >> = >> Does this general approach seem sensible? Since the conduit code is quit= e new and under heavy development I thought I'd better ask :-) >> = >> A side-benefit is that Lwt_unix apps which use vchan can decide to use e= ither the Mirage FLOW interface or the Lwt_io interface. >> = >> It looks like the Mirage conduit interface is FLOW based, so I can expos= e the existing vchan implementation there. >> = >> Cheers, >> -- = >> 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 _______________________________________________ MirageOS-devel 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 Sep 01 19:44:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 01 Sep 2014 19:44:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXWP-0006aa-GW; Mon, 01 Sep 2014 19:44:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXWO-0006aV-8q for mirageos-devel@lists.xenproject.org; Mon, 01 Sep 2014 19:44:12 +0000 Received: from [85.158.139.211:57242] by server-17.bemta-5.messagelabs.com id 90/D5-08943-B8CC4045; Mon, 01 Sep 2014 19:44:11 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1409600650!11767812!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27439 invoked from network); 1 Sep 2014 19:44:10 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Sep 2014 19:44:10 -0000 X-IronPort-AV: E=Sophos;i="5.04,444,1406592000"; d="scan'208";a="24429501" From: Dave Scott To: Anil Madhavapeddy Thread-Topic: [MirageOS-devel] conduit + vchan Thread-Index: AQHPvlqGaUV79hNJ/0Ob3/JviDyOYJvrz7OAgADMMAA= Date: Mon, 1 Sep 2014 19:43:58 +0000 Message-ID: <0ADC5AE0-7C36-48D1-8986-2E834DCFA12A@citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <28A1ECE6754F5D42AED7DBED44B40321@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] conduit + vchan X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 1 Sep 2014, at 08:33, Anil Madhavapeddy wrote: > Hi Dave, > = > The conduit merge required quite a few different patches across repositor= ies, so I've opened up an OPAM remote to track all the branches required he= re: https://github.com/mirage/mirage-dev Great, this repo is working for me. I=92ve added the latest, greatest vchan= library=97 I=92d like to get that working with conduit too. > There's a Travis file to check that the overall set of packages are worki= ng. Since it's a sequence of git remotes, we'll need to occasionally push = dummy commits to the mirage-dev repository to trigger a recompile with the = latest sub-repositories. > = > I'm tracking the overall feature in : https://github.com/mirage/mirage/is= sues/287 > = > So far, the Conduit API is settling down and works with Lwt_unix, Async a= nd Mirage, including client DNS lookups and HTTP requests. Before merging,= I'd like to: > = > - add sexp accessor functions > - switch to V2 interfaces (required for previous) > - get OCaml TLS hooked in > = > Once this is all done, Conduit can be released independently of the rest = of the Mirage libs (which in turn unblocks a Cohttp 1.0 release). I'm just= holding back releasing it too early so that we don't have to keep revving = the Lwt_unix interfaces all the time. Sounds good. > Regarding vchan, the biggest difference in the new APIs is that Conduit c= reates a V1_FLOW interface that abstracts across all the connection mechani= sms (currently TCPv4 and vchan). Previously in Mirage 1.0, this was hardco= ded to TCPv4, and I've had to modify those interfaces in the development re= pository to bring TCPv4 in compliance with the FLOW interface (it's slightl= y odd that we didn't do that before!). IIRC we designed the FLOW from scratch and it ended up different to TCPv4. = Since we wanted V1 to remain stable I think it made sense to postpone TCPv4= -as-FLOW to V2. It=92s definitely the right time to fix it now though! That= reminds me, I wanted to make CONSOLE into a superset of FLOW also. Cheers, Dave > = > -anil > = > On 23 Aug 2014, at 00:43, David Scott wrote: > = >> In the last weekly call I agreed to work on conduit + vchan. >> = >> https://github.com/mirage/mirage-www/pull/219/files#diff-ad18f4983a07ffe= 4c757b33c537226a1R70 >> = >> Looking at the Lwt_unix conduit API >> = >> https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lwt_unix_conduit.ml >> = >> It seems to be using Lwt_io input/output channels. So my plan is to impl= ement Lwt_io channels on top of the FLOW exposed by vchan. I've got a proto= type of that here: >> = >> https://github.com/djs55/ocaml-vchan/blob/improve-lwt/lwt/vchan_lwt_unix= .ml >> = >> Does this general approach seem sensible? Since the conduit code is quit= e new and under heavy development I thought I'd better ask :-) >> = >> A side-benefit is that Lwt_unix apps which use vchan can decide to use e= ither the Mirage FLOW interface or the Lwt_io interface. >> = >> It looks like the Mirage conduit interface is FLOW based, so I can expos= e the existing vchan implementation there. >> = >> Cheers, >> -- = >> 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 _______________________________________________ MirageOS-devel 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 Sep 01 19:52:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 01 Sep 2014 19:52:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXea-0006eY-Ae; Mon, 01 Sep 2014 19:52:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXeY-0006eT-TZ for mirageos-devel@lists.xenproject.org; Mon, 01 Sep 2014 19:52:39 +0000 Received: from [85.158.143.35:30345] by server-1.bemta-4.messagelabs.com id 92/51-05872-68EC4045; Mon, 01 Sep 2014 19:52:38 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1409601157!9497308!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11811 invoked from network); 1 Sep 2014 19:52:37 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Sep 2014 19:52:37 -0000 X-IronPort-AV: E=Sophos;i="5.04,444,1406592000"; d="scan'208";a="24429535" From: Dave Scott To: "mirageos-devel@lists.xenproject.org" Thread-Topic: Mirage weekly call tomorrow (tuesday 2nd sept) 4pm BST (== GMT + 1) Thread-Index: AQHPxh5GsEYwYRbT5UCMZ+RnZY+dAg== Date: Mon, 1 Sep 2014 19:52:35 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Subject: [MirageOS-devel] Mirage weekly call tomorrow (tuesday 2nd sept) 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, Please join the mirage call tomorrow afternoon=97 all are welcome, no prior= experience necessary! If there are items you=92d like to bring up, feel free to propose an agenda= item here: https://github.com/mirage/mirage-www/wiki/Call-Agenda I think some of the team are in Sweden at ICFP, but hopefully they can dial= -in. I=92ve even refreshed the dial-in numbers =97 check out the swedish on= e below... 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Austria: +43 (0) 7 2088 2169 Australia: +61 2 8355 1035 Belgium: +32 (0) 42 68 0154 Canada: +1 (647) 497-9373 Switzerland: +41 (0) 435 0824 39 Germany: +49 (0) 811 8899 6930 Denmark: +45 (0) 89 88 04 29 Spain: +34 911 23 4170 Finland: +358 (0) 931 58 4586 France: +33 (0) 170 950 587 United Kingdom: +44 (0) 20 3657 6778 Ireland: +353 (0) 19 036 185 Italy: +39 0 294 75 15 35 Netherlands: +31 (0) 108 080 114 Norway: +47 21 01 89 06 New Zealand: +64 (0) 9 801 0292 Sweden: +46 (0) 852 500 288 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 01 19:52:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 01 Sep 2014 19:52:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXea-0006eY-Ae; Mon, 01 Sep 2014 19:52:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOXeY-0006eT-TZ for mirageos-devel@lists.xenproject.org; Mon, 01 Sep 2014 19:52:39 +0000 Received: from [85.158.143.35:30345] by server-1.bemta-4.messagelabs.com id 92/51-05872-68EC4045; Mon, 01 Sep 2014 19:52:38 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1409601157!9497308!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11811 invoked from network); 1 Sep 2014 19:52:37 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 1 Sep 2014 19:52:37 -0000 X-IronPort-AV: E=Sophos;i="5.04,444,1406592000"; d="scan'208";a="24429535" From: Dave Scott To: "mirageos-devel@lists.xenproject.org" Thread-Topic: Mirage weekly call tomorrow (tuesday 2nd sept) 4pm BST (== GMT + 1) Thread-Index: AQHPxh5GsEYwYRbT5UCMZ+RnZY+dAg== Date: Mon, 1 Sep 2014 19:52:35 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Subject: [MirageOS-devel] Mirage weekly call tomorrow (tuesday 2nd sept) 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, Please join the mirage call tomorrow afternoon=97 all are welcome, no prior= experience necessary! If there are items you=92d like to bring up, feel free to propose an agenda= item here: https://github.com/mirage/mirage-www/wiki/Call-Agenda I think some of the team are in Sweden at ICFP, but hopefully they can dial= -in. I=92ve even refreshed the dial-in numbers =97 check out the swedish on= e below... 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Austria: +43 (0) 7 2088 2169 Australia: +61 2 8355 1035 Belgium: +32 (0) 42 68 0154 Canada: +1 (647) 497-9373 Switzerland: +41 (0) 435 0824 39 Germany: +49 (0) 811 8899 6930 Denmark: +45 (0) 89 88 04 29 Spain: +34 911 23 4170 Finland: +358 (0) 931 58 4586 France: +33 (0) 170 950 587 United Kingdom: +44 (0) 20 3657 6778 Ireland: +353 (0) 19 036 185 Italy: +39 0 294 75 15 35 Netherlands: +31 (0) 108 080 114 Norway: +47 21 01 89 06 New Zealand: +64 (0) 9 801 0292 Sweden: +46 (0) 852 500 288 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 02 08:02:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 08:02: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 1XOj2b-0006Sq-HP; Tue, 02 Sep 2014 08:02:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOj2a-0006Sl-AO for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 08:02:12 +0000 Received: from [193.109.254.147:8806] by server-3.bemta-14.messagelabs.com id F2/95-23707-38975045; Tue, 02 Sep 2014 08:02:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1409644930!12892024!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6208 invoked from network); 2 Sep 2014 08:02:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-27.messagelabs.com with SMTP; 2 Sep 2014 08:02:10 -0000 Received: (qmail 9172 invoked by uid 634); 2 Sep 2014 08:02:10 -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 Unknown (HELO [172.24.32.65]) (31.15.33.252) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 02 Sep 2014 09:02:09 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <0ADC5AE0-7C36-48D1-8986-2E834DCFA12A@citrix.com> Date: Tue, 2 Sep 2014 10:02:07 +0200 Message-Id: <0F4AB27E-CB2C-4EF0-A30C-766AD87D5F0C@recoil.org> References: <0ADC5AE0-7C36-48D1-8986-2E834DCFA12A@citrix.com> To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] conduit + vchan X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 1 Sep 2014, at 21:43, Dave Scott wrote: > Hi, > = > On 1 Sep 2014, at 08:33, Anil Madhavapeddy wrote: > = >> Hi Dave, >> = >> The conduit merge required quite a few different patches across reposito= ries, so I've opened up an OPAM remote to track all the branches required h= ere:https://github.com/mirage/mirage-dev > = > Great, this repo is working for me. I=92ve added the latest, greatest vch= an library=97 I=92d like to get that working with conduit too. Excellent! I'll cut a minor Cohttp release with some important bugfixes fr= om a branch, so we have time to get this working. If you get a chance to r= eview the Conduit APIs, I'll merge to mirage/master branches rather than ha= ve them on my personal forks. > = >> There's a Travis file to check that the overall set of packages are work= ing. Since it's a sequence of git remotes, we'll need to occasionally push= dummy commits to the mirage-dev repository to trigger a recompile with the= latest sub-repositories. >> = >> I'm tracking the overall feature in : https://github.com/mirage/mirage/i= ssues/287 >> = >> So far, the Conduit API is settling down and works with Lwt_unix, Async = and Mirage, including client DNS lookups and HTTP requests. Before merging= , I'd like to: >> = >> - add sexp accessor functions >> - switch to V2 interfaces (required for previous) >> - get OCaml TLS hooked in >> = >> Once this is all done, Conduit can be released independently of the rest= of the Mirage libs (which in turn unblocks a Cohttp 1.0 release). I'm jus= t holding back releasing it too early so that we don't have to keep revving= the Lwt_unix interfaces all the time. > = > Sounds good. > = >> Regarding vchan, the biggest difference in the new APIs is that Conduit = creates a V1_FLOW interface that abstracts across all the connection mechan= isms (currently TCPv4 and vchan). Previously in Mirage 1.0, this was hardc= oded to TCPv4, and I've had to modify those interfaces in the development r= epository to bring TCPv4 in compliance with the FLOW interface (it's slight= ly odd that we didn't do that before!). > = > IIRC we designed the FLOW from scratch and it ended up different to TCPv4= . Since we wanted V1 to remain stable I think it made sense to postpone TCP= v4-as-FLOW to V2. It=92s definitely the right time to fix it now though! Th= at reminds me, I wanted to make CONSOLE into a superset of FLOW also. This will definitely be V2 I think -- since end points in Conduit are abstr= act, we need the sexp accessors for logging endpoints in a human readable f= ormat. -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 Sep 02 08:02:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 08:02: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 1XOj2b-0006Sq-HP; Tue, 02 Sep 2014 08:02:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOj2a-0006Sl-AO for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 08:02:12 +0000 Received: from [193.109.254.147:8806] by server-3.bemta-14.messagelabs.com id F2/95-23707-38975045; Tue, 02 Sep 2014 08:02:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1409644930!12892024!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6208 invoked from network); 2 Sep 2014 08:02:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-27.messagelabs.com with SMTP; 2 Sep 2014 08:02:10 -0000 Received: (qmail 9172 invoked by uid 634); 2 Sep 2014 08:02:10 -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 Unknown (HELO [172.24.32.65]) (31.15.33.252) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 02 Sep 2014 09:02:09 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <0ADC5AE0-7C36-48D1-8986-2E834DCFA12A@citrix.com> Date: Tue, 2 Sep 2014 10:02:07 +0200 Message-Id: <0F4AB27E-CB2C-4EF0-A30C-766AD87D5F0C@recoil.org> References: <0ADC5AE0-7C36-48D1-8986-2E834DCFA12A@citrix.com> To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] conduit + vchan X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 1 Sep 2014, at 21:43, Dave Scott wrote: > Hi, > = > On 1 Sep 2014, at 08:33, Anil Madhavapeddy wrote: > = >> Hi Dave, >> = >> The conduit merge required quite a few different patches across reposito= ries, so I've opened up an OPAM remote to track all the branches required h= ere:https://github.com/mirage/mirage-dev > = > Great, this repo is working for me. I=92ve added the latest, greatest vch= an library=97 I=92d like to get that working with conduit too. Excellent! I'll cut a minor Cohttp release with some important bugfixes fr= om a branch, so we have time to get this working. If you get a chance to r= eview the Conduit APIs, I'll merge to mirage/master branches rather than ha= ve them on my personal forks. > = >> There's a Travis file to check that the overall set of packages are work= ing. Since it's a sequence of git remotes, we'll need to occasionally push= dummy commits to the mirage-dev repository to trigger a recompile with the= latest sub-repositories. >> = >> I'm tracking the overall feature in : https://github.com/mirage/mirage/i= ssues/287 >> = >> So far, the Conduit API is settling down and works with Lwt_unix, Async = and Mirage, including client DNS lookups and HTTP requests. Before merging= , I'd like to: >> = >> - add sexp accessor functions >> - switch to V2 interfaces (required for previous) >> - get OCaml TLS hooked in >> = >> Once this is all done, Conduit can be released independently of the rest= of the Mirage libs (which in turn unblocks a Cohttp 1.0 release). I'm jus= t holding back releasing it too early so that we don't have to keep revving= the Lwt_unix interfaces all the time. > = > Sounds good. > = >> Regarding vchan, the biggest difference in the new APIs is that Conduit = creates a V1_FLOW interface that abstracts across all the connection mechan= isms (currently TCPv4 and vchan). Previously in Mirage 1.0, this was hardc= oded to TCPv4, and I've had to modify those interfaces in the development r= epository to bring TCPv4 in compliance with the FLOW interface (it's slight= ly odd that we didn't do that before!). > = > IIRC we designed the FLOW from scratch and it ended up different to TCPv4= . Since we wanted V1 to remain stable I think it made sense to postpone TCP= v4-as-FLOW to V2. It=92s definitely the right time to fix it now though! Th= at reminds me, I wanted to make CONSOLE into a superset of FLOW also. This will definitely be V2 I think -- since end points in Conduit are abstr= act, we need the sexp accessors for logging endpoints in a human readable f= ormat. -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 Sep 02 14:10:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 14:10:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOonO-0006mb-Op; Tue, 02 Sep 2014 14:10:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOonN-0006mW-HC for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 14:10:53 +0000 Received: from [85.158.137.68:40963] by server-15.bemta-3.messagelabs.com id B4/DA-01573-CEFC5045; Tue, 02 Sep 2014 14:10:52 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1409667050!7545497!1 X-Originating-IP: [209.85.218.52] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13393 invoked from network); 2 Sep 2014 14:10:52 -0000 Received: from mail-oi0-f52.google.com (HELO mail-oi0-f52.google.com) (209.85.218.52) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 14:10:52 -0000 Received: by mail-oi0-f52.google.com with SMTP id e131so4477540oig.11 for ; Tue, 02 Sep 2014 07:10:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=yiDVxVGxd6qElA8BKkf1hnozS1tNaO840nP8DqgBKZA=; b=ntA9s3ie6if2923GxUhvdViNd4OcvnFsfbp3HVyfBszioV2irBf+F2oj1IqXdPLEkE Mw6d2gFCIWbfY7eqJpSqN035WJwHXUn3V1lUmeuJdCbhbKxjPotKvgHFz7xxC0+a4zi4 sZgZ4bc00ozKShZa1mtk93fq4hA87WPOJiIk98a1PW1nbLOlQSrQmfRxUPCsH6orMyEc aZeExqtl22rLKBzxZzWhuQeA9QeahKfXUA3PKGwi0bL6lWoaPYJllGphhcc7f//7FwTO GKORQhj/KJfGynUXvR95DjeO2cdDLTkpgO45UleRX7zwIjdYV6jTIkergi7CFrlsFf5+ HXLw== MIME-Version: 1.0 X-Received: by 10.60.45.234 with SMTP id q10mr32544628oem.25.1409667050653; Tue, 02 Sep 2014 07:10:50 -0700 (PDT) Received: by 10.76.20.105 with HTTP; Tue, 2 Sep 2014 07:10:50 -0700 (PDT) In-Reply-To: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> References: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> Date: Tue, 2 Sep 2014 15:10:50 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMjEgQXVndXN0IDIwMTQgMTg6MzAsIERhdmUgU2NvdHQgPERhdmUuU2NvdHRAY2l0cml4LmNv bT4gd3JvdGU6Cj4gSGksCj4KPiBPbiAyMSBBdWcgMjAxNCwgYXQgMTI6MTAsIFRob21hcyBMZW9u YXJkIDx0YWxleDVAZ21haWwuY29tPiB3cm90ZToKWy4uLl0KPj4gSSd2ZSB3cml0dGVuIHVwIHRo ZSBwcm9maWxpbmcgSSd2ZSBkb25lIHNvIGZhciBoZXJlOgo+Pgo+PiBodHRwOi8vcm9zY2lkdXMu Y29tL2Jsb2cvYmxvZy8yMDE0LzA4LzE1L29wdGltaXNpbmctdGhlLXVuaWtlcm5lbC8KPj4KPj4g VGhlIGdyYXBocyBhcmUgcXVpdGUgaW50ZXJlc3RpbmcgLSBpZiBwZW9wbGUgZmFtaWxpYXIgd2l0 aCB0aGUgY29kZQo+PiBjb3VsZCBleHBsYWluIHdoYXQncyBnb2luZyBvbiAoZXNwZWNpYWxseSB3 aXRoIHRoZSBibG9jayBkZXZpY2UpIHRoYXQKPj4gd291bGQgYmUgZ3JlYXQhCj4KPiBUaGUgZ3Jh cGhzIGFyZSBpbnRlcmVzdGluZyEKPgo+IElJUkMgdGhlIGdyYW50IHVubWFwIG9wZXJhdGlvbiBp cyB2ZXJ5IGV4cGVuc2l2ZSBzaW5jZSBpdCBpbnZvbHZlcyBhIFRMQiBzaG9vdGRvd24uIFRoaXMg YWRkcyBhIGxhcmdlIGFtb3VudCAocmVsYXRpdmVseSwgY29tcGFyZWQgdG8gbW9kZXJuIGZsYXNo LWJhc2VkIGRpc2tzKSB0byB0aGUgcmVxdWVzdC9yZXNwb25zZSBsYXRlbmN5LiBJIHRoaW5rIHRo aXMgaXMgd2h5IHRoZSBwZXJmb3JtYW5jZSBpcyBzbyB0ZXJyaWJsZSB3aXRoIG9uZSByZXF1ZXN0 IGF0IGEgdGltZS4gSSBzdXNwZWN0IHRoYXQgdGhlIGJhdGNoaW5nIHlvdeKAmXJlIHNlZWluZyB3 aXRoIHR3byByZXF1ZXN0cyBpcyBhbiBhcnRlZmFjdCBvZiB0aGUgYmFja2VuZCwgd2hpY2ggaXMg cHJvYmFibHkgdHJ5aW5nIHRvIHVubWFwIGJvdGggZ3JhbnQgcmVmZXJlbmNlcyBhdCBvbmNlIGZv ciBlZmZpY2llbmN5LiBXaGVuIEkgd3JvdGUgYSB1c2VyLXNwYWNlIGJsb2NrIGJhY2tlbmQgYmF0 Y2hpbmcgdGhlIHVubWFwcyBtYWRlIGEgbWFzc2l2ZSBkaWZmZXJlbmNlLgoKSSB3b25kZXIgaWYg dGhpcyBhcHBsaWVzIHRvIEFSTS4gWW91IHNob3VsZCBiZSBhYmxlIHRvIGludmFsaWRhdGUKaW5k aXZpZHVhbCBUTEIgZW50cmllcyB0aGVyZSwgSSB0aGluay4KCj4gVGhlcmUgaXMgYSBibG9jayBw cm90b2NvbCBleHRlbnNpb24gY2FsbGVkIOKAnHBlcnNpc3RlbnQgZ3JhbnRz4oCdIHRoYXQgd2Ug aGF2ZW7igJl0IGltcGxlbWVudGVkICh5ZXQpLiBUaGlzIGRvZXMgdGhlIG9idmlvdXMgdGhpbmcg YW5kIHByZS1zaGFyZXMgYSBzZXQgb2YgcGFnZXMuIFdlIG1pZ2h0IHN1ZmZlciBhIGJpdCBiZWNh dXNlIG9mIGV4dHJhIGNvcGllcyAoaS5lLiB3ZSBtaWdodCBoYXZlIHRvIGNvcHkgaW50byB0aGUg cHJlLXNoYXJlZCBwYWdlcykgYnV0IHdlIHdvdWxkIHNhdmUgdGhlIHVubWFwIG92ZXJoZWFkLCBz byBpdCBtaWdodCBiZSB3b3J0aCBpdC4KCkhhZCBhIGdvIGF0IHRoaXMsIGJ1dCBpdCBkaWRuJ3Qg bWFrZSBtdWNoIGRpZmZlcmVuY2UuIEhvd2V2ZXIsIEkndmUKZGlzY292ZXJlZCB0aGF0IGRkIGlu IGRvbTAgaXNuJ3QgdG9vIGZhc3QgZWl0aGVyLiBJIG9yaWdpbmFsbHkgdGVzdGVkCndpdGggaGRw YXJtLCB3aGljaCByZXBvcnRzIDIwIE1CL3MgYXMgZXhwZWN0ZWQ6CgokIGhkcGFybSAtdCAvZGV2 L21tY2JsazAKIFRpbWluZyBidWZmZXJlZCBkaXNrIHJlYWRzOiAgNjIgTUIgaW4gIDMuMDcgc2Vj b25kcyA9ICAyMC4yMSBNQi9zZWMKCmRkJ3Mgc3BlZWQgc2VlbXMgdG8gZGVwZW5kIGEgbG90IG9u IHRoZSBibG9jayBzaXplLiBVc2luZwo0MDk2KjExPTQ1MDU2IGJ5dGVzICh3aGljaCBJIGFzc3Vt ZSBpcyB3aGF0IGRvbTAgd291bGQgZG8gaW4gcmVzcG9uc2UKdG8gYSBndWVzdCByZXF1ZXN0KSwg SSBnZXQgMTYuOSBNQi9zOgoKJCBkZCBpZmxhZz1kaXJlY3QgaWY9L2Rldi92ZzAvYmVuY2ggIG9m PS9kZXYvbnVsbCBicz00NTA1NiBjb3VudD0xMDAwCjEwMDArMCByZWNvcmRzIGluCjEwMDArMCBy ZWNvcmRzIG91dAo0NTA1NjAwMCBieXRlcyAoNDUgTUIpIGNvcGllZCwgMi42NTkxMSBzLCAxNi45 IE1CL3MKCmJzPTY1NTM2IGdpdmVzIDE4LjggTUIvcyBhbmQgYnM9MTMxMDcyIGdpdmVzIDIwLjgg TUIvcy4gTGludXggZG9tVQpyZXBvcnRzIDIwLjM2IE1CL3NlYyBmcm9tIGhkcGFybSBidXQgb25s eSAxOC42IE1CL3MgZnJvbSBkZAooYnM9MTMxMDcyKS4gU28gcGVyaGFwcyBNaXJhZ2UgaXMgZG9p bmcgcHJldHR5IHdlbGwgYWxyZWFkeS4KCj4+IE92ZXJhbGwsIHRoZSBjaGFuZ2VzIGluY3JlYXNl ZCB0aGUgcXVldWluZyBzZXJ2aWNlJ3MgZG93bmxvYWQgcmF0ZQo+PiBmcm9tIDIuNDYgTUIvcyB0 byA3LjI0IE1CL3MsIHdoaWNoIGlzIG5pY2UgYnV0IHN0aWxsIGEgYml0Cj4+IGRpc2FwcG9pbnRp bmcuCj4KPiBDZXJ0YWlubHkgYSBnb29kIHN0YXJ0IQoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAg ICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYg IDhCOUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAg QkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2 ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 14:10:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 14:10:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOonO-0006mb-Op; Tue, 02 Sep 2014 14:10:54 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOonN-0006mW-HC for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 14:10:53 +0000 Received: from [85.158.137.68:40963] by server-15.bemta-3.messagelabs.com id B4/DA-01573-CEFC5045; Tue, 02 Sep 2014 14:10:52 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1409667050!7545497!1 X-Originating-IP: [209.85.218.52] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13393 invoked from network); 2 Sep 2014 14:10:52 -0000 Received: from mail-oi0-f52.google.com (HELO mail-oi0-f52.google.com) (209.85.218.52) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 14:10:52 -0000 Received: by mail-oi0-f52.google.com with SMTP id e131so4477540oig.11 for ; Tue, 02 Sep 2014 07:10:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=yiDVxVGxd6qElA8BKkf1hnozS1tNaO840nP8DqgBKZA=; b=ntA9s3ie6if2923GxUhvdViNd4OcvnFsfbp3HVyfBszioV2irBf+F2oj1IqXdPLEkE Mw6d2gFCIWbfY7eqJpSqN035WJwHXUn3V1lUmeuJdCbhbKxjPotKvgHFz7xxC0+a4zi4 sZgZ4bc00ozKShZa1mtk93fq4hA87WPOJiIk98a1PW1nbLOlQSrQmfRxUPCsH6orMyEc aZeExqtl22rLKBzxZzWhuQeA9QeahKfXUA3PKGwi0bL6lWoaPYJllGphhcc7f//7FwTO GKORQhj/KJfGynUXvR95DjeO2cdDLTkpgO45UleRX7zwIjdYV6jTIkergi7CFrlsFf5+ HXLw== MIME-Version: 1.0 X-Received: by 10.60.45.234 with SMTP id q10mr32544628oem.25.1409667050653; Tue, 02 Sep 2014 07:10:50 -0700 (PDT) Received: by 10.76.20.105 with HTTP; Tue, 2 Sep 2014 07:10:50 -0700 (PDT) In-Reply-To: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> References: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> Date: Tue, 2 Sep 2014 15:10:50 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMjEgQXVndXN0IDIwMTQgMTg6MzAsIERhdmUgU2NvdHQgPERhdmUuU2NvdHRAY2l0cml4LmNv bT4gd3JvdGU6Cj4gSGksCj4KPiBPbiAyMSBBdWcgMjAxNCwgYXQgMTI6MTAsIFRob21hcyBMZW9u YXJkIDx0YWxleDVAZ21haWwuY29tPiB3cm90ZToKWy4uLl0KPj4gSSd2ZSB3cml0dGVuIHVwIHRo ZSBwcm9maWxpbmcgSSd2ZSBkb25lIHNvIGZhciBoZXJlOgo+Pgo+PiBodHRwOi8vcm9zY2lkdXMu Y29tL2Jsb2cvYmxvZy8yMDE0LzA4LzE1L29wdGltaXNpbmctdGhlLXVuaWtlcm5lbC8KPj4KPj4g VGhlIGdyYXBocyBhcmUgcXVpdGUgaW50ZXJlc3RpbmcgLSBpZiBwZW9wbGUgZmFtaWxpYXIgd2l0 aCB0aGUgY29kZQo+PiBjb3VsZCBleHBsYWluIHdoYXQncyBnb2luZyBvbiAoZXNwZWNpYWxseSB3 aXRoIHRoZSBibG9jayBkZXZpY2UpIHRoYXQKPj4gd291bGQgYmUgZ3JlYXQhCj4KPiBUaGUgZ3Jh cGhzIGFyZSBpbnRlcmVzdGluZyEKPgo+IElJUkMgdGhlIGdyYW50IHVubWFwIG9wZXJhdGlvbiBp cyB2ZXJ5IGV4cGVuc2l2ZSBzaW5jZSBpdCBpbnZvbHZlcyBhIFRMQiBzaG9vdGRvd24uIFRoaXMg YWRkcyBhIGxhcmdlIGFtb3VudCAocmVsYXRpdmVseSwgY29tcGFyZWQgdG8gbW9kZXJuIGZsYXNo LWJhc2VkIGRpc2tzKSB0byB0aGUgcmVxdWVzdC9yZXNwb25zZSBsYXRlbmN5LiBJIHRoaW5rIHRo aXMgaXMgd2h5IHRoZSBwZXJmb3JtYW5jZSBpcyBzbyB0ZXJyaWJsZSB3aXRoIG9uZSByZXF1ZXN0 IGF0IGEgdGltZS4gSSBzdXNwZWN0IHRoYXQgdGhlIGJhdGNoaW5nIHlvdeKAmXJlIHNlZWluZyB3 aXRoIHR3byByZXF1ZXN0cyBpcyBhbiBhcnRlZmFjdCBvZiB0aGUgYmFja2VuZCwgd2hpY2ggaXMg cHJvYmFibHkgdHJ5aW5nIHRvIHVubWFwIGJvdGggZ3JhbnQgcmVmZXJlbmNlcyBhdCBvbmNlIGZv ciBlZmZpY2llbmN5LiBXaGVuIEkgd3JvdGUgYSB1c2VyLXNwYWNlIGJsb2NrIGJhY2tlbmQgYmF0 Y2hpbmcgdGhlIHVubWFwcyBtYWRlIGEgbWFzc2l2ZSBkaWZmZXJlbmNlLgoKSSB3b25kZXIgaWYg dGhpcyBhcHBsaWVzIHRvIEFSTS4gWW91IHNob3VsZCBiZSBhYmxlIHRvIGludmFsaWRhdGUKaW5k aXZpZHVhbCBUTEIgZW50cmllcyB0aGVyZSwgSSB0aGluay4KCj4gVGhlcmUgaXMgYSBibG9jayBw cm90b2NvbCBleHRlbnNpb24gY2FsbGVkIOKAnHBlcnNpc3RlbnQgZ3JhbnRz4oCdIHRoYXQgd2Ug aGF2ZW7igJl0IGltcGxlbWVudGVkICh5ZXQpLiBUaGlzIGRvZXMgdGhlIG9idmlvdXMgdGhpbmcg YW5kIHByZS1zaGFyZXMgYSBzZXQgb2YgcGFnZXMuIFdlIG1pZ2h0IHN1ZmZlciBhIGJpdCBiZWNh dXNlIG9mIGV4dHJhIGNvcGllcyAoaS5lLiB3ZSBtaWdodCBoYXZlIHRvIGNvcHkgaW50byB0aGUg cHJlLXNoYXJlZCBwYWdlcykgYnV0IHdlIHdvdWxkIHNhdmUgdGhlIHVubWFwIG92ZXJoZWFkLCBz byBpdCBtaWdodCBiZSB3b3J0aCBpdC4KCkhhZCBhIGdvIGF0IHRoaXMsIGJ1dCBpdCBkaWRuJ3Qg bWFrZSBtdWNoIGRpZmZlcmVuY2UuIEhvd2V2ZXIsIEkndmUKZGlzY292ZXJlZCB0aGF0IGRkIGlu IGRvbTAgaXNuJ3QgdG9vIGZhc3QgZWl0aGVyLiBJIG9yaWdpbmFsbHkgdGVzdGVkCndpdGggaGRw YXJtLCB3aGljaCByZXBvcnRzIDIwIE1CL3MgYXMgZXhwZWN0ZWQ6CgokIGhkcGFybSAtdCAvZGV2 L21tY2JsazAKIFRpbWluZyBidWZmZXJlZCBkaXNrIHJlYWRzOiAgNjIgTUIgaW4gIDMuMDcgc2Vj b25kcyA9ICAyMC4yMSBNQi9zZWMKCmRkJ3Mgc3BlZWQgc2VlbXMgdG8gZGVwZW5kIGEgbG90IG9u IHRoZSBibG9jayBzaXplLiBVc2luZwo0MDk2KjExPTQ1MDU2IGJ5dGVzICh3aGljaCBJIGFzc3Vt ZSBpcyB3aGF0IGRvbTAgd291bGQgZG8gaW4gcmVzcG9uc2UKdG8gYSBndWVzdCByZXF1ZXN0KSwg SSBnZXQgMTYuOSBNQi9zOgoKJCBkZCBpZmxhZz1kaXJlY3QgaWY9L2Rldi92ZzAvYmVuY2ggIG9m PS9kZXYvbnVsbCBicz00NTA1NiBjb3VudD0xMDAwCjEwMDArMCByZWNvcmRzIGluCjEwMDArMCBy ZWNvcmRzIG91dAo0NTA1NjAwMCBieXRlcyAoNDUgTUIpIGNvcGllZCwgMi42NTkxMSBzLCAxNi45 IE1CL3MKCmJzPTY1NTM2IGdpdmVzIDE4LjggTUIvcyBhbmQgYnM9MTMxMDcyIGdpdmVzIDIwLjgg TUIvcy4gTGludXggZG9tVQpyZXBvcnRzIDIwLjM2IE1CL3NlYyBmcm9tIGhkcGFybSBidXQgb25s eSAxOC42IE1CL3MgZnJvbSBkZAooYnM9MTMxMDcyKS4gU28gcGVyaGFwcyBNaXJhZ2UgaXMgZG9p bmcgcHJldHR5IHdlbGwgYWxyZWFkeS4KCj4+IE92ZXJhbGwsIHRoZSBjaGFuZ2VzIGluY3JlYXNl ZCB0aGUgcXVldWluZyBzZXJ2aWNlJ3MgZG93bmxvYWQgcmF0ZQo+PiBmcm9tIDIuNDYgTUIvcyB0 byA3LjI0IE1CL3MsIHdoaWNoIGlzIG5pY2UgYnV0IHN0aWxsIGEgYml0Cj4+IGRpc2FwcG9pbnRp bmcuCj4KPiBDZXJ0YWlubHkgYSBnb29kIHN0YXJ0IQoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAg ICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYg IDhCOUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAg QkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2 ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1i aW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 15:04:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 15:04:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOpd9-0007hi-Gq; Tue, 02 Sep 2014 15:04:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOpd8-0007hd-DA for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 15:04:22 +0000 Received: from [85.158.143.35:3705] by server-1.bemta-4.messagelabs.com id 0E/46-05872-57CD5045; Tue, 02 Sep 2014 15:04:21 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1409670258!13130218!1 X-Originating-IP: [209.85.216.178] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18757 invoked from network); 2 Sep 2014 15:04:19 -0000 Received: from mail-qc0-f178.google.com (HELO mail-qc0-f178.google.com) (209.85.216.178) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 15:04:19 -0000 Received: by mail-qc0-f178.google.com with SMTP id x13so7100870qcv.9 for ; Tue, 02 Sep 2014 08:04:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Te1YCd5mIYDAmii27w17hBsnlj+otFYbw8MLneHSUhI=; b=SfTCFMSiEX6C3LXZb8nnVka2q4w/v6oD7NVnF7P86H3761snH7LUrzx0ouLAtCzZkO HD+ABPuesw8zesvk1b7FRJ6IRwQgFUVgN40kmRUwkHHzz9Qw431GXknXseV/raMumw/y n7qF03vbTDLpczcq/JxII11hvYYHIiWhho865QJhtuBTglqVKnjP2yrA6XiD850ErIIZ Negdbzia65K5kcN++IV+VNH2Y3grLgJgGvr2wplG83pXA4GfXSrq/9kE1jy2IvcW85up 6O6y2QpoyXWLoQZGlOUXzl7ABtGQgkdBKfnNS5HeQOGY/0hx1a8rXhTzRxsAtHzfcwHW USeg== MIME-Version: 1.0 X-Received: by 10.140.35.242 with SMTP id n105mr52641421qgn.11.1409670258564; Tue, 02 Sep 2014 08:04:18 -0700 (PDT) Received: by 10.140.109.133 with HTTP; Tue, 2 Sep 2014 08:04:18 -0700 (PDT) In-Reply-To: References: Date: Tue, 2 Sep 2014 16:04:18 +0100 X-Google-Sender-Auth: yz_u6weHBFfFOqT7ZhCjphHijkc Message-ID: From: Jon Crowcroft To: Thomas Leonard Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6606698414022095955==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6606698414022095955== Content-Type: multipart/alternative; boundary=001a11c03ce0032cb50502166f05 --001a11c03ce0032cb50502166f05 Content-Type: text/plain; charset=UTF-8 by the way, back in the day, someone did some work on UDP in BSD unix to get it to not go so slow (see A Faster UDP by partidge and pink http://dl.acm.org/citation.cfm?id=169943 but i dont think anyone picked up on those optimisations in the Linux world (though obviously did for TCP) - not sure tho! On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard wrote: > On 21 August 2014 15:09, Thomas Gazagnaire wrote: > >>> Cool -- it would be great to polish up a tool like this. > >> > >> Yes, I think there's a lot we could do here. I've written up the > >> profiling I've done so far here: > >> > >> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ > >> > >> The graphs are quite interesting - if people familiar with the code > >> could explain what's going on (especially with the block device) that > >> would be great! > > > > I'm settting up a 4.01 switch with profiling on. > > Thanks! > > > Do you think the -fno-omit-frame-pointer configure options could also > help to have more precise profiling information? > > I'm not sure it would help. The problems currently are: > > 1. We can't tell when a function returns until the next one is called. > 2. Tail calls look like the function returned first. > 3. For recursive calls, we can't tell which frame is the caller. (e.g. > foo calls foo and foo calls bar, but we don't know which foo > activation called bar). > > We could guess (3) by looking at the stack pointer. But it wouldn't > work for tail calls, since the stack doesn't grow and if we solved (1) > and (2) then we'd get (3) for free. > > I guess it wouldn't be hard to make the compiler call a trace function > on every return / before every tail call. > > The frame pointer would be useful if we didn't have tracing but wanted > a backtrace. > > > Thomas > > > >> > >> Overall, the changes increased the queuing service's download rate > >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit > >> disappointing. > >> > >> > >> -- > >> Dr Thomas Leonard http://0install.net/ > >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > >> > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11c03ce0032cb50502166f05 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
by the way, back in the day, someone did some work on UDP = in BSD unix to get it to not go so slow (see
A Faster UDP
by = partidge and pink=C2=A0
but i dont think anyone picked up on those optimisations in the = Linux world (though obviously did for TCP) - not sure tho!


On Thu, Aug 21, 20= 14 at 3:31 PM, Thomas Leonard <talex5@gmail.com> wrote:
On 21 August 2014 15:09, Tho= mas Gazagnaire <thomas@gazagnai= re.org> wrote:
>>> Cool -- it would be great to polish up a tool like this.
>>
>> Yes, I think there's a lot we could do here. I've written = up the
>> profiling I've done so far here:
>>
>> http://roscidus.com/blog/blog/2014/08/15/opt= imising-the-unikernel/
>>
>> The graphs are quite interesting - if people familiar with the cod= e
>> could explain what's going on (especially with the block devic= e) that
>> would be great!
>
> I'm settting up a 4.01 switch with profiling on.

Thanks!

> Do you think the -fno-omit-frame-pointer configure options could also = help to have more precise profiling information?

I'm not sure it would help. The problems currently are:

1. We can't tell when a function returns until the next one is called.<= br> 2. Tail calls look like the function returned first.
3. For recursive calls, we can't tell which frame is the caller. (e.g.<= br> foo calls foo and foo calls bar, but we don't know which foo
activation called bar).

We could guess (3) by looking at the stack pointer. But it wouldn't
work for tail calls, since the stack doesn't grow and if we solved (1)<= br> and (2) then we'd get (3) for free.

I guess it wouldn't be hard to make the compiler call a trace function<= br> on every return / before every tail call.

The frame pointer would be useful if we didn't have tracing but wanted<= br> a backtrace.

> Thomas
>
>>
>> Overall, the changes increased the queuing service's download = rate
>> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit
>> disappointing.
>>
>>
>> --
>> Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
>> GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
>> GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA
>>
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-de= vel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>



--
Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA

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

--001a11c03ce0032cb50502166f05-- --===============6606698414022095955== 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 --===============6606698414022095955==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 15:04:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 15:04:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOpd9-0007hi-Gq; Tue, 02 Sep 2014 15:04:23 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOpd8-0007hd-DA for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 15:04:22 +0000 Received: from [85.158.143.35:3705] by server-1.bemta-4.messagelabs.com id 0E/46-05872-57CD5045; Tue, 02 Sep 2014 15:04:21 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1409670258!13130218!1 X-Originating-IP: [209.85.216.178] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18757 invoked from network); 2 Sep 2014 15:04:19 -0000 Received: from mail-qc0-f178.google.com (HELO mail-qc0-f178.google.com) (209.85.216.178) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 15:04:19 -0000 Received: by mail-qc0-f178.google.com with SMTP id x13so7100870qcv.9 for ; Tue, 02 Sep 2014 08:04:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Te1YCd5mIYDAmii27w17hBsnlj+otFYbw8MLneHSUhI=; b=SfTCFMSiEX6C3LXZb8nnVka2q4w/v6oD7NVnF7P86H3761snH7LUrzx0ouLAtCzZkO HD+ABPuesw8zesvk1b7FRJ6IRwQgFUVgN40kmRUwkHHzz9Qw431GXknXseV/raMumw/y n7qF03vbTDLpczcq/JxII11hvYYHIiWhho865QJhtuBTglqVKnjP2yrA6XiD850ErIIZ Negdbzia65K5kcN++IV+VNH2Y3grLgJgGvr2wplG83pXA4GfXSrq/9kE1jy2IvcW85up 6O6y2QpoyXWLoQZGlOUXzl7ABtGQgkdBKfnNS5HeQOGY/0hx1a8rXhTzRxsAtHzfcwHW USeg== MIME-Version: 1.0 X-Received: by 10.140.35.242 with SMTP id n105mr52641421qgn.11.1409670258564; Tue, 02 Sep 2014 08:04:18 -0700 (PDT) Received: by 10.140.109.133 with HTTP; Tue, 2 Sep 2014 08:04:18 -0700 (PDT) In-Reply-To: References: Date: Tue, 2 Sep 2014 16:04:18 +0100 X-Google-Sender-Auth: yz_u6weHBFfFOqT7ZhCjphHijkc Message-ID: From: Jon Crowcroft To: Thomas Leonard Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6606698414022095955==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6606698414022095955== Content-Type: multipart/alternative; boundary=001a11c03ce0032cb50502166f05 --001a11c03ce0032cb50502166f05 Content-Type: text/plain; charset=UTF-8 by the way, back in the day, someone did some work on UDP in BSD unix to get it to not go so slow (see A Faster UDP by partidge and pink http://dl.acm.org/citation.cfm?id=169943 but i dont think anyone picked up on those optimisations in the Linux world (though obviously did for TCP) - not sure tho! On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard wrote: > On 21 August 2014 15:09, Thomas Gazagnaire wrote: > >>> Cool -- it would be great to polish up a tool like this. > >> > >> Yes, I think there's a lot we could do here. I've written up the > >> profiling I've done so far here: > >> > >> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ > >> > >> The graphs are quite interesting - if people familiar with the code > >> could explain what's going on (especially with the block device) that > >> would be great! > > > > I'm settting up a 4.01 switch with profiling on. > > Thanks! > > > Do you think the -fno-omit-frame-pointer configure options could also > help to have more precise profiling information? > > I'm not sure it would help. The problems currently are: > > 1. We can't tell when a function returns until the next one is called. > 2. Tail calls look like the function returned first. > 3. For recursive calls, we can't tell which frame is the caller. (e.g. > foo calls foo and foo calls bar, but we don't know which foo > activation called bar). > > We could guess (3) by looking at the stack pointer. But it wouldn't > work for tail calls, since the stack doesn't grow and if we solved (1) > and (2) then we'd get (3) for free. > > I guess it wouldn't be hard to make the compiler call a trace function > on every return / before every tail call. > > The frame pointer would be useful if we didn't have tracing but wanted > a backtrace. > > > Thomas > > > >> > >> Overall, the changes increased the queuing service's download rate > >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit > >> disappointing. > >> > >> > >> -- > >> Dr Thomas Leonard http://0install.net/ > >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > >> > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11c03ce0032cb50502166f05 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
by the way, back in the day, someone did some work on UDP = in BSD unix to get it to not go so slow (see
A Faster UDP
by = partidge and pink=C2=A0
but i dont think anyone picked up on those optimisations in the = Linux world (though obviously did for TCP) - not sure tho!


On Thu, Aug 21, 20= 14 at 3:31 PM, Thomas Leonard <talex5@gmail.com> wrote:
On 21 August 2014 15:09, Tho= mas Gazagnaire <thomas@gazagnai= re.org> wrote:
>>> Cool -- it would be great to polish up a tool like this.
>>
>> Yes, I think there's a lot we could do here. I've written = up the
>> profiling I've done so far here:
>>
>> http://roscidus.com/blog/blog/2014/08/15/opt= imising-the-unikernel/
>>
>> The graphs are quite interesting - if people familiar with the cod= e
>> could explain what's going on (especially with the block devic= e) that
>> would be great!
>
> I'm settting up a 4.01 switch with profiling on.

Thanks!

> Do you think the -fno-omit-frame-pointer configure options could also = help to have more precise profiling information?

I'm not sure it would help. The problems currently are:

1. We can't tell when a function returns until the next one is called.<= br> 2. Tail calls look like the function returned first.
3. For recursive calls, we can't tell which frame is the caller. (e.g.<= br> foo calls foo and foo calls bar, but we don't know which foo
activation called bar).

We could guess (3) by looking at the stack pointer. But it wouldn't
work for tail calls, since the stack doesn't grow and if we solved (1)<= br> and (2) then we'd get (3) for free.

I guess it wouldn't be hard to make the compiler call a trace function<= br> on every return / before every tail call.

The frame pointer would be useful if we didn't have tracing but wanted<= br> a backtrace.

> Thomas
>
>>
>> Overall, the changes increased the queuing service's download = rate
>> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit
>> disappointing.
>>
>>
>> --
>> Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
>> GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
>> GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA
>>
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-de= vel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>



--
Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA

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

--001a11c03ce0032cb50502166f05-- --===============6606698414022095955== 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 --===============6606698414022095955==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 19:49:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 19:49: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 1XOu4q-0000T5-Co; Tue, 02 Sep 2014 19:49:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOu4p-0000T0-35 for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 19:49:15 +0000 Received: from [85.158.137.68:15479] by server-2.bemta-3.messagelabs.com id 2E/5F-09149-A3F16045; Tue, 02 Sep 2014 19:49:14 +0000 X-Env-Sender: jacob.d.mitchell@gmail.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1409687352!12101776!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24867 invoked from network); 2 Sep 2014 19:49:13 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 19:49:13 -0000 Received: by mail-qa0-f44.google.com with SMTP id j7so6827427qaq.31 for ; Tue, 02 Sep 2014 12:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=9ONOfDfHre3XKtDv5vpKuvXu9+ns8NHi8alrq6WaOkw=; b=D5FulXfY9DG7huoApZqSsqYQPoMaiGiVeOVCjNQE1EDXlND04ZA4lbAchYmSGEXrR6 Be6kMIDaaFZS4PcR/zgu20ou6Lb4KQg0mpjgmE/sNccZGseDYEeLDBqAiK95WTRvmPiT /qM0llNndPA86N4AbtjfqIAzCsQXPO6wJ4I7GsPVtCIwgc2C9BJEFS8iyuLS4Uzg0s1X D+DWn4xoOEbYYkGXg0DS0gNZXfcrtW3Fsf29//XmvDhSLT8v4UQ5waXh/5f9PiOqCmR2 2PTbNqeBHDxyR2qHQ398aEHclJEfV/Qhqsj8iSKLvkal2Ovb5wdk43wvV7C4M+tRsVzd jECg== X-Received: by 10.140.104.213 with SMTP id a79mr56505184qgf.46.1409687352384; Tue, 02 Sep 2014 12:49:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.34 with HTTP; Tue, 2 Sep 2014 12:48:52 -0700 (PDT) From: Jacob Mitchell Date: Tue, 2 Sep 2014 12:48:52 -0700 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org 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 Goal: print the current time to the console; repeat until termination. I think I'm close, but when I call "make" the compiled main.ml file results in an "Unbound value clock" error. Refer to https://gist.github.com/anonymous/90f4107cf5008b12d356 for my source code, the main.ml file, and the build log. Any pointers? I haven't found any tests or sample code to demonstrate how to use non-polymorphic first-class modules like CLOCK, TIME, and RANDOM. -Jake _______________________________________________ MirageOS-devel 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 Sep 02 19:49:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 19:49: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 1XOu4q-0000T5-Co; Tue, 02 Sep 2014 19:49:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOu4p-0000T0-35 for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 19:49:15 +0000 Received: from [85.158.137.68:15479] by server-2.bemta-3.messagelabs.com id 2E/5F-09149-A3F16045; Tue, 02 Sep 2014 19:49:14 +0000 X-Env-Sender: jacob.d.mitchell@gmail.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1409687352!12101776!1 X-Originating-IP: [209.85.216.44] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24867 invoked from network); 2 Sep 2014 19:49:13 -0000 Received: from mail-qa0-f44.google.com (HELO mail-qa0-f44.google.com) (209.85.216.44) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 19:49:13 -0000 Received: by mail-qa0-f44.google.com with SMTP id j7so6827427qaq.31 for ; Tue, 02 Sep 2014 12:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=9ONOfDfHre3XKtDv5vpKuvXu9+ns8NHi8alrq6WaOkw=; b=D5FulXfY9DG7huoApZqSsqYQPoMaiGiVeOVCjNQE1EDXlND04ZA4lbAchYmSGEXrR6 Be6kMIDaaFZS4PcR/zgu20ou6Lb4KQg0mpjgmE/sNccZGseDYEeLDBqAiK95WTRvmPiT /qM0llNndPA86N4AbtjfqIAzCsQXPO6wJ4I7GsPVtCIwgc2C9BJEFS8iyuLS4Uzg0s1X D+DWn4xoOEbYYkGXg0DS0gNZXfcrtW3Fsf29//XmvDhSLT8v4UQ5waXh/5f9PiOqCmR2 2PTbNqeBHDxyR2qHQ398aEHclJEfV/Qhqsj8iSKLvkal2Ovb5wdk43wvV7C4M+tRsVzd jECg== X-Received: by 10.140.104.213 with SMTP id a79mr56505184qgf.46.1409687352384; Tue, 02 Sep 2014 12:49:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.34 with HTTP; Tue, 2 Sep 2014 12:48:52 -0700 (PDT) From: Jacob Mitchell Date: Tue, 2 Sep 2014 12:48:52 -0700 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org 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 Goal: print the current time to the console; repeat until termination. I think I'm close, but when I call "make" the compiled main.ml file results in an "Unbound value clock" error. Refer to https://gist.github.com/anonymous/90f4107cf5008b12d356 for my source code, the main.ml file, and the build log. Any pointers? I haven't found any tests or sample code to demonstrate how to use non-polymorphic first-class modules like CLOCK, TIME, and RANDOM. -Jake _______________________________________________ MirageOS-devel 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 Sep 02 20:09:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 20:09: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 1XOuOB-0000i2-CY; Tue, 02 Sep 2014 20:09:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOuO9-0000hH-TR for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 20:09:14 +0000 Received: from [193.109.254.147:5719] by server-15.bemta-14.messagelabs.com id 3E/93-30948-9E326045; Tue, 02 Sep 2014 20:09:13 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1409688551!13030796!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21268 invoked from network); 2 Sep 2014 20:09:11 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 20:09:11 -0000 X-IronPort-AV: E=Sophos;i="5.04,451,1406592000"; d="scan'208";a="24456887" From: Dave Scott To: Jacob Mitchell Thread-Topic: [MirageOS-devel] Help using V1.CLOCK Thread-Index: AQHPxucAEpqPkB2OD0WOVdll2dKMVJvuJCkA Date: Tue, 2 Sep 2014 20:09:10 +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: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 2 Sep 2014, at 20:48, Jacob Mitchell wrote: > Goal: print the current time to the console; repeat until termination. > = > I think I'm close, but when I call "make" the compiled main.ml file > results in an "Unbound value clock" error. Refer to > https://gist.github.com/anonymous/90f4107cf5008b12d356 for my source > code, the main.ml file, and the build log. > = > Any pointers? I haven't found any tests or sample code to demonstrate > how to use non-polymorphic first-class modules like CLOCK, TIME, and > RANDOM. It looks to me like a mismatch between the generated code (in main.ml) and = the mirage-clock code. The other devices (block, network, console) have a = =91connect=92 function to connect to an instance, but the clock[1] is a sin= gleton. So I think we just need to omit all references to =93clock=94 (the = instance) in the generated fragment: >>>> module M1 =3D Unikernel.Main(Console)(Clock) let t1 () =3D clock () >>=3D function | `Error e -> fail (Failure "clock") | `Ok clock -> console1 () >>=3D function | `Error e -> fail (Failure "console1") | `Ok console1 -> M1.start console1 clock <<<< I=92ll take a quick look. Cheers, Dave [1] https://github.com/mirage/mirage-clock/blob/master/unix/clock.mli _______________________________________________ MirageOS-devel 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 Sep 02 20:09:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 20:09: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 1XOuOB-0000i2-CY; Tue, 02 Sep 2014 20:09:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOuO9-0000hH-TR for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 20:09:14 +0000 Received: from [193.109.254.147:5719] by server-15.bemta-14.messagelabs.com id 3E/93-30948-9E326045; Tue, 02 Sep 2014 20:09:13 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1409688551!13030796!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21268 invoked from network); 2 Sep 2014 20:09:11 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 20:09:11 -0000 X-IronPort-AV: E=Sophos;i="5.04,451,1406592000"; d="scan'208";a="24456887" From: Dave Scott To: Jacob Mitchell Thread-Topic: [MirageOS-devel] Help using V1.CLOCK Thread-Index: AQHPxucAEpqPkB2OD0WOVdll2dKMVJvuJCkA Date: Tue, 2 Sep 2014 20:09:10 +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: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 2 Sep 2014, at 20:48, Jacob Mitchell wrote: > Goal: print the current time to the console; repeat until termination. > = > I think I'm close, but when I call "make" the compiled main.ml file > results in an "Unbound value clock" error. Refer to > https://gist.github.com/anonymous/90f4107cf5008b12d356 for my source > code, the main.ml file, and the build log. > = > Any pointers? I haven't found any tests or sample code to demonstrate > how to use non-polymorphic first-class modules like CLOCK, TIME, and > RANDOM. It looks to me like a mismatch between the generated code (in main.ml) and = the mirage-clock code. The other devices (block, network, console) have a = =91connect=92 function to connect to an instance, but the clock[1] is a sin= gleton. So I think we just need to omit all references to =93clock=94 (the = instance) in the generated fragment: >>>> module M1 =3D Unikernel.Main(Console)(Clock) let t1 () =3D clock () >>=3D function | `Error e -> fail (Failure "clock") | `Ok clock -> console1 () >>=3D function | `Error e -> fail (Failure "console1") | `Ok console1 -> M1.start console1 clock <<<< I=92ll take a quick look. Cheers, Dave [1] https://github.com/mirage/mirage-clock/blob/master/unix/clock.mli _______________________________________________ MirageOS-devel 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 Sep 02 20:34:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 20:34: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 1XOumG-0001JC-4J; Tue, 02 Sep 2014 20:34:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOumF-0001J4-Cw for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 20:34:07 +0000 Received: from [85.158.143.35:48137] by server-2.bemta-4.messagelabs.com id E1/A5-04525-EB926045; Tue, 02 Sep 2014 20:34:06 +0000 X-Env-Sender: jacob.d.mitchell@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1409690043!13238984!1 X-Originating-IP: [209.85.192.41] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6538 invoked from network); 2 Sep 2014 20:34:04 -0000 Received: from mail-qg0-f41.google.com (HELO mail-qg0-f41.google.com) (209.85.192.41) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 20:34:04 -0000 Received: by mail-qg0-f41.google.com with SMTP id i50so7196067qgf.0 for ; Tue, 02 Sep 2014 13:34:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=bIEp83oM5KgKnI2E1POI8onE+68aIT6BBwX8sV/dA+c=; b=hsz8Ix45APLovQ9DBG9c6v62D1tFTwGqn9iMP+PNBzd2oP6ldAZS+nhLqtUtCmlD2D q4RnC8JXOwjS9oIsjtpE+UOw+VyWYBlXIXdKat5T5/FHBcYIZFJCli4dB5seEP9o0jEp TOL4YoK0FF0mrDNkujYmjHHZFisJ9bfunL1PUHxn6AH5lB1HQoRHE2z28zc0y4BjIY2f EFcJ6+EMsIoAQK32Wl/zvZV97E/xbKb6xSV3wR6cmkbAzp+TKJZDSkW9f4HOnhKQwErI pX1LRWE8BJy3kZScp+BnaB+6ZGy9qY8EFA9XM3LndhrfvMfz1OyBYMkEII7uGxTr8HEZ +nRw== X-Received: by 10.140.102.142 with SMTP id w14mr55348538qge.101.1409690043122; Tue, 02 Sep 2014 13:34:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.34 with HTTP; Tue, 2 Sep 2014 13:33:43 -0700 (PDT) In-Reply-To: References: From: Jacob Mitchell Date: Tue, 2 Sep 2014 13:33:43 -0700 Message-ID: To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org VGhhbmtzLCBEYXZlLgoKT24gVHVlLCBTZXAgMiwgMjAxNCBhdCAxOjA5IFBNLCBEYXZlIFNjb3R0 IDxEYXZlLlNjb3R0QGNpdHJpeC5jb20+IHdyb3RlOgo+IEhpLAo+Cj4gT24gMiBTZXAgMjAxNCwg YXQgMjA6NDgsIEphY29iIE1pdGNoZWxsIDxqYWNvYi5kLm1pdGNoZWxsQGdtYWlsLmNvbT4gd3Jv dGU6Cj4KPj4gR29hbDogcHJpbnQgdGhlIGN1cnJlbnQgdGltZSB0byB0aGUgY29uc29sZTsgcmVw ZWF0IHVudGlsIHRlcm1pbmF0aW9uLgo+Pgo+PiBJIHRoaW5rIEknbSBjbG9zZSwgYnV0IHdoZW4g SSBjYWxsICJtYWtlIiB0aGUgY29tcGlsZWQgbWFpbi5tbCBmaWxlCj4+IHJlc3VsdHMgaW4gYW4g IlVuYm91bmQgdmFsdWUgY2xvY2siIGVycm9yLiBSZWZlciB0bwo+PiBodHRwczovL2dpc3QuZ2l0 aHViLmNvbS9hbm9ueW1vdXMvOTBmNDEwN2NmNTAwOGIxMmQzNTYgZm9yIG15IHNvdXJjZQo+PiBj b2RlLCB0aGUgbWFpbi5tbCBmaWxlLCBhbmQgdGhlIGJ1aWxkIGxvZy4KPj4KPj4gQW55IHBvaW50 ZXJzPyBJIGhhdmVuJ3QgZm91bmQgYW55IHRlc3RzIG9yIHNhbXBsZSBjb2RlIHRvIGRlbW9uc3Ry YXRlCj4+IGhvdyB0byB1c2Ugbm9uLXBvbHltb3JwaGljIGZpcnN0LWNsYXNzIG1vZHVsZXMgbGlr ZSBDTE9DSywgVElNRSwgYW5kCj4+IFJBTkRPTS4KPgo+IEl0IGxvb2tzIHRvIG1lIGxpa2UgYSBt aXNtYXRjaCBiZXR3ZWVuIHRoZSBnZW5lcmF0ZWQgY29kZSAoaW4gbWFpbi5tbCkgYW5kIHRoZSBt aXJhZ2UtY2xvY2sgY29kZS4gVGhlIG90aGVyIGRldmljZXMgKGJsb2NrLCBuZXR3b3JrLCBjb25z b2xlKSBoYXZlIGEg4oCYY29ubmVjdOKAmSBmdW5jdGlvbiB0byBjb25uZWN0IHRvIGFuIGluc3Rh bmNlLCBidXQgdGhlIGNsb2NrWzFdIGlzIGEgc2luZ2xldG9uLiBTbyBJIHRoaW5rIHdlIGp1c3Qg bmVlZCB0byBvbWl0IGFsbCByZWZlcmVuY2VzIHRvIOKAnGNsb2Nr4oCdICh0aGUgaW5zdGFuY2Up IGluIHRoZSBnZW5lcmF0ZWQgZnJhZ21lbnQ6Cj4KPj4+Pj4KPiBtb2R1bGUgTTEgPSBVbmlrZXJu ZWwuTWFpbihDb25zb2xlKShDbG9jaykKPgo+IGxldCB0MSAoKSA9Cj4gICBjbG9jayAoKSA+Pj0g ZnVuY3Rpb24KPiAgIHwgYEVycm9yIGUgLT4gZmFpbCAoRmFpbHVyZSAiY2xvY2siKQo+ICAgfCBg T2sgY2xvY2sgLT4KPiAgIGNvbnNvbGUxICgpID4+PSBmdW5jdGlvbgo+ICAgfCBgRXJyb3IgZSAt PiBmYWlsIChGYWlsdXJlICJjb25zb2xlMSIpCj4gICB8IGBPayBjb25zb2xlMSAtPgo+ICAgTTEu c3RhcnQgY29uc29sZTEgY2xvY2sKPiA8PDw8Cj4KClRoZSBwcm9ibGVtIG1heSBleHRlbmQgdG8g Zmlyc3QtY2xhc3MgbW9kdWxlcyB0aGF0IGFyZW4ndCBERVZJQ0VzCihlLmcuIFJBTkRPTSkuIEkg cmFuIGludG8gdGhlIHNhbWUgc29ydCBvZiBlcnJvciB3aGVuIEkgdHJpZWQgcHJpbnRpbmcKYSBy YW5kb20gaW50IG9uIGVhY2ggbGluZSBpbnN0ZWFkIG9mIHRoZSBjdXJyZW50IHRpbWUuIFRoZSBj b2RlIEkKdHJpZWQgZm9sbG93czoKCj4+Pj4gKGNvbmZpZy5tbCkKb3BlbiBNaXJhZ2UKCmxldCBt YWluID0KICBmb3JlaWduICJVbmlrZXJuZWwuTWFpbiIgKGNvbnNvbGUgQC0+IHJhbmRvbSBALT4g am9iKQoKbGV0ICgpID0KICByZWdpc3RlciAiY29uc29sZSIgWyBtYWluICQgZGVmYXVsdF9jb25z b2xlICQgZGVmYXVsdF9yYW5kb20gXQo8PDw8CgoKPj4+PiAodW5pa2VybmVsLm1sKQpvcGVuIFYx Cm9wZW4gTHd0Cgptb2R1bGUgTWFpbiAoQzogQ09OU09MRSkoUkFORDogUkFORE9NKSA9IHN0cnVj dAoKbGV0IHN0YXJ0IGNvbnNvbGUgcmFuZG9tID0KICBSQU5ELnNlbGZfaW5pdCAoKSA7CiAgd2hp bGUgdHJ1ZSBkbwogICAgQy5sb2cgY29uc29sZSAoUHJpbnRmLnNwcmludGYgIiVkIiAoUkFORC5p bnQgMikpCiAgZG9uZSA7CiAgcmV0dXJuICgpCmVuZAo8PDw8CgoKPj4+PiBidWlsZCBlcnJvciAo dW5kZXIgVU5JWCBtb2RlKQpGaWxlICJtYWluLm1sIiwgbGluZSAyMCwgY2hhcmFjdGVycyAyLTg6 CkVycm9yOiBVbmJvdW5kIHZhbHVlIHJhbmRvbQpDb21tYW5kIGV4aXRlZCB3aXRoIGNvZGUgMi4K bWFrZTogKioqIFttYWluLm5hdGl2ZV0gRXJyb3IgMTAKPDw8PAoKCj4+Pj4gZ2VuZXJhdGVkIG1h aW4ubWwgKGV4Y2VycHQpCm1vZHVsZSBNMSA9IFVuaWtlcm5lbC5NYWluKENvbnNvbGUpKFJhbmRv bSkKCmxldCB0MSAoKSA9CiAgY29uc29sZTEgKCkgPj49IGZ1bmN0aW9uCiAgfCBgRXJyb3IgZSAt PiBmYWlsIChGYWlsdXJlICJjb25zb2xlMSIpCiAgfCBgT2sgY29uc29sZTEgLT4KICByYW5kb20g KCkgPj49IGZ1bmN0aW9uCiAgfCBgRXJyb3IgZSAtPiBmYWlsIChGYWlsdXJlICJyYW5kb20iKQog IHwgYE9rIHJhbmRvbSAtPgogIE0xLnN0YXJ0IGNvbnNvbGUxIHJhbmRvbQo8PDw8Cgo+IEnigJls bCB0YWtlIGEgcXVpY2sgbG9vay4KPgo+IENoZWVycywKPiBEYXZlCj4KPiBbMV0gaHR0cHM6Ly9n aXRodWIuY29tL21pcmFnZS9taXJhZ2UtY2xvY2svYmxvYi9tYXN0ZXIvdW5peC9jbG9jay5tbGkK Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9T LWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpo dHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFn ZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 20:34:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 20:34: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 1XOumG-0001JC-4J; Tue, 02 Sep 2014 20:34:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOumF-0001J4-Cw for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 20:34:07 +0000 Received: from [85.158.143.35:48137] by server-2.bemta-4.messagelabs.com id E1/A5-04525-EB926045; Tue, 02 Sep 2014 20:34:06 +0000 X-Env-Sender: jacob.d.mitchell@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1409690043!13238984!1 X-Originating-IP: [209.85.192.41] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6538 invoked from network); 2 Sep 2014 20:34:04 -0000 Received: from mail-qg0-f41.google.com (HELO mail-qg0-f41.google.com) (209.85.192.41) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 20:34:04 -0000 Received: by mail-qg0-f41.google.com with SMTP id i50so7196067qgf.0 for ; Tue, 02 Sep 2014 13:34:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=bIEp83oM5KgKnI2E1POI8onE+68aIT6BBwX8sV/dA+c=; b=hsz8Ix45APLovQ9DBG9c6v62D1tFTwGqn9iMP+PNBzd2oP6ldAZS+nhLqtUtCmlD2D q4RnC8JXOwjS9oIsjtpE+UOw+VyWYBlXIXdKat5T5/FHBcYIZFJCli4dB5seEP9o0jEp TOL4YoK0FF0mrDNkujYmjHHZFisJ9bfunL1PUHxn6AH5lB1HQoRHE2z28zc0y4BjIY2f EFcJ6+EMsIoAQK32Wl/zvZV97E/xbKb6xSV3wR6cmkbAzp+TKJZDSkW9f4HOnhKQwErI pX1LRWE8BJy3kZScp+BnaB+6ZGy9qY8EFA9XM3LndhrfvMfz1OyBYMkEII7uGxTr8HEZ +nRw== X-Received: by 10.140.102.142 with SMTP id w14mr55348538qge.101.1409690043122; Tue, 02 Sep 2014 13:34:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.34 with HTTP; Tue, 2 Sep 2014 13:33:43 -0700 (PDT) In-Reply-To: References: From: Jacob Mitchell Date: Tue, 2 Sep 2014 13:33:43 -0700 Message-ID: To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org VGhhbmtzLCBEYXZlLgoKT24gVHVlLCBTZXAgMiwgMjAxNCBhdCAxOjA5IFBNLCBEYXZlIFNjb3R0 IDxEYXZlLlNjb3R0QGNpdHJpeC5jb20+IHdyb3RlOgo+IEhpLAo+Cj4gT24gMiBTZXAgMjAxNCwg YXQgMjA6NDgsIEphY29iIE1pdGNoZWxsIDxqYWNvYi5kLm1pdGNoZWxsQGdtYWlsLmNvbT4gd3Jv dGU6Cj4KPj4gR29hbDogcHJpbnQgdGhlIGN1cnJlbnQgdGltZSB0byB0aGUgY29uc29sZTsgcmVw ZWF0IHVudGlsIHRlcm1pbmF0aW9uLgo+Pgo+PiBJIHRoaW5rIEknbSBjbG9zZSwgYnV0IHdoZW4g SSBjYWxsICJtYWtlIiB0aGUgY29tcGlsZWQgbWFpbi5tbCBmaWxlCj4+IHJlc3VsdHMgaW4gYW4g IlVuYm91bmQgdmFsdWUgY2xvY2siIGVycm9yLiBSZWZlciB0bwo+PiBodHRwczovL2dpc3QuZ2l0 aHViLmNvbS9hbm9ueW1vdXMvOTBmNDEwN2NmNTAwOGIxMmQzNTYgZm9yIG15IHNvdXJjZQo+PiBj b2RlLCB0aGUgbWFpbi5tbCBmaWxlLCBhbmQgdGhlIGJ1aWxkIGxvZy4KPj4KPj4gQW55IHBvaW50 ZXJzPyBJIGhhdmVuJ3QgZm91bmQgYW55IHRlc3RzIG9yIHNhbXBsZSBjb2RlIHRvIGRlbW9uc3Ry YXRlCj4+IGhvdyB0byB1c2Ugbm9uLXBvbHltb3JwaGljIGZpcnN0LWNsYXNzIG1vZHVsZXMgbGlr ZSBDTE9DSywgVElNRSwgYW5kCj4+IFJBTkRPTS4KPgo+IEl0IGxvb2tzIHRvIG1lIGxpa2UgYSBt aXNtYXRjaCBiZXR3ZWVuIHRoZSBnZW5lcmF0ZWQgY29kZSAoaW4gbWFpbi5tbCkgYW5kIHRoZSBt aXJhZ2UtY2xvY2sgY29kZS4gVGhlIG90aGVyIGRldmljZXMgKGJsb2NrLCBuZXR3b3JrLCBjb25z b2xlKSBoYXZlIGEg4oCYY29ubmVjdOKAmSBmdW5jdGlvbiB0byBjb25uZWN0IHRvIGFuIGluc3Rh bmNlLCBidXQgdGhlIGNsb2NrWzFdIGlzIGEgc2luZ2xldG9uLiBTbyBJIHRoaW5rIHdlIGp1c3Qg bmVlZCB0byBvbWl0IGFsbCByZWZlcmVuY2VzIHRvIOKAnGNsb2Nr4oCdICh0aGUgaW5zdGFuY2Up IGluIHRoZSBnZW5lcmF0ZWQgZnJhZ21lbnQ6Cj4KPj4+Pj4KPiBtb2R1bGUgTTEgPSBVbmlrZXJu ZWwuTWFpbihDb25zb2xlKShDbG9jaykKPgo+IGxldCB0MSAoKSA9Cj4gICBjbG9jayAoKSA+Pj0g ZnVuY3Rpb24KPiAgIHwgYEVycm9yIGUgLT4gZmFpbCAoRmFpbHVyZSAiY2xvY2siKQo+ICAgfCBg T2sgY2xvY2sgLT4KPiAgIGNvbnNvbGUxICgpID4+PSBmdW5jdGlvbgo+ICAgfCBgRXJyb3IgZSAt PiBmYWlsIChGYWlsdXJlICJjb25zb2xlMSIpCj4gICB8IGBPayBjb25zb2xlMSAtPgo+ICAgTTEu c3RhcnQgY29uc29sZTEgY2xvY2sKPiA8PDw8Cj4KClRoZSBwcm9ibGVtIG1heSBleHRlbmQgdG8g Zmlyc3QtY2xhc3MgbW9kdWxlcyB0aGF0IGFyZW4ndCBERVZJQ0VzCihlLmcuIFJBTkRPTSkuIEkg cmFuIGludG8gdGhlIHNhbWUgc29ydCBvZiBlcnJvciB3aGVuIEkgdHJpZWQgcHJpbnRpbmcKYSBy YW5kb20gaW50IG9uIGVhY2ggbGluZSBpbnN0ZWFkIG9mIHRoZSBjdXJyZW50IHRpbWUuIFRoZSBj b2RlIEkKdHJpZWQgZm9sbG93czoKCj4+Pj4gKGNvbmZpZy5tbCkKb3BlbiBNaXJhZ2UKCmxldCBt YWluID0KICBmb3JlaWduICJVbmlrZXJuZWwuTWFpbiIgKGNvbnNvbGUgQC0+IHJhbmRvbSBALT4g am9iKQoKbGV0ICgpID0KICByZWdpc3RlciAiY29uc29sZSIgWyBtYWluICQgZGVmYXVsdF9jb25z b2xlICQgZGVmYXVsdF9yYW5kb20gXQo8PDw8CgoKPj4+PiAodW5pa2VybmVsLm1sKQpvcGVuIFYx Cm9wZW4gTHd0Cgptb2R1bGUgTWFpbiAoQzogQ09OU09MRSkoUkFORDogUkFORE9NKSA9IHN0cnVj dAoKbGV0IHN0YXJ0IGNvbnNvbGUgcmFuZG9tID0KICBSQU5ELnNlbGZfaW5pdCAoKSA7CiAgd2hp bGUgdHJ1ZSBkbwogICAgQy5sb2cgY29uc29sZSAoUHJpbnRmLnNwcmludGYgIiVkIiAoUkFORC5p bnQgMikpCiAgZG9uZSA7CiAgcmV0dXJuICgpCmVuZAo8PDw8CgoKPj4+PiBidWlsZCBlcnJvciAo dW5kZXIgVU5JWCBtb2RlKQpGaWxlICJtYWluLm1sIiwgbGluZSAyMCwgY2hhcmFjdGVycyAyLTg6 CkVycm9yOiBVbmJvdW5kIHZhbHVlIHJhbmRvbQpDb21tYW5kIGV4aXRlZCB3aXRoIGNvZGUgMi4K bWFrZTogKioqIFttYWluLm5hdGl2ZV0gRXJyb3IgMTAKPDw8PAoKCj4+Pj4gZ2VuZXJhdGVkIG1h aW4ubWwgKGV4Y2VycHQpCm1vZHVsZSBNMSA9IFVuaWtlcm5lbC5NYWluKENvbnNvbGUpKFJhbmRv bSkKCmxldCB0MSAoKSA9CiAgY29uc29sZTEgKCkgPj49IGZ1bmN0aW9uCiAgfCBgRXJyb3IgZSAt PiBmYWlsIChGYWlsdXJlICJjb25zb2xlMSIpCiAgfCBgT2sgY29uc29sZTEgLT4KICByYW5kb20g KCkgPj49IGZ1bmN0aW9uCiAgfCBgRXJyb3IgZSAtPiBmYWlsIChGYWlsdXJlICJyYW5kb20iKQog IHwgYE9rIHJhbmRvbSAtPgogIE0xLnN0YXJ0IGNvbnNvbGUxIHJhbmRvbQo8PDw8Cgo+IEnigJls bCB0YWtlIGEgcXVpY2sgbG9vay4KPgo+IENoZWVycywKPiBEYXZlCj4KPiBbMV0gaHR0cHM6Ly9n aXRodWIuY29tL21pcmFnZS9taXJhZ2UtY2xvY2svYmxvYi9tYXN0ZXIvdW5peC9jbG9jay5tbGkK Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCk1pcmFnZU9T LWRldmVsIG1haWxpbmcgbGlzdApNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZwpo dHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3RpbmZvL21pcmFn ZW9zLWRldmVsCg== From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 20:58:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 20:58:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOvAG-0001e2-4e; Tue, 02 Sep 2014 20:58:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOvAF-0001d7-7M for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 20:58:55 +0000 Received: from [193.109.254.147:37523] by server-12.bemta-14.messagelabs.com id 1B/F7-01461-E8F26045; Tue, 02 Sep 2014 20:58:54 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1409691533!13069517!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11972 invoked from network); 2 Sep 2014 20:58:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 20:58:53 -0000 X-IronPort-AV: E=Sophos;i="5.04,451,1406592000"; d="scan'208";a="24457649" From: Dave Scott To: Jacob Mitchell Thread-Topic: [MirageOS-devel] Help using V1.CLOCK Thread-Index: AQHPxucAEpqPkB2OD0WOVdll2dKMVJvuJCkAgAAG4YCAAAcCAA== Date: Tue, 2 Sep 2014 20:58:51 +0000 Message-ID: <1154A631-4D57-4616-BC4D-4204E8DBF4BC@citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <8181076E5D1C0D498962E1DB72D85E9A@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 2 Sep 2014, at 21:33, Jacob Mitchell wrote: > Thanks, Dave. > = > On Tue, Sep 2, 2014 at 1:09 PM, Dave Scott wrote: >> Hi, >> = >> On 2 Sep 2014, at 20:48, Jacob Mitchell wro= te: >> = >>> Goal: print the current time to the console; repeat until termination. >>> = >>> I think I'm close, but when I call "make" the compiled main.ml file >>> results in an "Unbound value clock" error. Refer to >>> https://gist.github.com/anonymous/90f4107cf5008b12d356 for my source >>> code, the main.ml file, and the build log. >>> = >>> Any pointers? I haven't found any tests or sample code to demonstrate >>> how to use non-polymorphic first-class modules like CLOCK, TIME, and >>> RANDOM. >> = >> It looks to me like a mismatch between the generated code (in main.ml) a= nd the mirage-clock code. The other devices (block, network, console) have = a =91connect=92 function to connect to an instance, but the clock[1] is a s= ingleton. So I think we just need to omit all references to =93clock=94 (th= e instance) in the generated fragment: >> = >>>>>> = >> module M1 =3D Unikernel.Main(Console)(Clock) >> = >> let t1 () =3D >> clock () >>=3D function >> | `Error e -> fail (Failure "clock") >> | `Ok clock -> >> console1 () >>=3D function >> | `Error e -> fail (Failure "console1") >> | `Ok console1 -> >> M1.start console1 clock >> <<<< >> = > = > The problem may extend to first-class modules that aren't DEVICEs > (e.g. RANDOM). I ran into the same sort of error when I tried printing > a random int on each line instead of the current time. The code I > tried follows: Hm, yes I see what you mean. I have a tentative fix here: https://github.com/mirage/mirage/pull/290 You could try it by opam remove mirage opam pin git://github.com/djs55/mirage#clock-random opam install mirage and then re-run =91mirage configure =97unix=92 Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 02 20:58:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 20:58:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOvAG-0001e2-4e; Tue, 02 Sep 2014 20:58:56 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOvAF-0001d7-7M for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 20:58:55 +0000 Received: from [193.109.254.147:37523] by server-12.bemta-14.messagelabs.com id 1B/F7-01461-E8F26045; Tue, 02 Sep 2014 20:58:54 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-10.tower-27.messagelabs.com!1409691533!13069517!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11972 invoked from network); 2 Sep 2014 20:58:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-10.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 20:58:53 -0000 X-IronPort-AV: E=Sophos;i="5.04,451,1406592000"; d="scan'208";a="24457649" From: Dave Scott To: Jacob Mitchell Thread-Topic: [MirageOS-devel] Help using V1.CLOCK Thread-Index: AQHPxucAEpqPkB2OD0WOVdll2dKMVJvuJCkAgAAG4YCAAAcCAA== Date: Tue, 2 Sep 2014 20:58:51 +0000 Message-ID: <1154A631-4D57-4616-BC4D-4204E8DBF4BC@citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <8181076E5D1C0D498962E1DB72D85E9A@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 2 Sep 2014, at 21:33, Jacob Mitchell wrote: > Thanks, Dave. > = > On Tue, Sep 2, 2014 at 1:09 PM, Dave Scott wrote: >> Hi, >> = >> On 2 Sep 2014, at 20:48, Jacob Mitchell wro= te: >> = >>> Goal: print the current time to the console; repeat until termination. >>> = >>> I think I'm close, but when I call "make" the compiled main.ml file >>> results in an "Unbound value clock" error. Refer to >>> https://gist.github.com/anonymous/90f4107cf5008b12d356 for my source >>> code, the main.ml file, and the build log. >>> = >>> Any pointers? I haven't found any tests or sample code to demonstrate >>> how to use non-polymorphic first-class modules like CLOCK, TIME, and >>> RANDOM. >> = >> It looks to me like a mismatch between the generated code (in main.ml) a= nd the mirage-clock code. The other devices (block, network, console) have = a =91connect=92 function to connect to an instance, but the clock[1] is a s= ingleton. So I think we just need to omit all references to =93clock=94 (th= e instance) in the generated fragment: >> = >>>>>> = >> module M1 =3D Unikernel.Main(Console)(Clock) >> = >> let t1 () =3D >> clock () >>=3D function >> | `Error e -> fail (Failure "clock") >> | `Ok clock -> >> console1 () >>=3D function >> | `Error e -> fail (Failure "console1") >> | `Ok console1 -> >> M1.start console1 clock >> <<<< >> = > = > The problem may extend to first-class modules that aren't DEVICEs > (e.g. RANDOM). I ran into the same sort of error when I tried printing > a random int on each line instead of the current time. The code I > tried follows: Hm, yes I see what you mean. I have a tentative fix here: https://github.com/mirage/mirage/pull/290 You could try it by opam remove mirage opam pin git://github.com/djs55/mirage#clock-random opam install mirage and then re-run =91mirage configure =97unix=92 Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 02 21:29:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 21:29: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 1XOveE-00025l-QH; Tue, 02 Sep 2014 21:29:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOveD-00025d-ET for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 21:29:53 +0000 Received: from [193.109.254.147:42653] by server-5.bemta-14.messagelabs.com id BB/89-28255-0D636045; Tue, 02 Sep 2014 21:29:52 +0000 X-Env-Sender: jacob.d.mitchell@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1409693389!13063610!1 X-Originating-IP: [209.85.192.42] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1150 invoked from network); 2 Sep 2014 21:29:50 -0000 Received: from mail-qg0-f42.google.com (HELO mail-qg0-f42.google.com) (209.85.192.42) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 21:29:50 -0000 Received: by mail-qg0-f42.google.com with SMTP id a108so7418785qge.1 for ; Tue, 02 Sep 2014 14:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=NiFrrlXJFDWU55c79GMV+RdBjJiYwzqvBkgNvDVHEfY=; b=07ILL57uRdgyU4HCZPxrc94OZBL7Iwjn1uK9jaxAg/NWNfJgE2UrG6hP/LoY1XAxBp Ik5TuY63fHIZZ5o6MbuxTEiq4Z/TIx4Bw5r/p9SY05ma3JbwKim94wuXqGMwzTiLInxa 309PiFz54lsxIysUZBig6Yaj+kp6ju4GfFmj6zyI9/947n1fYqVATlOmau/7Gnn/0WPw 21FDZcvDejqfPrcCdZTP6OFDVCXWdkJJG9KRR6tN1YWmjnR3pVI7S71EWXX7gSTWHuGn sUHGEBtGEJO5Oh+EOHTLRxGxkXotgoAdVHaIXHqnIHoVO2cDk81GBXnbvm5uspOR2krg GhKw== X-Received: by 10.140.34.164 with SMTP id l33mr54634805qgl.72.1409693389040; Tue, 02 Sep 2014 14:29:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.34 with HTTP; Tue, 2 Sep 2014 14:29:28 -0700 (PDT) In-Reply-To: <1154A631-4D57-4616-BC4D-4204E8DBF4BC@citrix.com> References: <1154A631-4D57-4616-BC4D-4204E8DBF4BC@citrix.com> From: Jacob Mitchell Date: Tue, 2 Sep 2014 14:29:28 -0700 Message-ID: To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gVHVlLCBTZXAgMiwgMjAxNCBhdCAxOjU4IFBNLCBEYXZlIFNjb3R0IDxEYXZlLlNjb3R0QGNp dHJpeC5jb20+IHdyb3RlOgo+Cj4gT24gMiBTZXAgMjAxNCwgYXQgMjE6MzMsIEphY29iIE1pdGNo ZWxsIDxqYWNvYi5kLm1pdGNoZWxsQGdtYWlsLmNvbT4gd3JvdGU6Cj4KPj4gVGhhbmtzLCBEYXZl Lgo+Pgo+PiBPbiBUdWUsIFNlcCAyLCAyMDE0IGF0IDE6MDkgUE0sIERhdmUgU2NvdHQgPERhdmUu U2NvdHRAY2l0cml4LmNvbT4gd3JvdGU6Cj4+PiBIaSwKPj4+Cj4+PiBPbiAyIFNlcCAyMDE0LCBh dCAyMDo0OCwgSmFjb2IgTWl0Y2hlbGwgPGphY29iLmQubWl0Y2hlbGxAZ21haWwuY29tPiB3cm90 ZToKPj4+Cj4+Pj4gR29hbDogcHJpbnQgdGhlIGN1cnJlbnQgdGltZSB0byB0aGUgY29uc29sZTsg cmVwZWF0IHVudGlsIHRlcm1pbmF0aW9uLgo+Pj4+Cj4+Pj4gSSB0aGluayBJJ20gY2xvc2UsIGJ1 dCB3aGVuIEkgY2FsbCAibWFrZSIgdGhlIGNvbXBpbGVkIG1haW4ubWwgZmlsZQo+Pj4+IHJlc3Vs dHMgaW4gYW4gIlVuYm91bmQgdmFsdWUgY2xvY2siIGVycm9yLiBSZWZlciB0bwo+Pj4+IGh0dHBz Oi8vZ2lzdC5naXRodWIuY29tL2Fub255bW91cy85MGY0MTA3Y2Y1MDA4YjEyZDM1NiBmb3IgbXkg c291cmNlCj4+Pj4gY29kZSwgdGhlIG1haW4ubWwgZmlsZSwgYW5kIHRoZSBidWlsZCBsb2cuCj4+ Pj4KPj4+PiBBbnkgcG9pbnRlcnM/IEkgaGF2ZW4ndCBmb3VuZCBhbnkgdGVzdHMgb3Igc2FtcGxl IGNvZGUgdG8gZGVtb25zdHJhdGUKPj4+PiBob3cgdG8gdXNlIG5vbi1wb2x5bW9ycGhpYyBmaXJz dC1jbGFzcyBtb2R1bGVzIGxpa2UgQ0xPQ0ssIFRJTUUsIGFuZAo+Pj4+IFJBTkRPTS4KPj4+Cj4+ PiBJdCBsb29rcyB0byBtZSBsaWtlIGEgbWlzbWF0Y2ggYmV0d2VlbiB0aGUgZ2VuZXJhdGVkIGNv ZGUgKGluIG1haW4ubWwpIGFuZCB0aGUgbWlyYWdlLWNsb2NrIGNvZGUuIFRoZSBvdGhlciBkZXZp Y2VzIChibG9jaywgbmV0d29yaywgY29uc29sZSkgaGF2ZSBhIOKAmGNvbm5lY3TigJkgZnVuY3Rp b24gdG8gY29ubmVjdCB0byBhbiBpbnN0YW5jZSwgYnV0IHRoZSBjbG9ja1sxXSBpcyBhIHNpbmds ZXRvbi4gU28gSSB0aGluayB3ZSBqdXN0IG5lZWQgdG8gb21pdCBhbGwgcmVmZXJlbmNlcyB0byDi gJxjbG9ja+KAnSAodGhlIGluc3RhbmNlKSBpbiB0aGUgZ2VuZXJhdGVkIGZyYWdtZW50Ogo+Pj4K Pj4+Pj4+Pgo+Pj4gbW9kdWxlIE0xID0gVW5pa2VybmVsLk1haW4oQ29uc29sZSkoQ2xvY2spCj4+ Pgo+Pj4gbGV0IHQxICgpID0KPj4+ICBjbG9jayAoKSA+Pj0gZnVuY3Rpb24KPj4+ICB8IGBFcnJv ciBlIC0+IGZhaWwgKEZhaWx1cmUgImNsb2NrIikKPj4+ICB8IGBPayBjbG9jayAtPgo+Pj4gIGNv bnNvbGUxICgpID4+PSBmdW5jdGlvbgo+Pj4gIHwgYEVycm9yIGUgLT4gZmFpbCAoRmFpbHVyZSAi Y29uc29sZTEiKQo+Pj4gIHwgYE9rIGNvbnNvbGUxIC0+Cj4+PiAgTTEuc3RhcnQgY29uc29sZTEg Y2xvY2sKPj4+IDw8PDwKPj4+Cj4+Cj4+IFRoZSBwcm9ibGVtIG1heSBleHRlbmQgdG8gZmlyc3Qt Y2xhc3MgbW9kdWxlcyB0aGF0IGFyZW4ndCBERVZJQ0VzCj4+IChlLmcuIFJBTkRPTSkuIEkgcmFu IGludG8gdGhlIHNhbWUgc29ydCBvZiBlcnJvciB3aGVuIEkgdHJpZWQgcHJpbnRpbmcKPj4gYSBy YW5kb20gaW50IG9uIGVhY2ggbGluZSBpbnN0ZWFkIG9mIHRoZSBjdXJyZW50IHRpbWUuIFRoZSBj b2RlIEkKPj4gdHJpZWQgZm9sbG93czoKPgo+IEhtLCB5ZXMgSSBzZWUgd2hhdCB5b3UgbWVhbi4K Pgo+IEkgaGF2ZSBhIHRlbnRhdGl2ZSBmaXggaGVyZToKPgo+IGh0dHBzOi8vZ2l0aHViLmNvbS9t aXJhZ2UvbWlyYWdlL3B1bGwvMjkwCj4KPiBZb3UgY291bGQgdHJ5IGl0IGJ5Cj4KPiBvcGFtIHJl bW92ZSBtaXJhZ2UKPiBvcGFtIHBpbiBnaXQ6Ly9naXRodWIuY29tL2RqczU1L21pcmFnZSNjbG9j ay1yYW5kb20KPiBvcGFtIGluc3RhbGwgbWlyYWdlCj4KPiBhbmQgdGhlbiByZS1ydW4g4oCYbWly YWdlIGNvbmZpZ3VyZSDigJR1bml44oCZCgpXb3JrcyBmb3IgbWUuIFRoZSBvbmx5IG1pbm9yIGFk anVzdG1lbnQgSSBoYWQgdG8gbWFrZSB3YXMgaW5zZXJ0aW5nCiJtaXJhZ2UiIGFmdGVyICJvcGFt IHBpbiIuCgpUaGFua3MgZm9yIHlvdXIgaGVscCEKCj4KPiBDaGVlcnMsCj4gRGF2ZQoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwg bWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9s aXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2 ZWwK From mirageos-devel-bounces@lists.xenproject.org Tue Sep 02 21:29:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 02 Sep 2014 21:29: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 1XOveE-00025l-QH; Tue, 02 Sep 2014 21:29:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XOveD-00025d-ET for mirageos-devel@lists.xenproject.org; Tue, 02 Sep 2014 21:29:53 +0000 Received: from [193.109.254.147:42653] by server-5.bemta-14.messagelabs.com id BB/89-28255-0D636045; Tue, 02 Sep 2014 21:29:52 +0000 X-Env-Sender: jacob.d.mitchell@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1409693389!13063610!1 X-Originating-IP: [209.85.192.42] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1150 invoked from network); 2 Sep 2014 21:29:50 -0000 Received: from mail-qg0-f42.google.com (HELO mail-qg0-f42.google.com) (209.85.192.42) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 2 Sep 2014 21:29:50 -0000 Received: by mail-qg0-f42.google.com with SMTP id a108so7418785qge.1 for ; Tue, 02 Sep 2014 14:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=NiFrrlXJFDWU55c79GMV+RdBjJiYwzqvBkgNvDVHEfY=; b=07ILL57uRdgyU4HCZPxrc94OZBL7Iwjn1uK9jaxAg/NWNfJgE2UrG6hP/LoY1XAxBp Ik5TuY63fHIZZ5o6MbuxTEiq4Z/TIx4Bw5r/p9SY05ma3JbwKim94wuXqGMwzTiLInxa 309PiFz54lsxIysUZBig6Yaj+kp6ju4GfFmj6zyI9/947n1fYqVATlOmau/7Gnn/0WPw 21FDZcvDejqfPrcCdZTP6OFDVCXWdkJJG9KRR6tN1YWmjnR3pVI7S71EWXX7gSTWHuGn sUHGEBtGEJO5Oh+EOHTLRxGxkXotgoAdVHaIXHqnIHoVO2cDk81GBXnbvm5uspOR2krg GhKw== X-Received: by 10.140.34.164 with SMTP id l33mr54634805qgl.72.1409693389040; Tue, 02 Sep 2014 14:29:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.87.34 with HTTP; Tue, 2 Sep 2014 14:29:28 -0700 (PDT) In-Reply-To: <1154A631-4D57-4616-BC4D-4204E8DBF4BC@citrix.com> References: <1154A631-4D57-4616-BC4D-4204E8DBF4BC@citrix.com> From: Jacob Mitchell Date: Tue, 2 Sep 2014 14:29:28 -0700 Message-ID: To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Help using V1.CLOCK X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gVHVlLCBTZXAgMiwgMjAxNCBhdCAxOjU4IFBNLCBEYXZlIFNjb3R0IDxEYXZlLlNjb3R0QGNp dHJpeC5jb20+IHdyb3RlOgo+Cj4gT24gMiBTZXAgMjAxNCwgYXQgMjE6MzMsIEphY29iIE1pdGNo ZWxsIDxqYWNvYi5kLm1pdGNoZWxsQGdtYWlsLmNvbT4gd3JvdGU6Cj4KPj4gVGhhbmtzLCBEYXZl Lgo+Pgo+PiBPbiBUdWUsIFNlcCAyLCAyMDE0IGF0IDE6MDkgUE0sIERhdmUgU2NvdHQgPERhdmUu U2NvdHRAY2l0cml4LmNvbT4gd3JvdGU6Cj4+PiBIaSwKPj4+Cj4+PiBPbiAyIFNlcCAyMDE0LCBh dCAyMDo0OCwgSmFjb2IgTWl0Y2hlbGwgPGphY29iLmQubWl0Y2hlbGxAZ21haWwuY29tPiB3cm90 ZToKPj4+Cj4+Pj4gR29hbDogcHJpbnQgdGhlIGN1cnJlbnQgdGltZSB0byB0aGUgY29uc29sZTsg cmVwZWF0IHVudGlsIHRlcm1pbmF0aW9uLgo+Pj4+Cj4+Pj4gSSB0aGluayBJJ20gY2xvc2UsIGJ1 dCB3aGVuIEkgY2FsbCAibWFrZSIgdGhlIGNvbXBpbGVkIG1haW4ubWwgZmlsZQo+Pj4+IHJlc3Vs dHMgaW4gYW4gIlVuYm91bmQgdmFsdWUgY2xvY2siIGVycm9yLiBSZWZlciB0bwo+Pj4+IGh0dHBz Oi8vZ2lzdC5naXRodWIuY29tL2Fub255bW91cy85MGY0MTA3Y2Y1MDA4YjEyZDM1NiBmb3IgbXkg c291cmNlCj4+Pj4gY29kZSwgdGhlIG1haW4ubWwgZmlsZSwgYW5kIHRoZSBidWlsZCBsb2cuCj4+ Pj4KPj4+PiBBbnkgcG9pbnRlcnM/IEkgaGF2ZW4ndCBmb3VuZCBhbnkgdGVzdHMgb3Igc2FtcGxl IGNvZGUgdG8gZGVtb25zdHJhdGUKPj4+PiBob3cgdG8gdXNlIG5vbi1wb2x5bW9ycGhpYyBmaXJz dC1jbGFzcyBtb2R1bGVzIGxpa2UgQ0xPQ0ssIFRJTUUsIGFuZAo+Pj4+IFJBTkRPTS4KPj4+Cj4+ PiBJdCBsb29rcyB0byBtZSBsaWtlIGEgbWlzbWF0Y2ggYmV0d2VlbiB0aGUgZ2VuZXJhdGVkIGNv ZGUgKGluIG1haW4ubWwpIGFuZCB0aGUgbWlyYWdlLWNsb2NrIGNvZGUuIFRoZSBvdGhlciBkZXZp Y2VzIChibG9jaywgbmV0d29yaywgY29uc29sZSkgaGF2ZSBhIOKAmGNvbm5lY3TigJkgZnVuY3Rp b24gdG8gY29ubmVjdCB0byBhbiBpbnN0YW5jZSwgYnV0IHRoZSBjbG9ja1sxXSBpcyBhIHNpbmds ZXRvbi4gU28gSSB0aGluayB3ZSBqdXN0IG5lZWQgdG8gb21pdCBhbGwgcmVmZXJlbmNlcyB0byDi gJxjbG9ja+KAnSAodGhlIGluc3RhbmNlKSBpbiB0aGUgZ2VuZXJhdGVkIGZyYWdtZW50Ogo+Pj4K Pj4+Pj4+Pgo+Pj4gbW9kdWxlIE0xID0gVW5pa2VybmVsLk1haW4oQ29uc29sZSkoQ2xvY2spCj4+ Pgo+Pj4gbGV0IHQxICgpID0KPj4+ICBjbG9jayAoKSA+Pj0gZnVuY3Rpb24KPj4+ICB8IGBFcnJv ciBlIC0+IGZhaWwgKEZhaWx1cmUgImNsb2NrIikKPj4+ICB8IGBPayBjbG9jayAtPgo+Pj4gIGNv bnNvbGUxICgpID4+PSBmdW5jdGlvbgo+Pj4gIHwgYEVycm9yIGUgLT4gZmFpbCAoRmFpbHVyZSAi Y29uc29sZTEiKQo+Pj4gIHwgYE9rIGNvbnNvbGUxIC0+Cj4+PiAgTTEuc3RhcnQgY29uc29sZTEg Y2xvY2sKPj4+IDw8PDwKPj4+Cj4+Cj4+IFRoZSBwcm9ibGVtIG1heSBleHRlbmQgdG8gZmlyc3Qt Y2xhc3MgbW9kdWxlcyB0aGF0IGFyZW4ndCBERVZJQ0VzCj4+IChlLmcuIFJBTkRPTSkuIEkgcmFu IGludG8gdGhlIHNhbWUgc29ydCBvZiBlcnJvciB3aGVuIEkgdHJpZWQgcHJpbnRpbmcKPj4gYSBy YW5kb20gaW50IG9uIGVhY2ggbGluZSBpbnN0ZWFkIG9mIHRoZSBjdXJyZW50IHRpbWUuIFRoZSBj b2RlIEkKPj4gdHJpZWQgZm9sbG93czoKPgo+IEhtLCB5ZXMgSSBzZWUgd2hhdCB5b3UgbWVhbi4K Pgo+IEkgaGF2ZSBhIHRlbnRhdGl2ZSBmaXggaGVyZToKPgo+IGh0dHBzOi8vZ2l0aHViLmNvbS9t aXJhZ2UvbWlyYWdlL3B1bGwvMjkwCj4KPiBZb3UgY291bGQgdHJ5IGl0IGJ5Cj4KPiBvcGFtIHJl bW92ZSBtaXJhZ2UKPiBvcGFtIHBpbiBnaXQ6Ly9naXRodWIuY29tL2RqczU1L21pcmFnZSNjbG9j ay1yYW5kb20KPiBvcGFtIGluc3RhbGwgbWlyYWdlCj4KPiBhbmQgdGhlbiByZS1ydW4g4oCYbWly YWdlIGNvbmZpZ3VyZSDigJR1bml44oCZCgpXb3JrcyBmb3IgbWUuIFRoZSBvbmx5IG1pbm9yIGFk anVzdG1lbnQgSSBoYWQgdG8gbWFrZSB3YXMgaW5zZXJ0aW5nCiJtaXJhZ2UiIGFmdGVyICJvcGFt IHBpbiIuCgpUaGFua3MgZm9yIHlvdXIgaGVscCEKCj4KPiBDaGVlcnMsCj4gRGF2ZQoKX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwg bWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9s aXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2 ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 08:06:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 08:06: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 1XP5Zt-0002La-EX; Wed, 03 Sep 2014 08:06:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP5Zj-0002L5-9E for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 08:06:04 +0000 Received: from [85.158.139.211:60324] by server-16.bemta-5.messagelabs.com id D7/31-01029-0EBC6045; Wed, 03 Sep 2014 08:05:52 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1409731548!12154388!1 X-Originating-IP: [209.85.218.53] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29270 invoked from network); 3 Sep 2014 08:05:49 -0000 Received: from mail-oi0-f53.google.com (HELO mail-oi0-f53.google.com) (209.85.218.53) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 08:05:49 -0000 Received: by mail-oi0-f53.google.com with SMTP id x69so154102oia.40 for ; Wed, 03 Sep 2014 01:05:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7NKTEb4iBo2gwbsHBIUX0aWGpCNxrKMTChcYTMqL4GE=; b=PlNbNAkzBCsUTJH0+LGr0XdJu1XqtXitpdeeq3BqLwIeAEmtKLaGWUqAI/55NS7LsG vA0VqimLyTcdLc8z4bhc+cu+IKgamahi4U/jQZANfd8Q64yI3dtZ3Uc/L6Du1QCBTP2/ dE/BzgHanvUwFMuA0qD+OLvfKMEbN3L7hK3NMrtPi4qkcn2JGpEuxrfjs3wcOSSNUUvt hqTLsTAxdvnefJ6QUct3G0xRn6GOLRUW4mEgs0HfR3PAGpyycponoYjwTSE3zy1z8pMk O9GvfpGxjJTApJZtGOn90Za2v2AEdjJAostRYOK5+FV0lgzWxEpbCyKnYz/BpSMDxhg7 ZiVA== MIME-Version: 1.0 X-Received: by 10.182.114.131 with SMTP id jg3mr36772507obb.9.1409731547806; Wed, 03 Sep 2014 01:05:47 -0700 (PDT) Received: by 10.76.20.105 with HTTP; Wed, 3 Sep 2014 01:05:47 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Sep 2014 09:05:47 +0100 Message-ID: From: Thomas Leonard To: Jon Crowcroft Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Interesting. I had to look at the things they did: - Calculating the checksum at the same time as copying the data: we now use checksum offloading to the hardware (or dom0), so we don't calculate the checksum at all. For UDP checksum is optional anyway and I think we skip it. - Remembering which application sent/received the previous UDP packet to avoid searching in the common case: might help, but we typically only have one application in Mirage anyway. In my UDP tests, I only testing sending. I need to look more closely at handling TCP acks. - BSD treated UDP sockets as being connected to a particular endpoint, and had to keep changing the address if the application specified the destination with each packet. Mirage already has the correct API. - Minimising privilege level changes and locking: these don't apply to Mirage since it's single-threaded and runs at a fixed level. - Pooling buffers to save on allocation. Could be useful. In general though, the bottleneck seems to be the Xen API rather than performance problems within Mirage. In all cases, we spend a lot of time blocking and/or dealing with Xen grants. On 2 September 2014 16:04, Jon Crowcroft wrote: > by the way, back in the day, someone did some work on UDP in BSD unix to get > it to not go so slow (see > A Faster UDP > by partidge and pink > http://dl.acm.org/citation.cfm?id=169943 > but i dont think anyone picked up on those optimisations in the Linux world > (though obviously did for TCP) - not sure tho! > > > On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard wrote: >> >> On 21 August 2014 15:09, Thomas Gazagnaire wrote: >> >>> Cool -- it would be great to polish up a tool like this. >> >> >> >> Yes, I think there's a lot we could do here. I've written up the >> >> profiling I've done so far here: >> >> >> >> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ >> >> >> >> The graphs are quite interesting - if people familiar with the code >> >> could explain what's going on (especially with the block device) that >> >> would be great! >> > >> > I'm settting up a 4.01 switch with profiling on. >> >> Thanks! >> >> > Do you think the -fno-omit-frame-pointer configure options could also >> > help to have more precise profiling information? >> >> I'm not sure it would help. The problems currently are: >> >> 1. We can't tell when a function returns until the next one is called. >> 2. Tail calls look like the function returned first. >> 3. For recursive calls, we can't tell which frame is the caller. (e.g. >> foo calls foo and foo calls bar, but we don't know which foo >> activation called bar). >> >> We could guess (3) by looking at the stack pointer. But it wouldn't >> work for tail calls, since the stack doesn't grow and if we solved (1) >> and (2) then we'd get (3) for free. >> >> I guess it wouldn't be hard to make the compiler call a trace function >> on every return / before every tail call. >> >> The frame pointer would be useful if we didn't have tracing but wanted >> a backtrace. >> >> > Thomas >> > >> >> >> >> Overall, the changes increased the queuing service's download rate >> >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit >> >> disappointing. >> >> >> >> >> >> -- >> >> Dr Thomas Leonard http://0install.net/ >> >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> >> >> >> _______________________________________________ >> >> MirageOS-devel mailing list >> >> MirageOS-devel@lists.xenproject.org >> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > >> >> >> >> -- >> Dr Thomas Leonard http://0install.net/ >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel 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 Sep 03 08:06:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 08:06: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 1XP5Zt-0002La-EX; Wed, 03 Sep 2014 08:06:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP5Zj-0002L5-9E for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 08:06:04 +0000 Received: from [85.158.139.211:60324] by server-16.bemta-5.messagelabs.com id D7/31-01029-0EBC6045; Wed, 03 Sep 2014 08:05:52 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1409731548!12154388!1 X-Originating-IP: [209.85.218.53] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29270 invoked from network); 3 Sep 2014 08:05:49 -0000 Received: from mail-oi0-f53.google.com (HELO mail-oi0-f53.google.com) (209.85.218.53) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 08:05:49 -0000 Received: by mail-oi0-f53.google.com with SMTP id x69so154102oia.40 for ; Wed, 03 Sep 2014 01:05:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7NKTEb4iBo2gwbsHBIUX0aWGpCNxrKMTChcYTMqL4GE=; b=PlNbNAkzBCsUTJH0+LGr0XdJu1XqtXitpdeeq3BqLwIeAEmtKLaGWUqAI/55NS7LsG vA0VqimLyTcdLc8z4bhc+cu+IKgamahi4U/jQZANfd8Q64yI3dtZ3Uc/L6Du1QCBTP2/ dE/BzgHanvUwFMuA0qD+OLvfKMEbN3L7hK3NMrtPi4qkcn2JGpEuxrfjs3wcOSSNUUvt hqTLsTAxdvnefJ6QUct3G0xRn6GOLRUW4mEgs0HfR3PAGpyycponoYjwTSE3zy1z8pMk O9GvfpGxjJTApJZtGOn90Za2v2AEdjJAostRYOK5+FV0lgzWxEpbCyKnYz/BpSMDxhg7 ZiVA== MIME-Version: 1.0 X-Received: by 10.182.114.131 with SMTP id jg3mr36772507obb.9.1409731547806; Wed, 03 Sep 2014 01:05:47 -0700 (PDT) Received: by 10.76.20.105 with HTTP; Wed, 3 Sep 2014 01:05:47 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Sep 2014 09:05:47 +0100 Message-ID: From: Thomas Leonard To: Jon Crowcroft Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Interesting. I had to look at the things they did: - Calculating the checksum at the same time as copying the data: we now use checksum offloading to the hardware (or dom0), so we don't calculate the checksum at all. For UDP checksum is optional anyway and I think we skip it. - Remembering which application sent/received the previous UDP packet to avoid searching in the common case: might help, but we typically only have one application in Mirage anyway. In my UDP tests, I only testing sending. I need to look more closely at handling TCP acks. - BSD treated UDP sockets as being connected to a particular endpoint, and had to keep changing the address if the application specified the destination with each packet. Mirage already has the correct API. - Minimising privilege level changes and locking: these don't apply to Mirage since it's single-threaded and runs at a fixed level. - Pooling buffers to save on allocation. Could be useful. In general though, the bottleneck seems to be the Xen API rather than performance problems within Mirage. In all cases, we spend a lot of time blocking and/or dealing with Xen grants. On 2 September 2014 16:04, Jon Crowcroft wrote: > by the way, back in the day, someone did some work on UDP in BSD unix to get > it to not go so slow (see > A Faster UDP > by partidge and pink > http://dl.acm.org/citation.cfm?id=169943 > but i dont think anyone picked up on those optimisations in the Linux world > (though obviously did for TCP) - not sure tho! > > > On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard wrote: >> >> On 21 August 2014 15:09, Thomas Gazagnaire wrote: >> >>> Cool -- it would be great to polish up a tool like this. >> >> >> >> Yes, I think there's a lot we could do here. I've written up the >> >> profiling I've done so far here: >> >> >> >> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ >> >> >> >> The graphs are quite interesting - if people familiar with the code >> >> could explain what's going on (especially with the block device) that >> >> would be great! >> > >> > I'm settting up a 4.01 switch with profiling on. >> >> Thanks! >> >> > Do you think the -fno-omit-frame-pointer configure options could also >> > help to have more precise profiling information? >> >> I'm not sure it would help. The problems currently are: >> >> 1. We can't tell when a function returns until the next one is called. >> 2. Tail calls look like the function returned first. >> 3. For recursive calls, we can't tell which frame is the caller. (e.g. >> foo calls foo and foo calls bar, but we don't know which foo >> activation called bar). >> >> We could guess (3) by looking at the stack pointer. But it wouldn't >> work for tail calls, since the stack doesn't grow and if we solved (1) >> and (2) then we'd get (3) for free. >> >> I guess it wouldn't be hard to make the compiler call a trace function >> on every return / before every tail call. >> >> The frame pointer would be useful if we didn't have tracing but wanted >> a backtrace. >> >> > Thomas >> > >> >> >> >> Overall, the changes increased the queuing service's download rate >> >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit >> >> disappointing. >> >> >> >> >> >> -- >> >> Dr Thomas Leonard http://0install.net/ >> >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> >> >> >> _______________________________________________ >> >> MirageOS-devel mailing list >> >> MirageOS-devel@lists.xenproject.org >> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > >> >> >> >> -- >> Dr Thomas Leonard http://0install.net/ >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel 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 Sep 03 08:59:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 08:59: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 1XP6PM-00042P-KO; Wed, 03 Sep 2014 08:59:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP6PM-00041q-1j for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 08:59:16 +0000 Received: from [85.158.143.35:16486] by server-3.bemta-4.messagelabs.com id CE/B6-06192-368D6045; Wed, 03 Sep 2014 08:59:15 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1409734753!13275763!1 X-Originating-IP: [209.85.219.42] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13030 invoked from network); 3 Sep 2014 08:59:14 -0000 Received: from mail-oa0-f42.google.com (HELO mail-oa0-f42.google.com) (209.85.219.42) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 08:59:14 -0000 Received: by mail-oa0-f42.google.com with SMTP id m1so5746656oag.15 for ; Wed, 03 Sep 2014 01:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8NqdHIPHvrm3bQZUK22zPfbJjHfrGtxvajgmBpM/tDc=; b=wC5F3tJZDKzmK8jyjxJ08jEBgSpMp8WUSaajrxeUrAYOSzKVVRow1VMtbpMn1X1kN9 5xYCVSgf+8DsriEo5uj0DyhBx2oDCwQ3LCF9CD4q4QtZkZJdZdiUiYphMKC4XNzZ2AdL aWcnbkwcJm6YtT1Ji/BYZ3IkT+b+4sVKspvheILJNyDGWwVFJ2B9zyWpHaR/D/MPNgVn MHneJHR3CNhYBtz5RYrGmMdNTGSxzAPKSJ+qNeKvgcFp7xZQ88tgfxH2YX3ZKxVuqR61 xi6jhnFbwPJF4UCwR0Dnz8keQwc5R3ZCk/EjUAoIWDp0THx5cybuncwYULVkrCq8KZ70 MTVQ== MIME-Version: 1.0 X-Received: by 10.182.142.67 with SMTP id ru3mr37299449obb.15.1409734753071; Wed, 03 Sep 2014 01:59:13 -0700 (PDT) Received: by 10.76.20.105 with HTTP; Wed, 3 Sep 2014 01:59:13 -0700 (PDT) In-Reply-To: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> Date: Wed, 3 Sep 2014 09:59:13 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19 August 2014 20:28, Anil Madhavapeddy wrote: > On 19 Aug 2014, at 14:26, Thomas Gazagnaire wrote: > >>>> Looks good -- since V2.mli isn't tagged yet, this can just extend the call >>>> to `write` instead of having a `write2`. >>> >>> I actually tried that first, but it makes V1 incompatible with V2 >>> which complicates things a bit. As it is, if you have a V2 module you >>> can use it with anything that wants a V1 type, which makes upgrading >>> easier. >> >> I'm not too worry about that, as we need to fix the error type definition at one point as well (and the FS module type) >> >>>> However, would it be better to >>>> define an interface flags type in `NETWORK`, and just let the `write` call >>>> supply a list of flags? That would permit easier extension to other >>>> offloads in the future. >>> >>> Yes, probably. Should the flags type be abstract? >> >> A possibility might be to define a record 'flag' with at least one field called "checksum". Not sure too much abstraction is a good thing here. Presumably that will break existing code when we add more flags. Is that OK? > Agreed on both counts... OK, but in that case how do we upgrade to the V2 API? Currently, if you ask mirage for e.g. a "network" then you get a V1 NETWORK. If V2 extends V1 then it can just give you a V2 NETWORK and everything still works, which was the path I took for testing the checksums. But if they're not compatible (and I agree they shouldn't need to be) then more things will have to change. How will I ask mirage for a V1 vs V2 NETWORK? Like this? let main = foreign "Unikernel.Main" (console2 @-> network2 @-> job) -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel 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 Sep 03 08:59:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 08:59: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 1XP6PM-00042P-KO; Wed, 03 Sep 2014 08:59:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP6PM-00041q-1j for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 08:59:16 +0000 Received: from [85.158.143.35:16486] by server-3.bemta-4.messagelabs.com id CE/B6-06192-368D6045; Wed, 03 Sep 2014 08:59:15 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1409734753!13275763!1 X-Originating-IP: [209.85.219.42] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13030 invoked from network); 3 Sep 2014 08:59:14 -0000 Received: from mail-oa0-f42.google.com (HELO mail-oa0-f42.google.com) (209.85.219.42) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 08:59:14 -0000 Received: by mail-oa0-f42.google.com with SMTP id m1so5746656oag.15 for ; Wed, 03 Sep 2014 01:59:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8NqdHIPHvrm3bQZUK22zPfbJjHfrGtxvajgmBpM/tDc=; b=wC5F3tJZDKzmK8jyjxJ08jEBgSpMp8WUSaajrxeUrAYOSzKVVRow1VMtbpMn1X1kN9 5xYCVSgf+8DsriEo5uj0DyhBx2oDCwQ3LCF9CD4q4QtZkZJdZdiUiYphMKC4XNzZ2AdL aWcnbkwcJm6YtT1Ji/BYZ3IkT+b+4sVKspvheILJNyDGWwVFJ2B9zyWpHaR/D/MPNgVn MHneJHR3CNhYBtz5RYrGmMdNTGSxzAPKSJ+qNeKvgcFp7xZQ88tgfxH2YX3ZKxVuqR61 xi6jhnFbwPJF4UCwR0Dnz8keQwc5R3ZCk/EjUAoIWDp0THx5cybuncwYULVkrCq8KZ70 MTVQ== MIME-Version: 1.0 X-Received: by 10.182.142.67 with SMTP id ru3mr37299449obb.15.1409734753071; Wed, 03 Sep 2014 01:59:13 -0700 (PDT) Received: by 10.76.20.105 with HTTP; Wed, 3 Sep 2014 01:59:13 -0700 (PDT) In-Reply-To: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> Date: Wed, 3 Sep 2014 09:59:13 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19 August 2014 20:28, Anil Madhavapeddy wrote: > On 19 Aug 2014, at 14:26, Thomas Gazagnaire wrote: > >>>> Looks good -- since V2.mli isn't tagged yet, this can just extend the call >>>> to `write` instead of having a `write2`. >>> >>> I actually tried that first, but it makes V1 incompatible with V2 >>> which complicates things a bit. As it is, if you have a V2 module you >>> can use it with anything that wants a V1 type, which makes upgrading >>> easier. >> >> I'm not too worry about that, as we need to fix the error type definition at one point as well (and the FS module type) >> >>>> However, would it be better to >>>> define an interface flags type in `NETWORK`, and just let the `write` call >>>> supply a list of flags? That would permit easier extension to other >>>> offloads in the future. >>> >>> Yes, probably. Should the flags type be abstract? >> >> A possibility might be to define a record 'flag' with at least one field called "checksum". Not sure too much abstraction is a good thing here. Presumably that will break existing code when we add more flags. Is that OK? > Agreed on both counts... OK, but in that case how do we upgrade to the V2 API? Currently, if you ask mirage for e.g. a "network" then you get a V1 NETWORK. If V2 extends V1 then it can just give you a V2 NETWORK and everything still works, which was the path I took for testing the checksums. But if they're not compatible (and I agree they shouldn't need to be) then more things will have to change. How will I ask mirage for a V1 vs V2 NETWORK? Like this? let main = foreign "Unikernel.Main" (console2 @-> network2 @-> job) -- Dr Thomas Leonard http://0install.net/ GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA _______________________________________________ MirageOS-devel 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 Sep 03 09:23:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 09:23: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 1XP6n2-00055L-7F; Wed, 03 Sep 2014 09:23:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP6n1-00055G-FX for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 09:23:43 +0000 Received: from [85.158.139.211:51233] by server-11.bemta-5.messagelabs.com id DC/EF-11011-E1ED6045; Wed, 03 Sep 2014 09:23:42 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1409736218!12170295!1 X-Originating-IP: [209.85.216.51] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25030 invoked from network); 3 Sep 2014 09:23:39 -0000 Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com) (209.85.216.51) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 09:23:39 -0000 Received: by mail-qa0-f51.google.com with SMTP id j7so7385848qaq.38 for ; Wed, 03 Sep 2014 02:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=azVo8FAdrRDruPlNnTNn37V2OduBMsCCOuYJjJmHhO4=; b=gtOhaR69T9HpIXYW0J7rWQiMNg1i71M0Cf8OYwZjsN+L7ZyG9apFNtQL6BGHYdqreL emSQF767cMoDhh8vKrP42XFJhLZoEPqdTbmnIBXSqN/QNMFWa9b47+6/GSgehUrqQXhe PlZntgxIznP1hj+zmgb0ORWUJHAByR4RSgEv9dsxYUAsNFyPb8yspQaPM83gHlweFcnR Y3B8absZfmU1zgo7fEWX3kBXYETLvYRn3qtrok5WiHYcwPG9tS0lL62yaIBjEc6KaPII KXbJRCrt0ogiJ1MzbumtQZvGVoI5Xl5IFmXnL8/z8gYNyazcW0SJ9kWTwoHRi9PYUkFZ jbZw== MIME-Version: 1.0 X-Received: by 10.224.128.9 with SMTP id i9mr64742975qas.50.1409736217878; Wed, 03 Sep 2014 02:23:37 -0700 (PDT) Received: by 10.140.109.133 with HTTP; Wed, 3 Sep 2014 02:23:37 -0700 (PDT) Received: by 10.140.109.133 with HTTP; Wed, 3 Sep 2014 02:23:37 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Sep 2014 10:23:37 +0100 X-Google-Sender-Auth: 8KTXLTYAuJUV-fwWDgz9iB4LiOE Message-ID: From: Jon Crowcroft To: Thomas Leonard Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6825728363437946598==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6825728363437946598== Content-Type: multipart/alternative; boundary=001a11c2cafc7e841f050225ca11 --001a11c2cafc7e841f050225ca11 Content-Type: text/plain; charset=UTF-8 I guessed as much....good to know tho On Sep 3, 2014 10:05 AM, "Thomas Leonard" wrote: > Interesting. I had to look at the things they did: > > - Calculating the checksum at the same time as copying the data: we > now use checksum offloading to the hardware (or dom0), so we don't > calculate the checksum at all. For UDP checksum is optional anyway and > I think we skip it. > > - Remembering which application sent/received the previous UDP packet > to avoid searching in the common case: might help, but we typically > only have one application in Mirage anyway. In my UDP tests, I only > testing sending. I need to look more closely at handling TCP acks. > > - BSD treated UDP sockets as being connected to a particular endpoint, > and had to keep changing the address if the application specified the > destination with each packet. Mirage already has the correct API. > > - Minimising privilege level changes and locking: these don't apply to > Mirage since it's single-threaded and runs at a fixed level. > > - Pooling buffers to save on allocation. Could be useful. > > In general though, the bottleneck seems to be the Xen API rather than > performance problems within Mirage. In all cases, we spend a lot of > time blocking and/or dealing with Xen grants. > > > On 2 September 2014 16:04, Jon Crowcroft > wrote: > > by the way, back in the day, someone did some work on UDP in BSD unix to > get > > it to not go so slow (see > > A Faster UDP > > by partidge and pink > > http://dl.acm.org/citation.cfm?id=169943 > > but i dont think anyone picked up on those optimisations in the Linux > world > > (though obviously did for TCP) - not sure tho! > > > > > > On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard > wrote: > >> > >> On 21 August 2014 15:09, Thomas Gazagnaire > wrote: > >> >>> Cool -- it would be great to polish up a tool like this. > >> >> > >> >> Yes, I think there's a lot we could do here. I've written up the > >> >> profiling I've done so far here: > >> >> > >> >> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ > >> >> > >> >> The graphs are quite interesting - if people familiar with the code > >> >> could explain what's going on (especially with the block device) that > >> >> would be great! > >> > > >> > I'm settting up a 4.01 switch with profiling on. > >> > >> Thanks! > >> > >> > Do you think the -fno-omit-frame-pointer configure options could also > >> > help to have more precise profiling information? > >> > >> I'm not sure it would help. The problems currently are: > >> > >> 1. We can't tell when a function returns until the next one is called. > >> 2. Tail calls look like the function returned first. > >> 3. For recursive calls, we can't tell which frame is the caller. (e.g. > >> foo calls foo and foo calls bar, but we don't know which foo > >> activation called bar). > >> > >> We could guess (3) by looking at the stack pointer. But it wouldn't > >> work for tail calls, since the stack doesn't grow and if we solved (1) > >> and (2) then we'd get (3) for free. > >> > >> I guess it wouldn't be hard to make the compiler call a trace function > >> on every return / before every tail call. > >> > >> The frame pointer would be useful if we didn't have tracing but wanted > >> a backtrace. > >> > >> > Thomas > >> > > >> >> > >> >> Overall, the changes increased the queuing service's download rate > >> >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit > >> >> disappointing. > >> >> > >> >> > >> >> -- > >> >> Dr Thomas Leonard http://0install.net/ > >> >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > >> >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > >> >> > >> >> _______________________________________________ > >> >> MirageOS-devel mailing list > >> >> MirageOS-devel@lists.xenproject.org > >> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > >> > > >> > >> > >> > >> -- > >> Dr Thomas Leonard http://0install.net/ > >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > >> > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > --001a11c2cafc7e841f050225ca11 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I guessed as much....good to know tho

On Sep 3, 2014 10:05 AM, "Thomas Leonard&qu= ot; <talex5@gmail.com> wrote:=
Interesting. I had to look at the things they did:

- Calculating the checksum at the same time as copying the data: we
now use checksum offloading to the hardware (or dom0), so we don't
calculate the checksum at all. For UDP checksum is optional anyway and
I think we skip it.

- Remembering which application sent/received the previous UDP packet
to avoid searching in the common case: might help, but we typically
only have one application in Mirage anyway. In my UDP tests, I only
testing sending. I need to look more closely at handling TCP acks.

- BSD treated UDP sockets as being connected to a particular endpoint,
and had to keep changing the address if the application specified the
destination with each packet. Mirage already has the correct API.

- Minimising privilege level changes and locking: these don't apply to<= br> Mirage since it's single-threaded and runs at a fixed level.

- Pooling buffers to save on allocation. Could be useful.

In general though, the bottleneck seems to be the Xen API rather than
performance problems within Mirage. In all cases, we spend a lot of
time blocking and/or dealing with Xen grants.


On 2 September 2014 16:04, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> wrote:
> by the way, back in the day, someone did some work on UDP in BSD unix = to get
> it to not go so slow (see
> A Faster UDP
> by partidge and pink
> http://dl.acm.org/citation.cfm?id=3D169943
> but i dont think anyone picked up on those optimisations in the Linux = world
> (though obviously did for TCP) - not sure tho!
>
>
> On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard <talex5@gmail.com> wrote:
>>
>> On 21 August 2014 15:09, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
>> >>> Cool -- it would be great to polish up a tool like th= is.
>> >>
>> >> Yes, I think there's a lot we could do here. I've= written up the
>> >> profiling I've done so far here:
>> >>
>> >> http://roscidus.com/blog/blog/2014/= 08/15/optimising-the-unikernel/
>> >>
>> >> The graphs are quite interesting - if people familiar wit= h the code
>> >> could explain what's going on (especially with the bl= ock device) that
>> >> would be great!
>> >
>> > I'm settting up a 4.01 switch with profiling on.
>>
>> Thanks!
>>
>> > Do you think the -fno-omit-frame-pointer configure options co= uld also
>> > help to have more precise profiling information?
>>
>> I'm not sure it would help. The problems currently are:
>>
>> 1. We can't tell when a function returns until the next one is= called.
>> 2. Tail calls look like the function returned first.
>> 3. For recursive calls, we can't tell which frame is the calle= r. (e.g.
>> foo calls foo and foo calls bar, but we don't know which foo >> activation called bar).
>>
>> We could guess (3) by looking at the stack pointer. But it wouldn&= #39;t
>> work for tail calls, since the stack doesn't grow and if we so= lved (1)
>> and (2) then we'd get (3) for free.
>>
>> I guess it wouldn't be hard to make the compiler call a trace = function
>> on every return / before every tail call.
>>
>> The frame pointer would be useful if we didn't have tracing bu= t wanted
>> a backtrace.
>>
>> > Thomas
>> >
>> >>
>> >> Overall, the changes increased the queuing service's = download rate
>> >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bi= t
>> >> disappointing.
>> >>
>> >>
>> >> --
>> >> Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
>> >> GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3= CC1
>> >> GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D= 8BA
>> >>
>> >> _______________________________________________
>> >> MirageOS-devel mailing list
>> >> Mi= rageOS-devel@lists.xenproject.org
>> >> http://lists.xenproject.org/cgi-bi= n/mailman/listinfo/mirageos-devel
>> >
>>
>>
>>
>> --
>> Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
>> GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
>> GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA
>>
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-de= vel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>
>



--
Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA
--001a11c2cafc7e841f050225ca11-- --===============6825728363437946598== 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 --===============6825728363437946598==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 09:23:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 09:23: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 1XP6n2-00055L-7F; Wed, 03 Sep 2014 09:23:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XP6n1-00055G-FX for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 09:23:43 +0000 Received: from [85.158.139.211:51233] by server-11.bemta-5.messagelabs.com id DC/EF-11011-E1ED6045; Wed, 03 Sep 2014 09:23:42 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1409736218!12170295!1 X-Originating-IP: [209.85.216.51] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25030 invoked from network); 3 Sep 2014 09:23:39 -0000 Received: from mail-qa0-f51.google.com (HELO mail-qa0-f51.google.com) (209.85.216.51) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 09:23:39 -0000 Received: by mail-qa0-f51.google.com with SMTP id j7so7385848qaq.38 for ; Wed, 03 Sep 2014 02:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=azVo8FAdrRDruPlNnTNn37V2OduBMsCCOuYJjJmHhO4=; b=gtOhaR69T9HpIXYW0J7rWQiMNg1i71M0Cf8OYwZjsN+L7ZyG9apFNtQL6BGHYdqreL emSQF767cMoDhh8vKrP42XFJhLZoEPqdTbmnIBXSqN/QNMFWa9b47+6/GSgehUrqQXhe PlZntgxIznP1hj+zmgb0ORWUJHAByR4RSgEv9dsxYUAsNFyPb8yspQaPM83gHlweFcnR Y3B8absZfmU1zgo7fEWX3kBXYETLvYRn3qtrok5WiHYcwPG9tS0lL62yaIBjEc6KaPII KXbJRCrt0ogiJ1MzbumtQZvGVoI5Xl5IFmXnL8/z8gYNyazcW0SJ9kWTwoHRi9PYUkFZ jbZw== MIME-Version: 1.0 X-Received: by 10.224.128.9 with SMTP id i9mr64742975qas.50.1409736217878; Wed, 03 Sep 2014 02:23:37 -0700 (PDT) Received: by 10.140.109.133 with HTTP; Wed, 3 Sep 2014 02:23:37 -0700 (PDT) Received: by 10.140.109.133 with HTTP; Wed, 3 Sep 2014 02:23:37 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Sep 2014 10:23:37 +0100 X-Google-Sender-Auth: 8KTXLTYAuJUV-fwWDgz9iB4LiOE Message-ID: From: Jon Crowcroft To: Thomas Leonard Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6825728363437946598==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6825728363437946598== Content-Type: multipart/alternative; boundary=001a11c2cafc7e841f050225ca11 --001a11c2cafc7e841f050225ca11 Content-Type: text/plain; charset=UTF-8 I guessed as much....good to know tho On Sep 3, 2014 10:05 AM, "Thomas Leonard" wrote: > Interesting. I had to look at the things they did: > > - Calculating the checksum at the same time as copying the data: we > now use checksum offloading to the hardware (or dom0), so we don't > calculate the checksum at all. For UDP checksum is optional anyway and > I think we skip it. > > - Remembering which application sent/received the previous UDP packet > to avoid searching in the common case: might help, but we typically > only have one application in Mirage anyway. In my UDP tests, I only > testing sending. I need to look more closely at handling TCP acks. > > - BSD treated UDP sockets as being connected to a particular endpoint, > and had to keep changing the address if the application specified the > destination with each packet. Mirage already has the correct API. > > - Minimising privilege level changes and locking: these don't apply to > Mirage since it's single-threaded and runs at a fixed level. > > - Pooling buffers to save on allocation. Could be useful. > > In general though, the bottleneck seems to be the Xen API rather than > performance problems within Mirage. In all cases, we spend a lot of > time blocking and/or dealing with Xen grants. > > > On 2 September 2014 16:04, Jon Crowcroft > wrote: > > by the way, back in the day, someone did some work on UDP in BSD unix to > get > > it to not go so slow (see > > A Faster UDP > > by partidge and pink > > http://dl.acm.org/citation.cfm?id=169943 > > but i dont think anyone picked up on those optimisations in the Linux > world > > (though obviously did for TCP) - not sure tho! > > > > > > On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard > wrote: > >> > >> On 21 August 2014 15:09, Thomas Gazagnaire > wrote: > >> >>> Cool -- it would be great to polish up a tool like this. > >> >> > >> >> Yes, I think there's a lot we could do here. I've written up the > >> >> profiling I've done so far here: > >> >> > >> >> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ > >> >> > >> >> The graphs are quite interesting - if people familiar with the code > >> >> could explain what's going on (especially with the block device) that > >> >> would be great! > >> > > >> > I'm settting up a 4.01 switch with profiling on. > >> > >> Thanks! > >> > >> > Do you think the -fno-omit-frame-pointer configure options could also > >> > help to have more precise profiling information? > >> > >> I'm not sure it would help. The problems currently are: > >> > >> 1. We can't tell when a function returns until the next one is called. > >> 2. Tail calls look like the function returned first. > >> 3. For recursive calls, we can't tell which frame is the caller. (e.g. > >> foo calls foo and foo calls bar, but we don't know which foo > >> activation called bar). > >> > >> We could guess (3) by looking at the stack pointer. But it wouldn't > >> work for tail calls, since the stack doesn't grow and if we solved (1) > >> and (2) then we'd get (3) for free. > >> > >> I guess it wouldn't be hard to make the compiler call a trace function > >> on every return / before every tail call. > >> > >> The frame pointer would be useful if we didn't have tracing but wanted > >> a backtrace. > >> > >> > Thomas > >> > > >> >> > >> >> Overall, the changes increased the queuing service's download rate > >> >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bit > >> >> disappointing. > >> >> > >> >> > >> >> -- > >> >> Dr Thomas Leonard http://0install.net/ > >> >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > >> >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > >> >> > >> >> _______________________________________________ > >> >> MirageOS-devel mailing list > >> >> MirageOS-devel@lists.xenproject.org > >> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > >> > > >> > >> > >> > >> -- > >> Dr Thomas Leonard http://0install.net/ > >> GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > >> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > >> > >> _______________________________________________ > >> MirageOS-devel mailing list > >> MirageOS-devel@lists.xenproject.org > >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > > > -- > Dr Thomas Leonard http://0install.net/ > GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 > GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA > --001a11c2cafc7e841f050225ca11 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I guessed as much....good to know tho

On Sep 3, 2014 10:05 AM, "Thomas Leonard&qu= ot; <talex5@gmail.com> wrote:=
Interesting. I had to look at the things they did:

- Calculating the checksum at the same time as copying the data: we
now use checksum offloading to the hardware (or dom0), so we don't
calculate the checksum at all. For UDP checksum is optional anyway and
I think we skip it.

- Remembering which application sent/received the previous UDP packet
to avoid searching in the common case: might help, but we typically
only have one application in Mirage anyway. In my UDP tests, I only
testing sending. I need to look more closely at handling TCP acks.

- BSD treated UDP sockets as being connected to a particular endpoint,
and had to keep changing the address if the application specified the
destination with each packet. Mirage already has the correct API.

- Minimising privilege level changes and locking: these don't apply to<= br> Mirage since it's single-threaded and runs at a fixed level.

- Pooling buffers to save on allocation. Could be useful.

In general though, the bottleneck seems to be the Xen API rather than
performance problems within Mirage. In all cases, we spend a lot of
time blocking and/or dealing with Xen grants.


On 2 September 2014 16:04, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> wrote:
> by the way, back in the day, someone did some work on UDP in BSD unix = to get
> it to not go so slow (see
> A Faster UDP
> by partidge and pink
> http://dl.acm.org/citation.cfm?id=3D169943
> but i dont think anyone picked up on those optimisations in the Linux = world
> (though obviously did for TCP) - not sure tho!
>
>
> On Thu, Aug 21, 2014 at 3:31 PM, Thomas Leonard <talex5@gmail.com> wrote:
>>
>> On 21 August 2014 15:09, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
>> >>> Cool -- it would be great to polish up a tool like th= is.
>> >>
>> >> Yes, I think there's a lot we could do here. I've= written up the
>> >> profiling I've done so far here:
>> >>
>> >> http://roscidus.com/blog/blog/2014/= 08/15/optimising-the-unikernel/
>> >>
>> >> The graphs are quite interesting - if people familiar wit= h the code
>> >> could explain what's going on (especially with the bl= ock device) that
>> >> would be great!
>> >
>> > I'm settting up a 4.01 switch with profiling on.
>>
>> Thanks!
>>
>> > Do you think the -fno-omit-frame-pointer configure options co= uld also
>> > help to have more precise profiling information?
>>
>> I'm not sure it would help. The problems currently are:
>>
>> 1. We can't tell when a function returns until the next one is= called.
>> 2. Tail calls look like the function returned first.
>> 3. For recursive calls, we can't tell which frame is the calle= r. (e.g.
>> foo calls foo and foo calls bar, but we don't know which foo >> activation called bar).
>>
>> We could guess (3) by looking at the stack pointer. But it wouldn&= #39;t
>> work for tail calls, since the stack doesn't grow and if we so= lved (1)
>> and (2) then we'd get (3) for free.
>>
>> I guess it wouldn't be hard to make the compiler call a trace = function
>> on every return / before every tail call.
>>
>> The frame pointer would be useful if we didn't have tracing bu= t wanted
>> a backtrace.
>>
>> > Thomas
>> >
>> >>
>> >> Overall, the changes increased the queuing service's = download rate
>> >> from 2.46 MB/s to 7.24 MB/s, which is nice but still a bi= t
>> >> disappointing.
>> >>
>> >>
>> >> --
>> >> Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
>> >> GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3= CC1
>> >> GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D= 8BA
>> >>
>> >> _______________________________________________
>> >> MirageOS-devel mailing list
>> >> Mi= rageOS-devel@lists.xenproject.org
>> >> http://lists.xenproject.org/cgi-bi= n/mailman/listinfo/mirageos-devel
>> >
>>
>>
>>
>> --
>> Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
>> GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
>> GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA
>>
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-de= vel@lists.xenproject.org
>> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>
>



--
Dr Thomas Leonard=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://0install.net/
GPG: 9242 9807 C985 3C07 44A6=C2=A0 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA=C2=A0 BD8E 0713 3F96 CA74 D8BA
--001a11c2cafc7e841f050225ca11-- --===============6825728363437946598== 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 --===============6825728363437946598==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 16:03:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 16:03: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 1XPD1s-0007Jq-NE; Wed, 03 Sep 2014 16:03:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPD1q-0007Jl-PJ for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 16:03:27 +0000 Received: from [85.158.137.68:25110] by server-16.bemta-3.messagelabs.com id 9B/B2-01431-ECB37045; Wed, 03 Sep 2014 16:03:26 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1409760204!12232903!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4123 invoked from network); 3 Sep 2014 16:03:25 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 16:03:25 -0000 Received: by mail-lb0-f181.google.com with SMTP id s7so1488873lbd.40 for ; Wed, 03 Sep 2014 09:03:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=VewJNiQYl0t2a7TsnPncpXhQ2tC7kQ/yahJN99JZUnI=; b=ZPq5MeBKaFhpmhzXwdosc1lMMrVqUXGkOtNHXaPpuhTR8hqDLTRPUSVzkOrRWgosro 0iHSKVP3fkXUZdnhdnGUyy8Ms5Y52gdABcNS7BYtGk3cv4oyAe6RYxO21WxGuV3sjjou VzqZtveNerhH5B2ryFXLCG33XxaH1dG6nffhuNMafxZqUMxKAFbnyFj9B0tcZzE6x7vt IJxSvQtBH6UCsu68z9Sf8ehPNACulEYldMtuYu9JPUd3rxA2GnnoegPJ4ZFlN3464PAA GINv3pAG9dkFNNyW207Nfmwz8c6O7SpCMHTLreUS4PTYHMFFB71gPv51VZiFtrfE2mac x3Zw== MIME-Version: 1.0 X-Received: by 10.152.9.42 with SMTP id w10mr42950053laa.9.1409760204500; Wed, 03 Sep 2014 09:03:24 -0700 (PDT) Received: by 10.25.136.134 with HTTP; Wed, 3 Sep 2014 09:03:24 -0700 (PDT) In-Reply-To: References: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> Date: Wed, 3 Sep 2014 17:03:24 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMiBTZXB0ZW1iZXIgMjAxNCAxNToxMCwgVGhvbWFzIExlb25hcmQgPHRhbGV4NUBnbWFpbC5j b20+IHdyb3RlOgo+IE9uIDIxIEF1Z3VzdCAyMDE0IDE4OjMwLCBEYXZlIFNjb3R0IDxEYXZlLlNj b3R0QGNpdHJpeC5jb20+IHdyb3RlOgo+PiBIaSwKPj4KPj4gT24gMjEgQXVnIDIwMTQsIGF0IDEy OjEwLCBUaG9tYXMgTGVvbmFyZCA8dGFsZXg1QGdtYWlsLmNvbT4gd3JvdGU6Cj4gWy4uLl0KPj4+ IEkndmUgd3JpdHRlbiB1cCB0aGUgcHJvZmlsaW5nIEkndmUgZG9uZSBzbyBmYXIgaGVyZToKPj4+ Cj4+PiBodHRwOi8vcm9zY2lkdXMuY29tL2Jsb2cvYmxvZy8yMDE0LzA4LzE1L29wdGltaXNpbmct dGhlLXVuaWtlcm5lbC8KPj4+Cj4+PiBUaGUgZ3JhcGhzIGFyZSBxdWl0ZSBpbnRlcmVzdGluZyAt IGlmIHBlb3BsZSBmYW1pbGlhciB3aXRoIHRoZSBjb2RlCj4+PiBjb3VsZCBleHBsYWluIHdoYXQn cyBnb2luZyBvbiAoZXNwZWNpYWxseSB3aXRoIHRoZSBibG9jayBkZXZpY2UpIHRoYXQKPj4+IHdv dWxkIGJlIGdyZWF0IQo+Pgo+PiBUaGUgZ3JhcGhzIGFyZSBpbnRlcmVzdGluZyEKPj4KPj4gSUlS QyB0aGUgZ3JhbnQgdW5tYXAgb3BlcmF0aW9uIGlzIHZlcnkgZXhwZW5zaXZlIHNpbmNlIGl0IGlu dm9sdmVzIGEgVExCIHNob290ZG93bi4gVGhpcyBhZGRzIGEgbGFyZ2UgYW1vdW50IChyZWxhdGl2 ZWx5LCBjb21wYXJlZCB0byBtb2Rlcm4gZmxhc2gtYmFzZWQgZGlza3MpIHRvIHRoZSByZXF1ZXN0 L3Jlc3BvbnNlIGxhdGVuY3kuIEkgdGhpbmsgdGhpcyBpcyB3aHkgdGhlIHBlcmZvcm1hbmNlIGlz IHNvIHRlcnJpYmxlIHdpdGggb25lIHJlcXVlc3QgYXQgYSB0aW1lLiBJIHN1c3BlY3QgdGhhdCB0 aGUgYmF0Y2hpbmcgeW914oCZcmUgc2VlaW5nIHdpdGggdHdvIHJlcXVlc3RzIGlzIGFuIGFydGVm YWN0IG9mIHRoZSBiYWNrZW5kLCB3aGljaCBpcyBwcm9iYWJseSB0cnlpbmcgdG8gdW5tYXAgYm90 aCBncmFudCByZWZlcmVuY2VzIGF0IG9uY2UgZm9yIGVmZmljaWVuY3kuIFdoZW4gSSB3cm90ZSBh IHVzZXItc3BhY2UgYmxvY2sgYmFja2VuZCBiYXRjaGluZyB0aGUgdW5tYXBzIG1hZGUgYSBtYXNz aXZlIGRpZmZlcmVuY2UuCj4KPiBJIHdvbmRlciBpZiB0aGlzIGFwcGxpZXMgdG8gQVJNLiBZb3Ug c2hvdWxkIGJlIGFibGUgdG8gaW52YWxpZGF0ZQo+IGluZGl2aWR1YWwgVExCIGVudHJpZXMgdGhl cmUsIEkgdGhpbmsuCj4KPj4gVGhlcmUgaXMgYSBibG9jayBwcm90b2NvbCBleHRlbnNpb24gY2Fs bGVkIOKAnHBlcnNpc3RlbnQgZ3JhbnRz4oCdIHRoYXQgd2UgaGF2ZW7igJl0IGltcGxlbWVudGVk ICh5ZXQpLiBUaGlzIGRvZXMgdGhlIG9idmlvdXMgdGhpbmcgYW5kIHByZS1zaGFyZXMgYSBzZXQg b2YgcGFnZXMuIFdlIG1pZ2h0IHN1ZmZlciBhIGJpdCBiZWNhdXNlIG9mIGV4dHJhIGNvcGllcyAo aS5lLiB3ZSBtaWdodCBoYXZlIHRvIGNvcHkgaW50byB0aGUgcHJlLXNoYXJlZCBwYWdlcykgYnV0 IHdlIHdvdWxkIHNhdmUgdGhlIHVubWFwIG92ZXJoZWFkLCBzbyBpdCBtaWdodCBiZSB3b3J0aCBp dC4KPgo+IEhhZCBhIGdvIGF0IHRoaXMsIGJ1dCBpdCBkaWRuJ3QgbWFrZSBtdWNoIGRpZmZlcmVu Y2UuIEhvd2V2ZXIsIEkndmUKPiBkaXNjb3ZlcmVkIHRoYXQgZGQgaW4gZG9tMCBpc24ndCB0b28g ZmFzdCBlaXRoZXIuIEkgb3JpZ2luYWxseSB0ZXN0ZWQKPiB3aXRoIGhkcGFybSwgd2hpY2ggcmVw b3J0cyAyMCBNQi9zIGFzIGV4cGVjdGVkOgo+Cj4gJCBoZHBhcm0gLXQgL2Rldi9tbWNibGswCj4g IFRpbWluZyBidWZmZXJlZCBkaXNrIHJlYWRzOiAgNjIgTUIgaW4gIDMuMDcgc2Vjb25kcyA9ICAy MC4yMSBNQi9zZWMKPgo+IGRkJ3Mgc3BlZWQgc2VlbXMgdG8gZGVwZW5kIGEgbG90IG9uIHRoZSBi bG9jayBzaXplLiBVc2luZwo+IDQwOTYqMTE9NDUwNTYgYnl0ZXMgKHdoaWNoIEkgYXNzdW1lIGlz IHdoYXQgZG9tMCB3b3VsZCBkbyBpbiByZXNwb25zZQo+IHRvIGEgZ3Vlc3QgcmVxdWVzdCksIEkg Z2V0IDE2LjkgTUIvczoKPgo+ICQgZGQgaWZsYWc9ZGlyZWN0IGlmPS9kZXYvdmcwL2JlbmNoICBv Zj0vZGV2L251bGwgYnM9NDUwNTYgY291bnQ9MTAwMAo+IDEwMDArMCByZWNvcmRzIGluCj4gMTAw MCswIHJlY29yZHMgb3V0Cj4gNDUwNTYwMDAgYnl0ZXMgKDQ1IE1CKSBjb3BpZWQsIDIuNjU5MTEg cywgMTYuOSBNQi9zCj4KPiBicz02NTUzNiBnaXZlcyAxOC44IE1CL3MgYW5kIGJzPTEzMTA3MiBn aXZlcyAyMC44IE1CL3MuIExpbnV4IGRvbVUKPiByZXBvcnRzIDIwLjM2IE1CL3NlYyBmcm9tIGhk cGFybSBidXQgb25seSAxOC42IE1CL3MgZnJvbSBkZAo+IChicz0xMzEwNzIpLiBTbyBwZXJoYXBz IE1pcmFnZSBpcyBkb2luZyBwcmV0dHkgd2VsbCBhbHJlYWR5LgoKSSBoYWQgYSBsb29rIGF0IGhv dyBoZHBhcm0gZ2V0cyB0aGUgZnVsbCBzcGVlZC4gSXQncyB1c2luZyAyNTYgcGFnZXMKcGVyIHJl cXVlc3QsIHdoaWNoIHJlcXVpcmVzIHN1cHBvcnQgZm9yIGluZGlyZWN0IHBhZ2VzIGluIGJsa2Zy b250Cih3aXRoIGRpcmVjdCByZXF1ZXN0cywgdGhlIG1heGltdW0gaXMgMTEgcGFnZXMgcGVyIHJl cXVlc3QpLgoKSSBhZGRlZCBzdXBwb3J0IGhlcmU6CgogIGh0dHBzOi8vZ2l0aHViLmNvbS90YWxl eDUvbWlyYWdlLWJsb2NrLXhlbi9jb21taXRzL21hc3RlcgoKV2l0aCB0aGlzLCBJIGdvdCAyMS4z MiBNQi9zIHJlYWQgYW5kIDkuMTcgTUIvcyB3cml0ZS4gVGhlIHJlc3VsdHMgdmFyeQphIGZhaXIg Yml0IHdpdGggYmxvY2sgc2l6ZSAodGhvc2Ugd2VyZSB0aGUgYmVzdCksIGJ1dCB0aGF0IHNlZW1z IGxpa2UKYW4gaW1wcm92ZW1lbnQgKHRoZSBwcmV2aW91cyBiZXN0IHdhcyAxOC4yN3IgYW5kIDcu MDd3KS4KCgotLSAKRHIgVGhvbWFzIExlb25hcmQgICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQv CkdQRzogOTI0MiA5ODA3IEM5ODUgM0MwNyA0NEE2ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEK R1BHOiBEQTk4IDI1QUUgQ0FEMCA4OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoK X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1Mt ZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0 dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdl b3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 16:03:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 16:03: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 1XPD1s-0007Jq-NE; Wed, 03 Sep 2014 16:03:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPD1q-0007Jl-PJ for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 16:03:27 +0000 Received: from [85.158.137.68:25110] by server-16.bemta-3.messagelabs.com id 9B/B2-01431-ECB37045; Wed, 03 Sep 2014 16:03:26 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1409760204!12232903!1 X-Originating-IP: [209.85.217.181] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4123 invoked from network); 3 Sep 2014 16:03:25 -0000 Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com) (209.85.217.181) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 16:03:25 -0000 Received: by mail-lb0-f181.google.com with SMTP id s7so1488873lbd.40 for ; Wed, 03 Sep 2014 09:03:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=VewJNiQYl0t2a7TsnPncpXhQ2tC7kQ/yahJN99JZUnI=; b=ZPq5MeBKaFhpmhzXwdosc1lMMrVqUXGkOtNHXaPpuhTR8hqDLTRPUSVzkOrRWgosro 0iHSKVP3fkXUZdnhdnGUyy8Ms5Y52gdABcNS7BYtGk3cv4oyAe6RYxO21WxGuV3sjjou VzqZtveNerhH5B2ryFXLCG33XxaH1dG6nffhuNMafxZqUMxKAFbnyFj9B0tcZzE6x7vt IJxSvQtBH6UCsu68z9Sf8ehPNACulEYldMtuYu9JPUd3rxA2GnnoegPJ4ZFlN3464PAA GINv3pAG9dkFNNyW207Nfmwz8c6O7SpCMHTLreUS4PTYHMFFB71gPv51VZiFtrfE2mac x3Zw== MIME-Version: 1.0 X-Received: by 10.152.9.42 with SMTP id w10mr42950053laa.9.1409760204500; Wed, 03 Sep 2014 09:03:24 -0700 (PDT) Received: by 10.25.136.134 with HTTP; Wed, 3 Sep 2014 09:03:24 -0700 (PDT) In-Reply-To: References: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> Date: Wed, 3 Sep 2014 17:03:24 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org T24gMiBTZXB0ZW1iZXIgMjAxNCAxNToxMCwgVGhvbWFzIExlb25hcmQgPHRhbGV4NUBnbWFpbC5j b20+IHdyb3RlOgo+IE9uIDIxIEF1Z3VzdCAyMDE0IDE4OjMwLCBEYXZlIFNjb3R0IDxEYXZlLlNj b3R0QGNpdHJpeC5jb20+IHdyb3RlOgo+PiBIaSwKPj4KPj4gT24gMjEgQXVnIDIwMTQsIGF0IDEy OjEwLCBUaG9tYXMgTGVvbmFyZCA8dGFsZXg1QGdtYWlsLmNvbT4gd3JvdGU6Cj4gWy4uLl0KPj4+ IEkndmUgd3JpdHRlbiB1cCB0aGUgcHJvZmlsaW5nIEkndmUgZG9uZSBzbyBmYXIgaGVyZToKPj4+ Cj4+PiBodHRwOi8vcm9zY2lkdXMuY29tL2Jsb2cvYmxvZy8yMDE0LzA4LzE1L29wdGltaXNpbmct dGhlLXVuaWtlcm5lbC8KPj4+Cj4+PiBUaGUgZ3JhcGhzIGFyZSBxdWl0ZSBpbnRlcmVzdGluZyAt IGlmIHBlb3BsZSBmYW1pbGlhciB3aXRoIHRoZSBjb2RlCj4+PiBjb3VsZCBleHBsYWluIHdoYXQn cyBnb2luZyBvbiAoZXNwZWNpYWxseSB3aXRoIHRoZSBibG9jayBkZXZpY2UpIHRoYXQKPj4+IHdv dWxkIGJlIGdyZWF0IQo+Pgo+PiBUaGUgZ3JhcGhzIGFyZSBpbnRlcmVzdGluZyEKPj4KPj4gSUlS QyB0aGUgZ3JhbnQgdW5tYXAgb3BlcmF0aW9uIGlzIHZlcnkgZXhwZW5zaXZlIHNpbmNlIGl0IGlu dm9sdmVzIGEgVExCIHNob290ZG93bi4gVGhpcyBhZGRzIGEgbGFyZ2UgYW1vdW50IChyZWxhdGl2 ZWx5LCBjb21wYXJlZCB0byBtb2Rlcm4gZmxhc2gtYmFzZWQgZGlza3MpIHRvIHRoZSByZXF1ZXN0 L3Jlc3BvbnNlIGxhdGVuY3kuIEkgdGhpbmsgdGhpcyBpcyB3aHkgdGhlIHBlcmZvcm1hbmNlIGlz IHNvIHRlcnJpYmxlIHdpdGggb25lIHJlcXVlc3QgYXQgYSB0aW1lLiBJIHN1c3BlY3QgdGhhdCB0 aGUgYmF0Y2hpbmcgeW914oCZcmUgc2VlaW5nIHdpdGggdHdvIHJlcXVlc3RzIGlzIGFuIGFydGVm YWN0IG9mIHRoZSBiYWNrZW5kLCB3aGljaCBpcyBwcm9iYWJseSB0cnlpbmcgdG8gdW5tYXAgYm90 aCBncmFudCByZWZlcmVuY2VzIGF0IG9uY2UgZm9yIGVmZmljaWVuY3kuIFdoZW4gSSB3cm90ZSBh IHVzZXItc3BhY2UgYmxvY2sgYmFja2VuZCBiYXRjaGluZyB0aGUgdW5tYXBzIG1hZGUgYSBtYXNz aXZlIGRpZmZlcmVuY2UuCj4KPiBJIHdvbmRlciBpZiB0aGlzIGFwcGxpZXMgdG8gQVJNLiBZb3Ug c2hvdWxkIGJlIGFibGUgdG8gaW52YWxpZGF0ZQo+IGluZGl2aWR1YWwgVExCIGVudHJpZXMgdGhl cmUsIEkgdGhpbmsuCj4KPj4gVGhlcmUgaXMgYSBibG9jayBwcm90b2NvbCBleHRlbnNpb24gY2Fs bGVkIOKAnHBlcnNpc3RlbnQgZ3JhbnRz4oCdIHRoYXQgd2UgaGF2ZW7igJl0IGltcGxlbWVudGVk ICh5ZXQpLiBUaGlzIGRvZXMgdGhlIG9idmlvdXMgdGhpbmcgYW5kIHByZS1zaGFyZXMgYSBzZXQg b2YgcGFnZXMuIFdlIG1pZ2h0IHN1ZmZlciBhIGJpdCBiZWNhdXNlIG9mIGV4dHJhIGNvcGllcyAo aS5lLiB3ZSBtaWdodCBoYXZlIHRvIGNvcHkgaW50byB0aGUgcHJlLXNoYXJlZCBwYWdlcykgYnV0 IHdlIHdvdWxkIHNhdmUgdGhlIHVubWFwIG92ZXJoZWFkLCBzbyBpdCBtaWdodCBiZSB3b3J0aCBp dC4KPgo+IEhhZCBhIGdvIGF0IHRoaXMsIGJ1dCBpdCBkaWRuJ3QgbWFrZSBtdWNoIGRpZmZlcmVu Y2UuIEhvd2V2ZXIsIEkndmUKPiBkaXNjb3ZlcmVkIHRoYXQgZGQgaW4gZG9tMCBpc24ndCB0b28g ZmFzdCBlaXRoZXIuIEkgb3JpZ2luYWxseSB0ZXN0ZWQKPiB3aXRoIGhkcGFybSwgd2hpY2ggcmVw b3J0cyAyMCBNQi9zIGFzIGV4cGVjdGVkOgo+Cj4gJCBoZHBhcm0gLXQgL2Rldi9tbWNibGswCj4g IFRpbWluZyBidWZmZXJlZCBkaXNrIHJlYWRzOiAgNjIgTUIgaW4gIDMuMDcgc2Vjb25kcyA9ICAy MC4yMSBNQi9zZWMKPgo+IGRkJ3Mgc3BlZWQgc2VlbXMgdG8gZGVwZW5kIGEgbG90IG9uIHRoZSBi bG9jayBzaXplLiBVc2luZwo+IDQwOTYqMTE9NDUwNTYgYnl0ZXMgKHdoaWNoIEkgYXNzdW1lIGlz IHdoYXQgZG9tMCB3b3VsZCBkbyBpbiByZXNwb25zZQo+IHRvIGEgZ3Vlc3QgcmVxdWVzdCksIEkg Z2V0IDE2LjkgTUIvczoKPgo+ICQgZGQgaWZsYWc9ZGlyZWN0IGlmPS9kZXYvdmcwL2JlbmNoICBv Zj0vZGV2L251bGwgYnM9NDUwNTYgY291bnQ9MTAwMAo+IDEwMDArMCByZWNvcmRzIGluCj4gMTAw MCswIHJlY29yZHMgb3V0Cj4gNDUwNTYwMDAgYnl0ZXMgKDQ1IE1CKSBjb3BpZWQsIDIuNjU5MTEg cywgMTYuOSBNQi9zCj4KPiBicz02NTUzNiBnaXZlcyAxOC44IE1CL3MgYW5kIGJzPTEzMTA3MiBn aXZlcyAyMC44IE1CL3MuIExpbnV4IGRvbVUKPiByZXBvcnRzIDIwLjM2IE1CL3NlYyBmcm9tIGhk cGFybSBidXQgb25seSAxOC42IE1CL3MgZnJvbSBkZAo+IChicz0xMzEwNzIpLiBTbyBwZXJoYXBz IE1pcmFnZSBpcyBkb2luZyBwcmV0dHkgd2VsbCBhbHJlYWR5LgoKSSBoYWQgYSBsb29rIGF0IGhv dyBoZHBhcm0gZ2V0cyB0aGUgZnVsbCBzcGVlZC4gSXQncyB1c2luZyAyNTYgcGFnZXMKcGVyIHJl cXVlc3QsIHdoaWNoIHJlcXVpcmVzIHN1cHBvcnQgZm9yIGluZGlyZWN0IHBhZ2VzIGluIGJsa2Zy b250Cih3aXRoIGRpcmVjdCByZXF1ZXN0cywgdGhlIG1heGltdW0gaXMgMTEgcGFnZXMgcGVyIHJl cXVlc3QpLgoKSSBhZGRlZCBzdXBwb3J0IGhlcmU6CgogIGh0dHBzOi8vZ2l0aHViLmNvbS90YWxl eDUvbWlyYWdlLWJsb2NrLXhlbi9jb21taXRzL21hc3RlcgoKV2l0aCB0aGlzLCBJIGdvdCAyMS4z MiBNQi9zIHJlYWQgYW5kIDkuMTcgTUIvcyB3cml0ZS4gVGhlIHJlc3VsdHMgdmFyeQphIGZhaXIg Yml0IHdpdGggYmxvY2sgc2l6ZSAodGhvc2Ugd2VyZSB0aGUgYmVzdCksIGJ1dCB0aGF0IHNlZW1z IGxpa2UKYW4gaW1wcm92ZW1lbnQgKHRoZSBwcmV2aW91cyBiZXN0IHdhcyAxOC4yN3IgYW5kIDcu MDd3KS4KCgotLSAKRHIgVGhvbWFzIExlb25hcmQgICAgICAgIGh0dHA6Ly8waW5zdGFsbC5uZXQv CkdQRzogOTI0MiA5ODA3IEM5ODUgM0MwNyA0NEE2ICA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEK R1BHOiBEQTk4IDI1QUUgQ0FEMCA4OTc1IDdDREEgIEJEOEUgMDcxMyAzRjk2IENBNzQgRDhCQQoK X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1Mt ZGV2ZWwgbWFpbGluZyBsaXN0Ck1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0 dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdl b3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 16:21:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 16:21: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 1XPDJ7-0008F7-RZ; Wed, 03 Sep 2014 16:21:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPDJ7-0008Ez-4w for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 16:21:17 +0000 Received: from [193.109.254.147:52183] by server-1.bemta-14.messagelabs.com id 6D/8D-24760-CFF37045; Wed, 03 Sep 2014 16:21:16 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1409761275!13277235!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6211 invoked from network); 3 Sep 2014 16:21:15 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-13.tower-27.messagelabs.com with SMTP; 3 Sep 2014 16:21:15 -0000 Received: (qmail 14565 invoked from network); 3 Sep 2014 16:21:14 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 3 Sep 2014 16:21:14 -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 12395-09 for ; Wed, 3 Sep 2014 17:21:07 +0100 (BST) Received: (qmail 14442 invoked by uid 599); 3 Sep 2014 16:21:07 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 03 Sep 2014 17:21:07 +0100 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 1XPDIw-0001Ie-Es; Wed, 03 Sep 2014 17:21:06 +0100 From: Richard Mortier To: Thomas Leonard Date: Wed, 3 Sep 2014 17:21:04 +0100 Thread-Topic: [MirageOS-devel] TCP checksum offload with Xen Thread-Index: Ac/HkxAjipB7Jo9/Tl6cGbU1vh09MA== Message-ID: <4DE36E8B-63BD-42AE-A28B-B67D26D66A08@nottingham.ac.uk> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2769631096903194297==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2769631096903194297== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 3 Sep 2014, at 09:59, Thomas Leonard wrote: > How will I ask mirage for a V1 vs V2 NETWORK? Like this? >=20 > let main =3D foreign "Unikernel.Main" (console2 @-> network2 @-> job) would it be possible to encapsulate by just opening a different module = (or even namespace if that's a thing yet), e.g. via a config/command = line option? or are there cases where we might want to mix V1 and V2? = (can't immediately think of any; guess they might be dealt with by = making things explicit anyway, ie., V1.console @-> V2.network @-> V2.job = or somesuch?!) --=20 Cheers, R. --Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUBz/wAAoJEOLF27JWwSg38rgQAK03DyjuNcl5xJ6/i1JlLnE+ urQSGhgm5wvmMVtcyRLe0XL58FSuFXuBMdJT0oUFJTlnI4mI2hsB9tV1DaQexTmS YRq6y8ucJb1c8tHxJBhaE1WwLbmAZ5aUELEsP3p3r48gRFmMl00fx7xoenHCQqKy OKrSeaJBXgrThWAZENDtijZdjK+GyW6SRP7axWJybgDf64PlBha8kRQygdi3wuja Nw2PbYC2YZRC1bk789hRDF09j/SDGCjLHSwiQ3dWyZOnRG7CNQnEorjHisFmdGKa 67erosxQOYgcx5Vn03OXmaTqoHyDu6ONiFrR+JoevTNWNZtaDq36G2g2jXLlq4Yr 1iGoXwFZHX0sQN5LQrwuDOcrfh4XHXUBihHYu5XC9tcCCcUd0qZ8AKYd6EV7qOnd Dxji3BT8AXYRFr7MPW77rNqgkgL6u+60GadLLBz2OsSTz9gHl0KcovAgrmfTUrKt 1W93T6BzNn1zuRrPqzXAt9KJ4IhI+YjFtSoQRMwuCBX4MIHYp+uAdigLs9dahyV9 q8mWv1RsbuqbtK7Obr9WEtHNoDYNF/vVzWMGRqJmkAEONcmvq4lyfCJB4NuZEs8T k3w5tyzjlPtsZM0EXb7S3K6DDz/QX2fUiqgqwHh/cMUIjXMUq1E3tnDhALsVWVes UCSR6VB3EUnxfsMo6rY4 =2j9x -----END PGP SIGNATURE----- --Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE-- --===============2769631096903194297== 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 --===============2769631096903194297==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 16:21:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 16:21: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 1XPDJ7-0008F7-RZ; Wed, 03 Sep 2014 16:21:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPDJ7-0008Ez-4w for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 16:21:17 +0000 Received: from [193.109.254.147:52183] by server-1.bemta-14.messagelabs.com id 6D/8D-24760-CFF37045; Wed, 03 Sep 2014 16:21:16 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1409761275!13277235!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6211 invoked from network); 3 Sep 2014 16:21:15 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-13.tower-27.messagelabs.com with SMTP; 3 Sep 2014 16:21:15 -0000 Received: (qmail 14565 invoked from network); 3 Sep 2014 16:21:14 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 3 Sep 2014 16:21:14 -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 12395-09 for ; Wed, 3 Sep 2014 17:21:07 +0100 (BST) Received: (qmail 14442 invoked by uid 599); 3 Sep 2014 16:21:07 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 03 Sep 2014 17:21:07 +0100 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 1XPDIw-0001Ie-Es; Wed, 03 Sep 2014 17:21:06 +0100 From: Richard Mortier To: Thomas Leonard Date: Wed, 3 Sep 2014 17:21:04 +0100 Thread-Topic: [MirageOS-devel] TCP checksum offload with Xen Thread-Index: Ac/HkxAjipB7Jo9/Tl6cGbU1vh09MA== Message-ID: <4DE36E8B-63BD-42AE-A28B-B67D26D66A08@nottingham.ac.uk> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2769631096903194297==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2769631096903194297== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 3 Sep 2014, at 09:59, Thomas Leonard wrote: > How will I ask mirage for a V1 vs V2 NETWORK? Like this? >=20 > let main =3D foreign "Unikernel.Main" (console2 @-> network2 @-> job) would it be possible to encapsulate by just opening a different module = (or even namespace if that's a thing yet), e.g. via a config/command = line option? or are there cases where we might want to mix V1 and V2? = (can't immediately think of any; guess they might be dealt with by = making things explicit anyway, ie., V1.console @-> V2.network @-> V2.job = or somesuch?!) --=20 Cheers, R. --Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUBz/wAAoJEOLF27JWwSg38rgQAK03DyjuNcl5xJ6/i1JlLnE+ urQSGhgm5wvmMVtcyRLe0XL58FSuFXuBMdJT0oUFJTlnI4mI2hsB9tV1DaQexTmS YRq6y8ucJb1c8tHxJBhaE1WwLbmAZ5aUELEsP3p3r48gRFmMl00fx7xoenHCQqKy OKrSeaJBXgrThWAZENDtijZdjK+GyW6SRP7axWJybgDf64PlBha8kRQygdi3wuja Nw2PbYC2YZRC1bk789hRDF09j/SDGCjLHSwiQ3dWyZOnRG7CNQnEorjHisFmdGKa 67erosxQOYgcx5Vn03OXmaTqoHyDu6ONiFrR+JoevTNWNZtaDq36G2g2jXLlq4Yr 1iGoXwFZHX0sQN5LQrwuDOcrfh4XHXUBihHYu5XC9tcCCcUd0qZ8AKYd6EV7qOnd Dxji3BT8AXYRFr7MPW77rNqgkgL6u+60GadLLBz2OsSTz9gHl0KcovAgrmfTUrKt 1W93T6BzNn1zuRrPqzXAt9KJ4IhI+YjFtSoQRMwuCBX4MIHYp+uAdigLs9dahyV9 q8mWv1RsbuqbtK7Obr9WEtHNoDYNF/vVzWMGRqJmkAEONcmvq4lyfCJB4NuZEs8T k3w5tyzjlPtsZM0EXb7S3K6DDz/QX2fUiqgqwHh/cMUIjXMUq1E3tnDhALsVWVes UCSR6VB3EUnxfsMo6rY4 =2j9x -----END PGP SIGNATURE----- --Apple-Mail=_5F46F8D0-948A-46D3-BF58-CF59E3B237AE-- --===============2769631096903194297== 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 --===============2769631096903194297==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 16:47:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 16:47: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 1XPDiP-0000no-IL; Wed, 03 Sep 2014 16:47:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPDiO-0000nj-8L for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 16:47:24 +0000 Received: from [85.158.143.35:32898] by server-1.bemta-4.messagelabs.com id 81/65-05872-B1647045; Wed, 03 Sep 2014 16:47:23 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1409762842!5405518!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3786 invoked from network); 3 Sep 2014 16:47:22 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-2.tower-21.messagelabs.com with SMTP; 3 Sep 2014 16:47:22 -0000 Received: (qmail 28000 invoked from network); 3 Sep 2014 16:31:37 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 3 Sep 2014 16:31:37 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 26023-05 for ; Wed, 3 Sep 2014 17:31:29 +0100 (BST) Received: (qmail 27534 invoked by uid 599); 3 Sep 2014 16:31:29 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 03 Sep 2014 17:31:29 +0100 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 1XPDT2-0002Wj-6s; Wed, 03 Sep 2014 17:31:32 +0100 From: Richard Mortier To: Thomas Leonard , Jon Crowcroft Date: Wed, 3 Sep 2014 17:31:29 +0100 Thread-Topic: [MirageOS-devel] Profiling Mirage on Xen Thread-Index: Ac/HlITok97sUp5uQ3iVMURvYC0MQQ== Message-ID: <145B365F-FC99-43FF-93D6-816307257DDA@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5254870095139741541==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5254870095139741541== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 3 Sep 2014, at 09:05, Thomas Leonard wrote: > - Pooling buffers to save on allocation. Could be useful. fwiw the memorisation trick on dns would be related to this (i guess) -- = two related claims made with mirage is because the whole stack is = available, cross-layer/full-stack optimisations are more easily = possible; and the use of languages like ocaml tends to indicate high = level algorithmic optimisations are available. which seems perhaps a different approach to optimisation than = traditional systems permit. --=20 Cheers, R. --Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUB0JiAAoJEOLF27JWwSg378sP/A2TW/aOmpLtU6E6JYvfaGXb Fd7p0sgjdAFufdx5ivHb+k0GO+ncyQ3fQjxxwB5SU1DnNOUY4iCeL4ttnTO8V+tl aBSIUPjPF5jU4cJRdDZ1EP6XkVfAKUM5xRvOtnFrYD0zRSV+xo5dW6N3cY7sxC8i BZK4SCnH24qbg0KOXSl6Q0HOPA5KtkrrtbXXr2ZjLNfDEdR1zA390fSA/+NJUVA4 s2flvcV88fp2WBaMQzyqHh4n0+4TjHysQBujUwLWJi7uUi//CrfYU10lbfkVhSL/ 2C0DbxjSq8xoPtHqLnPAtzio8XbVEuPg63OPDOb52CKNbt6jLcDKC4qn/46TlbF0 F6bFovsWds6SqhweV+OGJ7SsSc+dbDU2cge7WCG8O9UczFuZG798YFvMi0NsfrDv D9k3BEG54gw++vnNl7Ud0fS8mSy1LpN7CS4xKH7VxBU2gnO2YAv7/znoMVxgDGQ+ PpBsCD4fplKooUHdzQt4Mamw2NDBau54sgiybEFbIeZyZGdwgMmgTNmkxjZSGLmk RPMjxXcOZXWrFib9ZpTm0do2jS7S+vXltG/eLJs6e3Y7pjMITFSgfWKHghEdAKIl GZS+/g9BbaEut+F0QAuEEmVbYyriCd831UMxztcY2mkVIBtlIDOB+3AFEfhx82Lv v5JPzOhEZcHVJ+sm1ocl =9aLR -----END PGP SIGNATURE----- --Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C-- --===============5254870095139741541== 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 --===============5254870095139741541==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 16:47:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 16:47: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 1XPDiP-0000no-IL; Wed, 03 Sep 2014 16:47:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPDiO-0000nj-8L for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 16:47:24 +0000 Received: from [85.158.143.35:32898] by server-1.bemta-4.messagelabs.com id 81/65-05872-B1647045; Wed, 03 Sep 2014 16:47:23 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1409762842!5405518!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3786 invoked from network); 3 Sep 2014 16:47:22 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-2.tower-21.messagelabs.com with SMTP; 3 Sep 2014 16:47:22 -0000 Received: (qmail 28000 invoked from network); 3 Sep 2014 16:31:37 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 3 Sep 2014 16:31:37 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 26023-05 for ; Wed, 3 Sep 2014 17:31:29 +0100 (BST) Received: (qmail 27534 invoked by uid 599); 3 Sep 2014 16:31:29 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 03 Sep 2014 17:31:29 +0100 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 1XPDT2-0002Wj-6s; Wed, 03 Sep 2014 17:31:32 +0100 From: Richard Mortier To: Thomas Leonard , Jon Crowcroft Date: Wed, 3 Sep 2014 17:31:29 +0100 Thread-Topic: [MirageOS-devel] Profiling Mirage on Xen Thread-Index: Ac/HlITok97sUp5uQ3iVMURvYC0MQQ== Message-ID: <145B365F-FC99-43FF-93D6-816307257DDA@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5254870095139741541==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5254870095139741541== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 3 Sep 2014, at 09:05, Thomas Leonard wrote: > - Pooling buffers to save on allocation. Could be useful. fwiw the memorisation trick on dns would be related to this (i guess) -- = two related claims made with mirage is because the whole stack is = available, cross-layer/full-stack optimisations are more easily = possible; and the use of languages like ocaml tends to indicate high = level algorithmic optimisations are available. which seems perhaps a different approach to optimisation than = traditional systems permit. --=20 Cheers, R. --Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUB0JiAAoJEOLF27JWwSg378sP/A2TW/aOmpLtU6E6JYvfaGXb Fd7p0sgjdAFufdx5ivHb+k0GO+ncyQ3fQjxxwB5SU1DnNOUY4iCeL4ttnTO8V+tl aBSIUPjPF5jU4cJRdDZ1EP6XkVfAKUM5xRvOtnFrYD0zRSV+xo5dW6N3cY7sxC8i BZK4SCnH24qbg0KOXSl6Q0HOPA5KtkrrtbXXr2ZjLNfDEdR1zA390fSA/+NJUVA4 s2flvcV88fp2WBaMQzyqHh4n0+4TjHysQBujUwLWJi7uUi//CrfYU10lbfkVhSL/ 2C0DbxjSq8xoPtHqLnPAtzio8XbVEuPg63OPDOb52CKNbt6jLcDKC4qn/46TlbF0 F6bFovsWds6SqhweV+OGJ7SsSc+dbDU2cge7WCG8O9UczFuZG798YFvMi0NsfrDv D9k3BEG54gw++vnNl7Ud0fS8mSy1LpN7CS4xKH7VxBU2gnO2YAv7/znoMVxgDGQ+ PpBsCD4fplKooUHdzQt4Mamw2NDBau54sgiybEFbIeZyZGdwgMmgTNmkxjZSGLmk RPMjxXcOZXWrFib9ZpTm0do2jS7S+vXltG/eLJs6e3Y7pjMITFSgfWKHghEdAKIl GZS+/g9BbaEut+F0QAuEEmVbYyriCd831UMxztcY2mkVIBtlIDOB+3AFEfhx82Lv v5JPzOhEZcHVJ+sm1ocl =9aLR -----END PGP SIGNATURE----- --Apple-Mail=_4D464473-A5BE-4A0D-82B5-391DC239AC1C-- --===============5254870095139741541== 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 --===============5254870095139741541==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 17:02:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 17: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 1XPDx2-0001oU-Tp; Wed, 03 Sep 2014 17:02:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPDx2-0001oO-7n for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 17:02:32 +0000 Received: from [85.158.143.35:49727] by server-3.bemta-4.messagelabs.com id 87/F7-06192-7A947045; Wed, 03 Sep 2014 17:02:31 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1409763748!13417922!1 X-Originating-IP: [209.85.220.50] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 691 invoked from network); 3 Sep 2014 17:02:30 -0000 Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 17:02:30 -0000 Received: by mail-pa0-f50.google.com with SMTP id kq14so17957912pab.9 for ; Wed, 03 Sep 2014 10:02:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6s4+3hhQJX2Dw6cVwn7kNoSTsH7gaF8tPfIrKWl3UmY=; b=XoQt90aWNOeAUhR38WJsJ3ahY8ZB4IKNAdZzU0bbsSqm3SoPBF7Q0ZL0pe3zZ6cIri Miy+7geAPm375YPDdcI4cmP++LkMWOwDPlvSRLdx2wVQ0HHAcxfTp09YEffG3vPicndS 0o9AgbVo2IlX/O013Ko1cMaWnq6fG9g+2WMlqL4rsMbKnnnMMkIVOIHmo6gKJIz7KiRT 31pDv3P/BuO29abXGBvqVflyJ5fQb8tRlLarWWWa6plgJ9WCM+lU3k9HweZTXKNeASoy YR8d5XjRMkC0yiYd8yfJUPuVmdCRJxzn4r3M1VRK0ZjKWk6tsOaVkl4gi/x3EuwuOV/T tPmQ== MIME-Version: 1.0 X-Received: by 10.66.158.130 with SMTP id wu2mr59411017pab.59.1409763746426; Wed, 03 Sep 2014 10:02:26 -0700 (PDT) Received: by 10.70.87.8 with HTTP; Wed, 3 Sep 2014 10:02:26 -0700 (PDT) In-Reply-To: References: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> Date: Wed, 3 Sep 2014 18:02:26 +0100 Message-ID: From: David Scott To: Thomas Leonard Cc: Dave Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8332300584034223263==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8332300584034223263== Content-Type: multipart/alternative; boundary=047d7b86c81452b55005022c33a0 --047d7b86c81452b55005022c33a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Sep 3, 2014 at 5:03 PM, Thomas Leonard wrote: > On 2 September 2014 15:10, Thomas Leonard wrote: > > On 21 August 2014 18:30, Dave Scott wrote: > >> Hi, > >> > >> On 21 Aug 2014, at 12:10, Thomas Leonard wrote: > > [...] > >>> I've written up the profiling I've done so far here: > >>> > >>> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ > >>> > >>> The graphs are quite interesting - if people familiar with the code > >>> could explain what's going on (especially with the block device) that > >>> would be great! > >> > >> The graphs are interesting! > >> > >> IIRC the grant unmap operation is very expensive since it involves a > TLB shootdown. This adds a large amount (relatively, compared to modern > flash-based disks) to the request/response latency. I think this is why t= he > performance is so terrible with one request at a time. I suspect that the > batching you=E2=80=99re seeing with two requests is an artefact of the ba= ckend, > which is probably trying to unmap both grant references at once for > efficiency. When I wrote a user-space block backend batching the unmaps > made a massive difference. > > > > I wonder if this applies to ARM. You should be able to invalidate > > individual TLB entries there, I think. > > > >> There is a block protocol extension called =E2=80=9Cpersistent grants= =E2=80=9D that we > haven=E2=80=99t implemented (yet). This does the obvious thing and pre-sh= ares a set > of pages. We might suffer a bit because of extra copies (i.e. we might ha= ve > to copy into the pre-shared pages) but we would save the unmap overhead, = so > it might be worth it. > > > > Had a go at this, but it didn't make much difference. However, I've > > discovered that dd in dom0 isn't too fast either. I originally tested > > with hdparm, which reports 20 MB/s as expected: > > > > $ hdparm -t /dev/mmcblk0 > > Timing buffered disk reads: 62 MB in 3.07 seconds =3D 20.21 MB/sec > > > > dd's speed seems to depend a lot on the block size. Using > > 4096*11=3D45056 bytes (which I assume is what dom0 would do in response > > to a guest request), I get 16.9 MB/s: > > > > $ dd iflag=3Ddirect if=3D/dev/vg0/bench of=3D/dev/null bs=3D45056 coun= t=3D1000 > > 1000+0 records in > > 1000+0 records out > > 45056000 bytes (45 MB) copied, 2.65911 s, 16.9 MB/s > > > > bs=3D65536 gives 18.8 MB/s and bs=3D131072 gives 20.8 MB/s. Linux domU > > reports 20.36 MB/sec from hdparm but only 18.6 MB/s from dd > > (bs=3D131072). So perhaps Mirage is doing pretty well already. > > I had a look at how hdparm gets the full speed. It's using 256 pages > per request, which requires support for indirect pages in blkfront > (with direct requests, the maximum is 11 pages per request). > > I added support here: > > https://github.com/talex5/mirage-block-xen/commits/master > > With this, I got 21.32 MB/s read and 9.17 MB/s write. The results vary > a fair bit with block size (those were the best), but that seems like > an improvement (the previous best was 18.27r and 7.07w). > Nice! When you're happy with it, please make a pull request... Cheers, Dave Scott --047d7b86c81452b55005022c33a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Wed, Sep 3, 2014 at 5:03 PM, Thomas Leonard &l= t;talex5@gmail.com> wrote:
On 2= September 2014 15:10, Thomas Leonard <talex5@gmail.com> wrote:
> On 21 August 2014 18:30, Dave Scott <Dave.Scott@citrix.com> wrote:
>> Hi,
>>
>> On 21 Aug 2014, at 12:10, Thomas Leonard <talex5@gmail.com> wrote:
> [...]
>>> I've written up the profiling I've done so far here: >>>
>>> http://roscidus.com/blog/blog/2014/08/15= /optimising-the-unikernel/
>>>
>>> The graphs are quite interesting - if people familiar with the= code
>>> could explain what's going on (especially with the block d= evice) that
>>> would be great!
>>
>> The graphs are interesting!
>>
>> IIRC the grant unmap operation is very expensive since it involves= a TLB shootdown. This adds a large amount (relatively, compared to modern = flash-based disks) to the request/response latency. I think this is why the= performance is so terrible with one request at a time. I suspect that the = batching you=E2=80=99re seeing with two requests is an artefact of the back= end, which is probably trying to unmap both grant references at once for ef= ficiency. When I wrote a user-space block backend batching the unmaps made = a massive difference.
>
> I wonder if this applies to ARM. You should be able to invalidate
> individual TLB entries there, I think.
>
>> There is a block protocol extension called =E2=80=9Cpersistent gra= nts=E2=80=9D that we haven=E2=80=99t implemented (yet). This does the obvio= us thing and pre-shares a set of pages. We might suffer a bit because of ex= tra copies (i.e. we might have to copy into the pre-shared pages) but we wo= uld save the unmap overhead, so it might be worth it.
>
> Had a go at this, but it didn't make much difference. However, I&#= 39;ve
> discovered that dd in dom0 isn't too fast either. I originally tes= ted
> with hdparm, which reports 20 MB/s as expected:
>
> $ hdparm -t /dev/mmcblk0
>=C2=A0 Timing buffered disk reads:=C2=A0 62 MB in=C2=A0 3.07 seconds = =3D=C2=A0 20.21 MB/sec
>
> dd's speed seems to depend a lot on the block size. Using
> 4096*11=3D45056 bytes (which I assume is what dom0 would do in respons= e
> to a guest request), I get 16.9 MB/s:
>
> $ dd iflag=3Ddirect if=3D/dev/vg0/bench=C2=A0 of=3D/dev/null bs=3D4505= 6 count=3D1000
> 1000+0 records in
> 1000+0 records out
> 45056000 bytes (45 MB) copied, 2.65911 s, 16.9 MB/s
>
> bs=3D65536 gives 18.8 MB/s and bs=3D131072 gives 20.8 MB/s. Linux domU=
> reports 20.36 MB/sec from hdparm but only 18.6 MB/s from dd
> (bs=3D131072). So perhaps Mirage is doing pretty well already.

I had a look at how hdparm gets the full speed. It's using = 256 pages
per request, which requires support for indirect pages in blkfront
(with direct requests, the maximum is 11 pages per request).

I added support here:

=C2=A0 https://github.com/talex5/mirage-block-xen/commits/mast= er

With this, I got 21.32 MB/s read and 9.17 MB/s write. The results vary
a fair bit with block size (those were the best), but that seems like
an improvement (the previous best was 18.27r and 7.07w).

Nice! When you're happy with it, please make a pull r= equest...

Cheers,
Dave Scott
--047d7b86c81452b55005022c33a0-- --===============8332300584034223263== 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 --===============8332300584034223263==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 17:02:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 17: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 1XPDx2-0001oU-Tp; Wed, 03 Sep 2014 17:02:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPDx2-0001oO-7n for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 17:02:32 +0000 Received: from [85.158.143.35:49727] by server-3.bemta-4.messagelabs.com id 87/F7-06192-7A947045; Wed, 03 Sep 2014 17:02:31 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1409763748!13417922!1 X-Originating-IP: [209.85.220.50] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 691 invoked from network); 3 Sep 2014 17:02:30 -0000 Received: from mail-pa0-f50.google.com (HELO mail-pa0-f50.google.com) (209.85.220.50) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 17:02:30 -0000 Received: by mail-pa0-f50.google.com with SMTP id kq14so17957912pab.9 for ; Wed, 03 Sep 2014 10:02:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6s4+3hhQJX2Dw6cVwn7kNoSTsH7gaF8tPfIrKWl3UmY=; b=XoQt90aWNOeAUhR38WJsJ3ahY8ZB4IKNAdZzU0bbsSqm3SoPBF7Q0ZL0pe3zZ6cIri Miy+7geAPm375YPDdcI4cmP++LkMWOwDPlvSRLdx2wVQ0HHAcxfTp09YEffG3vPicndS 0o9AgbVo2IlX/O013Ko1cMaWnq6fG9g+2WMlqL4rsMbKnnnMMkIVOIHmo6gKJIz7KiRT 31pDv3P/BuO29abXGBvqVflyJ5fQb8tRlLarWWWa6plgJ9WCM+lU3k9HweZTXKNeASoy YR8d5XjRMkC0yiYd8yfJUPuVmdCRJxzn4r3M1VRK0ZjKWk6tsOaVkl4gi/x3EuwuOV/T tPmQ== MIME-Version: 1.0 X-Received: by 10.66.158.130 with SMTP id wu2mr59411017pab.59.1409763746426; Wed, 03 Sep 2014 10:02:26 -0700 (PDT) Received: by 10.70.87.8 with HTTP; Wed, 3 Sep 2014 10:02:26 -0700 (PDT) In-Reply-To: References: <974E75E8-0977-41DE-9054-C5E556855D82@citrix.com> Date: Wed, 3 Sep 2014 18:02:26 +0100 Message-ID: From: David Scott To: Thomas Leonard Cc: Dave Scott , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Profiling Mirage on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8332300584034223263==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8332300584034223263== Content-Type: multipart/alternative; boundary=047d7b86c81452b55005022c33a0 --047d7b86c81452b55005022c33a0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Sep 3, 2014 at 5:03 PM, Thomas Leonard wrote: > On 2 September 2014 15:10, Thomas Leonard wrote: > > On 21 August 2014 18:30, Dave Scott wrote: > >> Hi, > >> > >> On 21 Aug 2014, at 12:10, Thomas Leonard wrote: > > [...] > >>> I've written up the profiling I've done so far here: > >>> > >>> http://roscidus.com/blog/blog/2014/08/15/optimising-the-unikernel/ > >>> > >>> The graphs are quite interesting - if people familiar with the code > >>> could explain what's going on (especially with the block device) that > >>> would be great! > >> > >> The graphs are interesting! > >> > >> IIRC the grant unmap operation is very expensive since it involves a > TLB shootdown. This adds a large amount (relatively, compared to modern > flash-based disks) to the request/response latency. I think this is why t= he > performance is so terrible with one request at a time. I suspect that the > batching you=E2=80=99re seeing with two requests is an artefact of the ba= ckend, > which is probably trying to unmap both grant references at once for > efficiency. When I wrote a user-space block backend batching the unmaps > made a massive difference. > > > > I wonder if this applies to ARM. You should be able to invalidate > > individual TLB entries there, I think. > > > >> There is a block protocol extension called =E2=80=9Cpersistent grants= =E2=80=9D that we > haven=E2=80=99t implemented (yet). This does the obvious thing and pre-sh= ares a set > of pages. We might suffer a bit because of extra copies (i.e. we might ha= ve > to copy into the pre-shared pages) but we would save the unmap overhead, = so > it might be worth it. > > > > Had a go at this, but it didn't make much difference. However, I've > > discovered that dd in dom0 isn't too fast either. I originally tested > > with hdparm, which reports 20 MB/s as expected: > > > > $ hdparm -t /dev/mmcblk0 > > Timing buffered disk reads: 62 MB in 3.07 seconds =3D 20.21 MB/sec > > > > dd's speed seems to depend a lot on the block size. Using > > 4096*11=3D45056 bytes (which I assume is what dom0 would do in response > > to a guest request), I get 16.9 MB/s: > > > > $ dd iflag=3Ddirect if=3D/dev/vg0/bench of=3D/dev/null bs=3D45056 coun= t=3D1000 > > 1000+0 records in > > 1000+0 records out > > 45056000 bytes (45 MB) copied, 2.65911 s, 16.9 MB/s > > > > bs=3D65536 gives 18.8 MB/s and bs=3D131072 gives 20.8 MB/s. Linux domU > > reports 20.36 MB/sec from hdparm but only 18.6 MB/s from dd > > (bs=3D131072). So perhaps Mirage is doing pretty well already. > > I had a look at how hdparm gets the full speed. It's using 256 pages > per request, which requires support for indirect pages in blkfront > (with direct requests, the maximum is 11 pages per request). > > I added support here: > > https://github.com/talex5/mirage-block-xen/commits/master > > With this, I got 21.32 MB/s read and 9.17 MB/s write. The results vary > a fair bit with block size (those were the best), but that seems like > an improvement (the previous best was 18.27r and 7.07w). > Nice! When you're happy with it, please make a pull request... Cheers, Dave Scott --047d7b86c81452b55005022c33a0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Wed, Sep 3, 2014 at 5:03 PM, Thomas Leonard &l= t;talex5@gmail.com> wrote:
On 2= September 2014 15:10, Thomas Leonard <talex5@gmail.com> wrote:
> On 21 August 2014 18:30, Dave Scott <Dave.Scott@citrix.com> wrote:
>> Hi,
>>
>> On 21 Aug 2014, at 12:10, Thomas Leonard <talex5@gmail.com> wrote:
> [...]
>>> I've written up the profiling I've done so far here: >>>
>>> http://roscidus.com/blog/blog/2014/08/15= /optimising-the-unikernel/
>>>
>>> The graphs are quite interesting - if people familiar with the= code
>>> could explain what's going on (especially with the block d= evice) that
>>> would be great!
>>
>> The graphs are interesting!
>>
>> IIRC the grant unmap operation is very expensive since it involves= a TLB shootdown. This adds a large amount (relatively, compared to modern = flash-based disks) to the request/response latency. I think this is why the= performance is so terrible with one request at a time. I suspect that the = batching you=E2=80=99re seeing with two requests is an artefact of the back= end, which is probably trying to unmap both grant references at once for ef= ficiency. When I wrote a user-space block backend batching the unmaps made = a massive difference.
>
> I wonder if this applies to ARM. You should be able to invalidate
> individual TLB entries there, I think.
>
>> There is a block protocol extension called =E2=80=9Cpersistent gra= nts=E2=80=9D that we haven=E2=80=99t implemented (yet). This does the obvio= us thing and pre-shares a set of pages. We might suffer a bit because of ex= tra copies (i.e. we might have to copy into the pre-shared pages) but we wo= uld save the unmap overhead, so it might be worth it.
>
> Had a go at this, but it didn't make much difference. However, I&#= 39;ve
> discovered that dd in dom0 isn't too fast either. I originally tes= ted
> with hdparm, which reports 20 MB/s as expected:
>
> $ hdparm -t /dev/mmcblk0
>=C2=A0 Timing buffered disk reads:=C2=A0 62 MB in=C2=A0 3.07 seconds = =3D=C2=A0 20.21 MB/sec
>
> dd's speed seems to depend a lot on the block size. Using
> 4096*11=3D45056 bytes (which I assume is what dom0 would do in respons= e
> to a guest request), I get 16.9 MB/s:
>
> $ dd iflag=3Ddirect if=3D/dev/vg0/bench=C2=A0 of=3D/dev/null bs=3D4505= 6 count=3D1000
> 1000+0 records in
> 1000+0 records out
> 45056000 bytes (45 MB) copied, 2.65911 s, 16.9 MB/s
>
> bs=3D65536 gives 18.8 MB/s and bs=3D131072 gives 20.8 MB/s. Linux domU=
> reports 20.36 MB/sec from hdparm but only 18.6 MB/s from dd
> (bs=3D131072). So perhaps Mirage is doing pretty well already.

I had a look at how hdparm gets the full speed. It's using = 256 pages
per request, which requires support for indirect pages in blkfront
(with direct requests, the maximum is 11 pages per request).

I added support here:

=C2=A0 https://github.com/talex5/mirage-block-xen/commits/mast= er

With this, I got 21.32 MB/s read and 9.17 MB/s write. The results vary
a fair bit with block size (those were the best), but that seems like
an improvement (the previous best was 18.27r and 7.07w).

Nice! When you're happy with it, please make a pull r= equest...

Cheers,
Dave Scott
--047d7b86c81452b55005022c33a0-- --===============8332300584034223263== 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 --===============8332300584034223263==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 18:35:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 18:35:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPFOq-0004sF-GB; Wed, 03 Sep 2014 18:35:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPFOo-0004sA-U4 for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 18:35:19 +0000 Received: from [193.109.254.147:17070] by server-9.bemta-14.messagelabs.com id 98/E2-31535-66F57045; Wed, 03 Sep 2014 18:35:18 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1409769317!13249549!1 X-Originating-IP: [209.85.212.173] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27944 invoked from network); 3 Sep 2014 18:35:17 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 18:35:17 -0000 Received: by mail-wi0-f173.google.com with SMTP id cc10so1506516wib.12 for ; Wed, 03 Sep 2014 11:35:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YNHjfz0h6c/a59NAU3vjSoqaOaD/Go8oIgPdBnDP+Nc=; b=kcyrQhdKtxtGrFhKniy2iqot+jb2UkAJp7hNRydHoW4z8kh5xCdcqvs2M3E4xwljVo o/KkuL/RMuLAUX9PTC/S43lrp9chA6N27d99TiKy70CCEisXnl7+sUsCBovLJ91zLB+c TPBipxJAgDOWa6fNc+d27iAMP1dtyRUSzwJ/Fn2IH44Fu0sdI9FyyHQtEHOzp+9KBL8D gEYJNbE2qHY05JqOj/QnAzvkzLu5Oq+M/tGfgPtfmqcyRoIGqxbbNcCjG1/X2omx8ovO 1sFcmZNaLZSaCoaEV4MWtAKzioV0c7gsyzXiYslMqUpOivyJ2MOcvb9SebNL2Dp4H3Xo OTTw== MIME-Version: 1.0 X-Received: by 10.180.87.231 with SMTP id bb7mr213460wib.63.1409769316809; Wed, 03 Sep 2014 11:35:16 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Wed, 3 Sep 2014 11:35:16 -0700 (PDT) Date: Wed, 3 Sep 2014 14:35:16 -0400 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] First Mirage/Ocaml project ideas X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4112319770264051494==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4112319770264051494== Content-Type: multipart/alternative; boundary=f46d0444e9cf5801e105022d7f62 --f46d0444e9cf5801e105022d7f62 Content-Type: text/plain; charset=UTF-8 Greetings, You have been good at promoting and evangelizing Mirage and Ocaml, I am a recent convert to the movement. I was hoping for some ideas for a small meaningful project that I could work on to learn ocaml and in the end give back to the Mirage project. Something not time critical. One idea I came up with was: NTPd (Network Time Protocol server). Ironic that I don't want a project that is *time critical* hahah. http://www.ntp.org/rfc.html I am open to ideas from the list. Warm regards, --Stephen --f46d0444e9cf5801e105022d7f62 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Greetings,

You have been good at promot= ing and evangelizing Mirage and Ocaml, =C2=A0I am a recent convert to the m= ovement. =C2=A0I was hoping for some ideas for a small meaningful project t= hat I could work on to learn ocaml and in the end give back to the Mirage p= roject. =C2=A0Something not time critical.

One idea I came up with was: NTPd (Network Time Protoco= l server). =C2=A0Ironic that I don't want a project that is *time criti= cal* hahah.


I am open to ideas from the list.

<= /div>
Warm regards,

--Stephen
--f46d0444e9cf5801e105022d7f62-- --===============4112319770264051494== 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 --===============4112319770264051494==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 03 18:35:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 03 Sep 2014 18:35:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPFOq-0004sF-GB; Wed, 03 Sep 2014 18:35:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPFOo-0004sA-U4 for mirageos-devel@lists.xenproject.org; Wed, 03 Sep 2014 18:35:19 +0000 Received: from [193.109.254.147:17070] by server-9.bemta-14.messagelabs.com id 98/E2-31535-66F57045; Wed, 03 Sep 2014 18:35:18 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1409769317!13249549!1 X-Originating-IP: [209.85.212.173] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27944 invoked from network); 3 Sep 2014 18:35:17 -0000 Received: from mail-wi0-f173.google.com (HELO mail-wi0-f173.google.com) (209.85.212.173) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 3 Sep 2014 18:35:17 -0000 Received: by mail-wi0-f173.google.com with SMTP id cc10so1506516wib.12 for ; Wed, 03 Sep 2014 11:35:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YNHjfz0h6c/a59NAU3vjSoqaOaD/Go8oIgPdBnDP+Nc=; b=kcyrQhdKtxtGrFhKniy2iqot+jb2UkAJp7hNRydHoW4z8kh5xCdcqvs2M3E4xwljVo o/KkuL/RMuLAUX9PTC/S43lrp9chA6N27d99TiKy70CCEisXnl7+sUsCBovLJ91zLB+c TPBipxJAgDOWa6fNc+d27iAMP1dtyRUSzwJ/Fn2IH44Fu0sdI9FyyHQtEHOzp+9KBL8D gEYJNbE2qHY05JqOj/QnAzvkzLu5Oq+M/tGfgPtfmqcyRoIGqxbbNcCjG1/X2omx8ovO 1sFcmZNaLZSaCoaEV4MWtAKzioV0c7gsyzXiYslMqUpOivyJ2MOcvb9SebNL2Dp4H3Xo OTTw== MIME-Version: 1.0 X-Received: by 10.180.87.231 with SMTP id bb7mr213460wib.63.1409769316809; Wed, 03 Sep 2014 11:35:16 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Wed, 3 Sep 2014 11:35:16 -0700 (PDT) Date: Wed, 3 Sep 2014 14:35:16 -0400 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] First Mirage/Ocaml project ideas X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4112319770264051494==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4112319770264051494== Content-Type: multipart/alternative; boundary=f46d0444e9cf5801e105022d7f62 --f46d0444e9cf5801e105022d7f62 Content-Type: text/plain; charset=UTF-8 Greetings, You have been good at promoting and evangelizing Mirage and Ocaml, I am a recent convert to the movement. I was hoping for some ideas for a small meaningful project that I could work on to learn ocaml and in the end give back to the Mirage project. Something not time critical. One idea I came up with was: NTPd (Network Time Protocol server). Ironic that I don't want a project that is *time critical* hahah. http://www.ntp.org/rfc.html I am open to ideas from the list. Warm regards, --Stephen --f46d0444e9cf5801e105022d7f62 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Greetings,

You have been good at promot= ing and evangelizing Mirage and Ocaml, =C2=A0I am a recent convert to the m= ovement. =C2=A0I was hoping for some ideas for a small meaningful project t= hat I could work on to learn ocaml and in the end give back to the Mirage p= roject. =C2=A0Something not time critical.

One idea I came up with was: NTPd (Network Time Protoco= l server). =C2=A0Ironic that I don't want a project that is *time criti= cal* hahah.


I am open to ideas from the list.

<= /div>
Warm regards,

--Stephen
--f46d0444e9cf5801e105022d7f62-- --===============4112319770264051494== 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 --===============4112319770264051494==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 10:38:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 10:38:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPURE-0003AR-68; Thu, 04 Sep 2014 10:38:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPURD-0003AJ-Eh for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 10:38:47 +0000 Received: from [85.158.139.211:56175] by server-15.bemta-5.messagelabs.com id EB/2F-12002-63148045; Thu, 04 Sep 2014 10:38:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1409827126!7119220!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22075 invoked from network); 4 Sep 2014 10:38:46 -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; 4 Sep 2014 10:38:46 -0000 Received: (qmail 16879 invoked by uid 634); 4 Sep 2014 10:38:45 -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 Unknown (HELO [172.25.35.29]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 04 Sep 2014 11:38:44 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 4 Sep 2014 12:38:43 +0200 Message-Id: References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] First Mirage/Ocaml project ideas X-BeenThere: mirageos-devel@lists.xenproject.org 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 brief reply as I'm at ICFP this week) Welcome! NTP would be an excellent protocol to start with, since it has a relatively simple binary format, and some non-trivial algorithmic calculation that would make for a nice concise implementation in OCaml. Feel free to ask questions at any level on this list... -anil On 3 Sep 2014, at 20:35, Stephen Mack wrote: > Greetings, > > You have been good at promoting and evangelizing Mirage and Ocaml, I am a recent convert to the movement. I was hoping for some ideas for a small meaningful project that I could work on to learn ocaml and in the end give back to the Mirage project. Something not time critical. > > One idea I came up with was: NTPd (Network Time Protocol server). Ironic that I don't want a project that is *time critical* hahah. > > http://www.ntp.org/rfc.html > > I am open to ideas from the list. > > Warm regards, > > --Stephen > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 10:38:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 10:38:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPURE-0003AR-68; Thu, 04 Sep 2014 10:38:48 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPURD-0003AJ-Eh for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 10:38:47 +0000 Received: from [85.158.139.211:56175] by server-15.bemta-5.messagelabs.com id EB/2F-12002-63148045; Thu, 04 Sep 2014 10:38:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1409827126!7119220!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22075 invoked from network); 4 Sep 2014 10:38:46 -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; 4 Sep 2014 10:38:46 -0000 Received: (qmail 16879 invoked by uid 634); 4 Sep 2014 10:38:45 -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 Unknown (HELO [172.25.35.29]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 04 Sep 2014 11:38:44 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 4 Sep 2014 12:38:43 +0200 Message-Id: References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] First Mirage/Ocaml project ideas X-BeenThere: mirageos-devel@lists.xenproject.org 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 brief reply as I'm at ICFP this week) Welcome! NTP would be an excellent protocol to start with, since it has a relatively simple binary format, and some non-trivial algorithmic calculation that would make for a nice concise implementation in OCaml. Feel free to ask questions at any level on this list... -anil On 3 Sep 2014, at 20:35, Stephen Mack wrote: > Greetings, > > You have been good at promoting and evangelizing Mirage and Ocaml, I am a recent convert to the movement. I was hoping for some ideas for a small meaningful project that I could work on to learn ocaml and in the end give back to the Mirage project. Something not time critical. > > One idea I came up with was: NTPd (Network Time Protocol server). Ironic that I don't want a project that is *time critical* hahah. > > http://www.ntp.org/rfc.html > > I am open to ideas from the list. > > Warm regards, > > --Stephen > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 13:47:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 13:47: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 1XPXNq-0000w0-OJ; Thu, 04 Sep 2014 13:47:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXNp-0000vr-Bm for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 13:47:29 +0000 Received: from [193.109.254.147:27281] by server-15.bemta-14.messagelabs.com id 1C/14-30948-07D68045; Thu, 04 Sep 2014 13:47:28 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1409838446!13508215!1 X-Originating-IP: [209.85.160.171] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8898 invoked from network); 4 Sep 2014 13:47:27 -0000 Received: from mail-yk0-f171.google.com (HELO mail-yk0-f171.google.com) (209.85.160.171) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2014 13:47:27 -0000 Received: by mail-yk0-f171.google.com with SMTP id 9so6054717ykp.16 for ; Thu, 04 Sep 2014 06:47:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=+SmOiDq/mzwo5QJOL/CRfUSonDx4pvgN2EmXee2BZo0=; b=ouTIkKs9ZQJhfnpjRfnL3t7rfjO2HOzT3UvuTE5prCC0/p5GvWpLYHtl8+AP6en/0U ID8K4OqgGG6V2qV7p8db0vum5WFjwNsBE+oACd28F5y8u0F+RfKHpEjB+j+yauN4NmxD duGBggiadjHOAAtVFjBHtJ1Igt2kGAusVfeqVxRqIXp9VQHy/0KZjlwsaV0keN3aeZlL 68ce4QAgbpxoSWsa81HRYnMZbxH6e0K0LiYb+ZDfKvWhNCw9wwKrJvww0Zlf3lmhx1n4 sqNDjI9LjPv1g6XXjkot5Sy8STtTMkidzZ4xUw4mqCR1hLYagx8janauvQF0CckzAKOc blOA== X-Received: by 10.236.90.208 with SMTP id e56mr1293388yhf.176.1409838446254; Thu, 04 Sep 2014 06:47:26 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id y67sm8658177yhc.11.2014.09.04.06.47.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Sep 2014 06:47:25 -0700 (PDT) From: Lars Kurth Message-Id: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> Date: Thu, 4 Sep 2014 14:47:23 +0100 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3888634229065416325==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3888634229065416325== Content-Type: multipart/alternative; boundary="Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621" --Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Also, have some of the URL=92s changed? Some of the links from = http://xenproject.org/developers/teams/mirage-os.html seem to not go to = the right places anymore? Regards Lars= --Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Also, have = some of the URL=92s changed? Some of the links from http://xenp= roject.org/developers/teams/mirage-os.html seem to not go to = the right places anymore?
Regards
Lars
= --Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621-- --===============3888634229065416325== 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 --===============3888634229065416325==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 13:47:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 13:47: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 1XPXNq-0000w0-OJ; Thu, 04 Sep 2014 13:47:30 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXNp-0000vr-Bm for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 13:47:29 +0000 Received: from [193.109.254.147:27281] by server-15.bemta-14.messagelabs.com id 1C/14-30948-07D68045; Thu, 04 Sep 2014 13:47:28 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1409838446!13508215!1 X-Originating-IP: [209.85.160.171] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8898 invoked from network); 4 Sep 2014 13:47:27 -0000 Received: from mail-yk0-f171.google.com (HELO mail-yk0-f171.google.com) (209.85.160.171) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2014 13:47:27 -0000 Received: by mail-yk0-f171.google.com with SMTP id 9so6054717ykp.16 for ; Thu, 04 Sep 2014 06:47:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=+SmOiDq/mzwo5QJOL/CRfUSonDx4pvgN2EmXee2BZo0=; b=ouTIkKs9ZQJhfnpjRfnL3t7rfjO2HOzT3UvuTE5prCC0/p5GvWpLYHtl8+AP6en/0U ID8K4OqgGG6V2qV7p8db0vum5WFjwNsBE+oACd28F5y8u0F+RfKHpEjB+j+yauN4NmxD duGBggiadjHOAAtVFjBHtJ1Igt2kGAusVfeqVxRqIXp9VQHy/0KZjlwsaV0keN3aeZlL 68ce4QAgbpxoSWsa81HRYnMZbxH6e0K0LiYb+ZDfKvWhNCw9wwKrJvww0Zlf3lmhx1n4 sqNDjI9LjPv1g6XXjkot5Sy8STtTMkidzZ4xUw4mqCR1hLYagx8janauvQF0CckzAKOc blOA== X-Received: by 10.236.90.208 with SMTP id e56mr1293388yhf.176.1409838446254; Thu, 04 Sep 2014 06:47:26 -0700 (PDT) Received: from [10.80.114.159] ([185.25.64.249]) by mx.google.com with ESMTPSA id y67sm8658177yhc.11.2014.09.04.06.47.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 04 Sep 2014 06:47:25 -0700 (PDT) From: Lars Kurth Message-Id: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> Date: Thu, 4 Sep 2014 14:47:23 +0100 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3888634229065416325==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3888634229065416325== Content-Type: multipart/alternative; boundary="Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621" --Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Also, have some of the URL=92s changed? Some of the links from = http://xenproject.org/developers/teams/mirage-os.html seem to not go to = the right places anymore? Regards Lars= --Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
Also, have = some of the URL=92s changed? Some of the links from http://xenp= roject.org/developers/teams/mirage-os.html seem to not go to = the right places anymore?
Regards
Lars
= --Apple-Mail=_3A1218F4-82D2-4B67-8D49-B1D7B9C85621-- --===============3888634229065416325== 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 --===============3888634229065416325==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 13:55:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 13:55:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXVP-00019y-5S; Thu, 04 Sep 2014 13:55:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXVN-00019t-DI for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 13:55:17 +0000 Received: from [85.158.143.35:17950] by server-1.bemta-4.messagelabs.com id FE/05-05872-44F68045; Thu, 04 Sep 2014 13:55:16 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1409838916!10165906!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28236 invoked from network); 4 Sep 2014 13:55:16 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2014 13:55:16 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [185.25.64.249] (port=44883 helo=[10.80.3.75]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jjl25) (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1XPXVL-0008D5-Ez (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 04 Sep 2014 14:55:15 +0100 Message-ID: <54086F46.1030001@cam.ac.uk> Date: Thu, 04 Sep 2014 14:55:18 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> In-Reply-To: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> Subject: Re: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0736082941259887111==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============0736082941259887111== Content-Type: multipart/alternative; boundary="------------060500030308080908010707" This is a multi-part message in MIME format. --------------060500030308080908010707 Content-Type: text/plain; charset=windows-1252 Content-Length: 570 Content-Transfer-Encoding: quoted-printable It's working for me right now. Which links are incorrect=3F I couldn't see any obviously wrong from a quick scan just now. Jon On 04/09/14 14:47, Lars Kurth wrote: > Also, have some of the URL=92s changed=3F Some of the links > from http://xenproject.org/developers/teams/mirage-os.html seem to not > go to the right places anymore=3F > Regards > Lars > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --------------060500030308080908010707 Content-Type: text/html; charset=windows-1252 Content-Length: 1777 Content-Transfer-Encoding: quoted-printable
It's working for me right now.

Which links are incorrect=3F I couldn't see any obviously wrong from a quick scan just now.

Jon

On 04/09/14 14:47, Lars Kurth wrote:
Also, have some of the URL=92s changed=3F Some of the links from=A0http://xenproject.org/developers/teams/mirage-os.html=A0seem to not go to the right places anymore=3F
Regards
Lars


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

--------------060500030308080908010707-- --===============0736082941259887111== 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 --===============0736082941259887111==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 13:55:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 13:55:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXVP-00019y-5S; Thu, 04 Sep 2014 13:55:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXVN-00019t-DI for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 13:55:17 +0000 Received: from [85.158.143.35:17950] by server-1.bemta-4.messagelabs.com id FE/05-05872-44F68045; Thu, 04 Sep 2014 13:55:16 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1409838916!10165906!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28236 invoked from network); 4 Sep 2014 13:55:16 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 4 Sep 2014 13:55:16 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [185.25.64.249] (port=44883 helo=[10.80.3.75]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jjl25) (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1XPXVL-0008D5-Ez (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 04 Sep 2014 14:55:15 +0100 Message-ID: <54086F46.1030001@cam.ac.uk> Date: Thu, 04 Sep 2014 14:55:18 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> In-Reply-To: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> Subject: Re: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0736082941259887111==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============0736082941259887111== Content-Type: multipart/alternative; boundary="------------060500030308080908010707" This is a multi-part message in MIME format. --------------060500030308080908010707 Content-Type: text/plain; charset=windows-1252 Content-Length: 570 Content-Transfer-Encoding: quoted-printable It's working for me right now. Which links are incorrect=3F I couldn't see any obviously wrong from a quick scan just now. Jon On 04/09/14 14:47, Lars Kurth wrote: > Also, have some of the URL=92s changed=3F Some of the links > from http://xenproject.org/developers/teams/mirage-os.html seem to not > go to the right places anymore=3F > Regards > Lars > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --------------060500030308080908010707 Content-Type: text/html; charset=windows-1252 Content-Length: 1777 Content-Transfer-Encoding: quoted-printable
It's working for me right now.

Which links are incorrect=3F I couldn't see any obviously wrong from a quick scan just now.

Jon

On 04/09/14 14:47, Lars Kurth wrote:
Also, have some of the URL=92s changed=3F Some of the links from=A0http://xenproject.org/developers/teams/mirage-os.html=A0seem to not go to the right places anymore=3F
Regards
Lars


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

--------------060500030308080908010707-- --===============0736082941259887111== 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 --===============0736082941259887111==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 04 13:57:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 13:57:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXXg-0001Bb-EX; Thu, 04 Sep 2014 13:57:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXXe-0001BW-GS for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 13:57:38 +0000 Received: from [85.158.137.68:3901] by server-5.bemta-3.messagelabs.com id 44/27-30889-1DF68045; Thu, 04 Sep 2014 13:57:37 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1409839057!12566224!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15310 invoked from network); 4 Sep 2014 13:57:37 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2014 13:57:37 -0000 X-IronPort-AV: E=Sophos;i="5.04,466,1406592000"; d="scan'208";a="24506059" From: Dave Scott To: Lars Kurth Thread-Topic: [MirageOS-devel] Openmirage.org seems to be down Thread-Index: AQHPyEbRJGhHQEWPF0GKXMA9YiJaS5vw3kSA Date: Thu, 4 Sep 2014 13:57:36 +0000 Message-ID: References: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> In-Reply-To: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <73FA63A9F542C24DA3556F95594D7CCA@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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 I think the server is up=97 I can ping it and I get HTTP on port 80: [djs@dark ~]$ telnet www.openmirage.org 80 Trying 128.232.97.54... Connected to www.openmirage.org. Escape character is '^]'. GET / HTTP/1.0 HTTP/1.1 200 OK content-length: 8761 content-type: text/html; charset=3DUTF-8 =85 On 4 Sep 2014, at 14:47, Lars Kurth wrote: > Also, have some of the URL=92s changed? Some of the links from http://xen= project.org/developers/teams/mirage-os.html seem to not go to the right pla= ces anymore? Which ones? I clicked on a few which looked ok (superficially at least). Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 04 13:57:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 13:57:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXXg-0001Bb-EX; Thu, 04 Sep 2014 13:57:40 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPXXe-0001BW-GS for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 13:57:38 +0000 Received: from [85.158.137.68:3901] by server-5.bemta-3.messagelabs.com id 44/27-30889-1DF68045; Thu, 04 Sep 2014 13:57:37 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1409839057!12566224!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15310 invoked from network); 4 Sep 2014 13:57:37 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Sep 2014 13:57:37 -0000 X-IronPort-AV: E=Sophos;i="5.04,466,1406592000"; d="scan'208";a="24506059" From: Dave Scott To: Lars Kurth Thread-Topic: [MirageOS-devel] Openmirage.org seems to be down Thread-Index: AQHPyEbRJGhHQEWPF0GKXMA9YiJaS5vw3kSA Date: Thu, 4 Sep 2014 13:57:36 +0000 Message-ID: References: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> In-Reply-To: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <73FA63A9F542C24DA3556F95594D7CCA@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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 I think the server is up=97 I can ping it and I get HTTP on port 80: [djs@dark ~]$ telnet www.openmirage.org 80 Trying 128.232.97.54... Connected to www.openmirage.org. Escape character is '^]'. GET / HTTP/1.0 HTTP/1.1 200 OK content-length: 8761 content-type: text/html; charset=3DUTF-8 =85 On 4 Sep 2014, at 14:47, Lars Kurth wrote: > Also, have some of the URL=92s changed? Some of the links from http://xen= project.org/developers/teams/mirage-os.html seem to not go to the right pla= ces anymore? Which ones? I clicked on a few which looked ok (superficially at least). Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 04 15:00:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 15:00: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 1XPYW6-0006GP-9V; Thu, 04 Sep 2014 15:00:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPYW4-0006GK-QP for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 15:00:04 +0000 Received: from [193.109.254.147:53504] by server-7.bemta-14.messagelabs.com id EA/FD-13362-47E78045; Thu, 04 Sep 2014 15:00:04 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1409842803!13532129!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24526 invoked from network); 4 Sep 2014 15:00:03 -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; 4 Sep 2014 15:00:03 -0000 Received: (qmail 525 invoked by uid 634); 4 Sep 2014 15:00:03 -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 Unknown (HELO [172.25.35.29]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 04 Sep 2014 15:59:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 4 Sep 2014 16:59:57 +0200 Message-Id: References: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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 A lot of Cambridge connectivity went down briefly. The unikernel is safe! We need to switch the live site to the distributed cluster of Xen/ARM Cubieboards soon to get higher uptime :-) On 4 Sep 2014, at 15:57, Dave Scott wrote: > = > I think the server is up=97 I can ping it and I get HTTP on port 80: > = > [djs@dark ~]$ telnet www.openmirage.org 80 > Trying 128.232.97.54... > Connected to www.openmirage.org. > Escape character is '^]'. > GET / HTTP/1.0 > = > HTTP/1.1 200 OK > content-length: 8761 > content-type: text/html; charset=3DUTF-8 > =85 > = > On 4 Sep 2014, at 14:47, Lars Kurth wrote: > = >> Also, have some of the URL=92s changed? Some of the links from http://xe= nproject.org/developers/teams/mirage-os.html seem to not go to the right pl= aces anymore? > = > Which ones? I clicked on a few which looked ok (superficially at least). > = > 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 Thu Sep 04 15:00:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 04 Sep 2014 15:00: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 1XPYW6-0006GP-9V; Thu, 04 Sep 2014 15:00:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPYW4-0006GK-QP for mirageos-devel@lists.xenproject.org; Thu, 04 Sep 2014 15:00:04 +0000 Received: from [193.109.254.147:53504] by server-7.bemta-14.messagelabs.com id EA/FD-13362-47E78045; Thu, 04 Sep 2014 15:00:04 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1409842803!13532129!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24526 invoked from network); 4 Sep 2014 15:00:03 -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; 4 Sep 2014 15:00:03 -0000 Received: (qmail 525 invoked by uid 634); 4 Sep 2014 15:00:03 -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 Unknown (HELO [172.25.35.29]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 04 Sep 2014 15:59:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 4 Sep 2014 16:59:57 +0200 Message-Id: References: <36D9B9E9-1FC6-4C5C-B67B-2F8C6C49E895@gmail.com> To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Openmirage.org seems to be down X-BeenThere: mirageos-devel@lists.xenproject.org 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 A lot of Cambridge connectivity went down briefly. The unikernel is safe! We need to switch the live site to the distributed cluster of Xen/ARM Cubieboards soon to get higher uptime :-) On 4 Sep 2014, at 15:57, Dave Scott wrote: > = > I think the server is up=97 I can ping it and I get HTTP on port 80: > = > [djs@dark ~]$ telnet www.openmirage.org 80 > Trying 128.232.97.54... > Connected to www.openmirage.org. > Escape character is '^]'. > GET / HTTP/1.0 > = > HTTP/1.1 200 OK > content-length: 8761 > content-type: text/html; charset=3DUTF-8 > =85 > = > On 4 Sep 2014, at 14:47, Lars Kurth wrote: > = >> Also, have some of the URL=92s changed? Some of the links from http://xe= nproject.org/developers/teams/mirage-os.html seem to not go to the right pl= aces anymore? > = > Which ones? I clicked on a few which looked ok (superficially at least). > = > 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 Fri Sep 05 00:10:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 00:10:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPh74-0000dI-2I; Fri, 05 Sep 2014 00:10:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPh72-0000dD-KN for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 00:10:48 +0000 Received: from [85.158.143.35:3719] by server-1.bemta-4.messagelabs.com id BB/7D-05872-78FF8045; Fri, 05 Sep 2014 00:10:47 +0000 X-Env-Sender: aaron.quamme@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1409875846!13710013!1 X-Originating-IP: [209.85.223.174] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16513 invoked from network); 5 Sep 2014 00:10:47 -0000 Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 00:10:47 -0000 Received: by mail-ie0-f174.google.com with SMTP id at20so12891397iec.19 for ; Thu, 04 Sep 2014 17:10:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=uGikAUcGHFOTd0odWQu46bM01QCrsLlEx9KUtuCv1xA=; b=DODuWVDUWdP6vA48EGLAbDGvHM7cyYHgZ0j94slijwF0vTLk7INXTB4zlw0Yo382Uo /NCb+yjE+2KV0K5351HoSeGhjXB5zBf0kQeyboqYdynL0qNFNs2CH0ed4Hg61tbEsduQ yv5top2scx/dUQCeKtYePRmyjaLbo38ZESmq0jy9E+GgIkPKOK2WEQ962ja0nhd1+tCe CuiP2yPk5GhHrbahJrUmao9unYtTaKi+dqiKHWCYGudjpdV6xbVZCuVmR5ba58I3aRoS 0mNnTL3IH/EnVEOX6eAv3NX85k6wCTHUNZJ9K2kMT5sApKObjXE0nA+e1MA0FylvJzj1 jCmQ== X-Received: by 10.42.88.133 with SMTP id c5mr10074209icm.83.1409875845917; Thu, 04 Sep 2014 17:10:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.117.229 with HTTP; Thu, 4 Sep 2014 17:10:25 -0700 (PDT) From: Aaron Quamme Date: Thu, 4 Sep 2014 19:10:25 -0500 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6249150609103381985==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6249150609103381985== Content-Type: multipart/alternative; boundary=90e6ba3fd297f92fb50502464c21 --90e6ba3fd297f92fb50502464c21 Content-Type: text/plain; charset=UTF-8 Hello, I'm looking for suggestions in the vein of Stephen's project - something relatively small and non-critical but still useful. I discovered Mirage and unikernels last week and find topic rather fascinating, so I decided to make it the focus of my undergraduate research project this semester. I don't have much experience with OCaml or with functional languages in general, but I've started on Real World OCaml. I'd greatly appreciate any suggestions you provide! -- Aaron --90e6ba3fd297f92fb50502464c21 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I'm looking for suggestions = in the vein of Stephen's project - something relatively small and non-c= ritical but still useful. I discovered Mirage and unikernels last week and = find topic rather fascinating, so I decided to make it the focus of my unde= rgraduate research project this semester. I don't have much experience = with OCaml or with functional languages in general, but I've started on= Real World OCaml.

I'd greatly appreciate any suggestions you provide!=

-- Aaron
--90e6ba3fd297f92fb50502464c21-- --===============6249150609103381985== 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 --===============6249150609103381985==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 00:10:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 00:10:56 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPh74-0000dI-2I; Fri, 05 Sep 2014 00:10:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPh72-0000dD-KN for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 00:10:48 +0000 Received: from [85.158.143.35:3719] by server-1.bemta-4.messagelabs.com id BB/7D-05872-78FF8045; Fri, 05 Sep 2014 00:10:47 +0000 X-Env-Sender: aaron.quamme@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1409875846!13710013!1 X-Originating-IP: [209.85.223.174] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16513 invoked from network); 5 Sep 2014 00:10:47 -0000 Received: from mail-ie0-f174.google.com (HELO mail-ie0-f174.google.com) (209.85.223.174) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 00:10:47 -0000 Received: by mail-ie0-f174.google.com with SMTP id at20so12891397iec.19 for ; Thu, 04 Sep 2014 17:10:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=uGikAUcGHFOTd0odWQu46bM01QCrsLlEx9KUtuCv1xA=; b=DODuWVDUWdP6vA48EGLAbDGvHM7cyYHgZ0j94slijwF0vTLk7INXTB4zlw0Yo382Uo /NCb+yjE+2KV0K5351HoSeGhjXB5zBf0kQeyboqYdynL0qNFNs2CH0ed4Hg61tbEsduQ yv5top2scx/dUQCeKtYePRmyjaLbo38ZESmq0jy9E+GgIkPKOK2WEQ962ja0nhd1+tCe CuiP2yPk5GhHrbahJrUmao9unYtTaKi+dqiKHWCYGudjpdV6xbVZCuVmR5ba58I3aRoS 0mNnTL3IH/EnVEOX6eAv3NX85k6wCTHUNZJ9K2kMT5sApKObjXE0nA+e1MA0FylvJzj1 jCmQ== X-Received: by 10.42.88.133 with SMTP id c5mr10074209icm.83.1409875845917; Thu, 04 Sep 2014 17:10:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.117.229 with HTTP; Thu, 4 Sep 2014 17:10:25 -0700 (PDT) From: Aaron Quamme Date: Thu, 4 Sep 2014 19:10:25 -0500 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6249150609103381985==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6249150609103381985== Content-Type: multipart/alternative; boundary=90e6ba3fd297f92fb50502464c21 --90e6ba3fd297f92fb50502464c21 Content-Type: text/plain; charset=UTF-8 Hello, I'm looking for suggestions in the vein of Stephen's project - something relatively small and non-critical but still useful. I discovered Mirage and unikernels last week and find topic rather fascinating, so I decided to make it the focus of my undergraduate research project this semester. I don't have much experience with OCaml or with functional languages in general, but I've started on Real World OCaml. I'd greatly appreciate any suggestions you provide! -- Aaron --90e6ba3fd297f92fb50502464c21 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I'm looking for suggestions = in the vein of Stephen's project - something relatively small and non-c= ritical but still useful. I discovered Mirage and unikernels last week and = find topic rather fascinating, so I decided to make it the focus of my unde= rgraduate research project this semester. I don't have much experience = with OCaml or with functional languages in general, but I've started on= Real World OCaml.

I'd greatly appreciate any suggestions you provide!=

-- Aaron
--90e6ba3fd297f92fb50502464c21-- --===============6249150609103381985== 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 --===============6249150609103381985==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 09:54:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 09:54: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 1XPqE7-00086q-1A; Fri, 05 Sep 2014 09:54:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqE6-00086Q-8Z for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 09:54:42 +0000 Received: from [85.158.137.68:42117] by server-12.bemta-3.messagelabs.com id 98/2E-01574-16889045; Fri, 05 Sep 2014 09:54:41 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1409910880!12720577!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16678 invoked from network); 5 Sep 2014 09:54:41 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 09:54:41 -0000 X-IronPort-AV: E=Sophos;i="5.04,471,1406592000"; d="scan'208";a="24529953" From: Dave Scott To: Aaron Quamme Thread-Topic: [MirageOS-devel] Mirage project suggestions for another newcomer Thread-Index: AQHPyJ3laeeuhDAYxU2zhIRLMCvMmJvyLA2A Date: Fri, 5 Sep 2014 09:54:39 +0000 Message-ID: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Aaron. On 5 Sep 2014, at 01:10, Aaron Quamme wrote: > Hello, > = > I'm looking for suggestions in the vein of Stephen's project - something = relatively small and non-critical but still useful. I discovered Mirage and= unikernels last week and find topic rather fascinating, so I decided to ma= ke it the focus of my undergraduate research project this semester. I don't= have much experience with OCaml or with functional languages in general, b= ut I've started on Real World OCaml. > = > I'd greatly appreciate any suggestions you provide! How about a DHCP server implementation? We already have a DHCP client: https://github.com/mirage/mirage-tcpip/tree/master/dhcp A DHCP server would be handy if we want to do fancy network stuff in future= e.g. for some kind of DHCP + NAT + VPN appliance. I=92m sure other people have other suggestions too! Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 05 09:54:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 09:54: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 1XPqE7-00086q-1A; Fri, 05 Sep 2014 09:54:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqE6-00086Q-8Z for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 09:54:42 +0000 Received: from [85.158.137.68:42117] by server-12.bemta-3.messagelabs.com id 98/2E-01574-16889045; Fri, 05 Sep 2014 09:54:41 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1409910880!12720577!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16678 invoked from network); 5 Sep 2014 09:54:41 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 09:54:41 -0000 X-IronPort-AV: E=Sophos;i="5.04,471,1406592000"; d="scan'208";a="24529953" From: Dave Scott To: Aaron Quamme Thread-Topic: [MirageOS-devel] Mirage project suggestions for another newcomer Thread-Index: AQHPyJ3laeeuhDAYxU2zhIRLMCvMmJvyLA2A Date: Fri, 5 Sep 2014 09:54:39 +0000 Message-ID: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Aaron. On 5 Sep 2014, at 01:10, Aaron Quamme wrote: > Hello, > = > I'm looking for suggestions in the vein of Stephen's project - something = relatively small and non-critical but still useful. I discovered Mirage and= unikernels last week and find topic rather fascinating, so I decided to ma= ke it the focus of my undergraduate research project this semester. I don't= have much experience with OCaml or with functional languages in general, b= ut I've started on Real World OCaml. > = > I'd greatly appreciate any suggestions you provide! How about a DHCP server implementation? We already have a DHCP client: https://github.com/mirage/mirage-tcpip/tree/master/dhcp A DHCP server would be handy if we want to do fancy network stuff in future= e.g. for some kind of DHCP + NAT + VPN appliance. I=92m sure other people have other suggestions too! Cheers, Dave _______________________________________________ MirageOS-devel 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 Sep 05 10:03:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:03: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 1XPqMo-00025R-B7; Fri, 05 Sep 2014 10:03:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqMm-000250-LI for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:03:40 +0000 Received: from [193.109.254.147:45580] by server-15.bemta-14.messagelabs.com id 3B/A1-30948-B7A89045; Fri, 05 Sep 2014 10:03:39 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1409911417!13690853!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13645 invoked from network); 5 Sep 2014 10:03:38 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 10:03:38 -0000 Received: by mail-qc0-f170.google.com with SMTP id r5so12302354qcx.29 for ; Fri, 05 Sep 2014 03:03:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Q+QlqHBM2t0pO7IMVR3GR/ZDotR7K/SbaZRb3RuSDF0=; b=jGhmHNPP/2pxx6o79AAgcZCZcQu0w4HDfp26UsKGQMRGzh4n36HpVL8x28Nk0lWmnN Z0HURXTrclYkdYLaauD4BWAyDpnHIXgocpnjuUzxnEPEPflpQzp8r87TAejEg3EQKOy0 YHjw+sfxCR4nflewwuI7Lc4BelCkkz2cVEJWJqPevvsO7/w0Rs4d0JzCs5L9Hg2QJYk9 hIbgq+KZSNvUxsuMdx3Gf0kdKLCboMbnIqo6VceMJEl4jt0amcbpxQjRNP20js4fjq9v 8tlPqeQGiqFqMe0ERnTLEkfBmUSKFBstDZUDb2/qq+zIhDZaOVgAOXj8GskzCQRX2Zap bMoA== MIME-Version: 1.0 X-Received: by 10.140.94.100 with SMTP id f91mr15716222qge.41.1409911417413; Fri, 05 Sep 2014 03:03:37 -0700 (PDT) Received: by 10.140.101.20 with HTTP; Fri, 5 Sep 2014 03:03:37 -0700 (PDT) Received: by 10.140.101.20 with HTTP; Fri, 5 Sep 2014 03:03:37 -0700 (PDT) In-Reply-To: References: Date: Fri, 5 Sep 2014 11:03:37 +0100 X-Google-Sender-Auth: AYJYfPdTVaIMCOf5U0bFlgWWpcY Message-ID: From: Jon Crowcroft To: Aaron Quamme Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2862301324576088137==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2862301324576088137== Content-Type: multipart/alternative; boundary=001a1139230433280305024e9522 --001a1139230433280305024e9522 Content-Type: text/plain; charset=UTF-8 Rewrite dig in ocaml, maybe? On Sep 5, 2014 1:11 AM, "Aaron Quamme" wrote: > Hello, > > I'm looking for suggestions in the vein of Stephen's project - something > relatively small and non-critical but still useful. I discovered Mirage and > unikernels last week and find topic rather fascinating, so I decided to > make it the focus of my undergraduate research project this semester. I > don't have much experience with OCaml or with functional languages in > general, but I've started on Real World OCaml. > > I'd greatly appreciate any suggestions you provide! > > -- Aaron > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --001a1139230433280305024e9522 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Rewrite dig in ocaml, maybe?

On Sep 5, 2014 1:11 AM, "Aaron Quamme"= <aaron.quamme@gmail.com&g= t; wrote:
Hello,

I'm looking for suggestions in the v= ein of Stephen's project - something relatively small and non-critical = but still useful. I discovered Mirage and unikernels last week and find top= ic rather fascinating, so I decided to make it the focus of my undergraduat= e research project this semester. I don't have much experience with OCa= ml or with functional languages in general, but I've started on Real Wo= rld OCaml.

I'd greatly appreciate any suggestions you provide!=

-- Aaron

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

--001a1139230433280305024e9522-- --===============2862301324576088137== 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 --===============2862301324576088137==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 10:03:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:03: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 1XPqMo-00025R-B7; Fri, 05 Sep 2014 10:03:42 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqMm-000250-LI for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:03:40 +0000 Received: from [193.109.254.147:45580] by server-15.bemta-14.messagelabs.com id 3B/A1-30948-B7A89045; Fri, 05 Sep 2014 10:03:39 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1409911417!13690853!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13645 invoked from network); 5 Sep 2014 10:03:38 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 10:03:38 -0000 Received: by mail-qc0-f170.google.com with SMTP id r5so12302354qcx.29 for ; Fri, 05 Sep 2014 03:03:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Q+QlqHBM2t0pO7IMVR3GR/ZDotR7K/SbaZRb3RuSDF0=; b=jGhmHNPP/2pxx6o79AAgcZCZcQu0w4HDfp26UsKGQMRGzh4n36HpVL8x28Nk0lWmnN Z0HURXTrclYkdYLaauD4BWAyDpnHIXgocpnjuUzxnEPEPflpQzp8r87TAejEg3EQKOy0 YHjw+sfxCR4nflewwuI7Lc4BelCkkz2cVEJWJqPevvsO7/w0Rs4d0JzCs5L9Hg2QJYk9 hIbgq+KZSNvUxsuMdx3Gf0kdKLCboMbnIqo6VceMJEl4jt0amcbpxQjRNP20js4fjq9v 8tlPqeQGiqFqMe0ERnTLEkfBmUSKFBstDZUDb2/qq+zIhDZaOVgAOXj8GskzCQRX2Zap bMoA== MIME-Version: 1.0 X-Received: by 10.140.94.100 with SMTP id f91mr15716222qge.41.1409911417413; Fri, 05 Sep 2014 03:03:37 -0700 (PDT) Received: by 10.140.101.20 with HTTP; Fri, 5 Sep 2014 03:03:37 -0700 (PDT) Received: by 10.140.101.20 with HTTP; Fri, 5 Sep 2014 03:03:37 -0700 (PDT) In-Reply-To: References: Date: Fri, 5 Sep 2014 11:03:37 +0100 X-Google-Sender-Auth: AYJYfPdTVaIMCOf5U0bFlgWWpcY Message-ID: From: Jon Crowcroft To: Aaron Quamme Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2862301324576088137==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2862301324576088137== Content-Type: multipart/alternative; boundary=001a1139230433280305024e9522 --001a1139230433280305024e9522 Content-Type: text/plain; charset=UTF-8 Rewrite dig in ocaml, maybe? On Sep 5, 2014 1:11 AM, "Aaron Quamme" wrote: > Hello, > > I'm looking for suggestions in the vein of Stephen's project - something > relatively small and non-critical but still useful. I discovered Mirage and > unikernels last week and find topic rather fascinating, so I decided to > make it the focus of my undergraduate research project this semester. I > don't have much experience with OCaml or with functional languages in > general, but I've started on Real World OCaml. > > I'd greatly appreciate any suggestions you provide! > > -- Aaron > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --001a1139230433280305024e9522 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Rewrite dig in ocaml, maybe?

On Sep 5, 2014 1:11 AM, "Aaron Quamme"= <aaron.quamme@gmail.com&g= t; wrote:
Hello,

I'm looking for suggestions in the v= ein of Stephen's project - something relatively small and non-critical = but still useful. I discovered Mirage and unikernels last week and find top= ic rather fascinating, so I decided to make it the focus of my undergraduat= e research project this semester. I don't have much experience with OCa= ml or with functional languages in general, but I've started on Real Wo= rld OCaml.

I'd greatly appreciate any suggestions you provide!=

-- Aaron

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

--001a1139230433280305024e9522-- --===============2862301324576088137== 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 --===============2862301324576088137==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 10:10:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:10:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqT7-0002XO-Dv; Fri, 05 Sep 2014 10:10:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqSz-0002Wx-1q for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:10:11 +0000 Received: from [193.109.254.147:33475] by server-8.bemta-14.messagelabs.com id 97/8B-01875-CFB89045; Fri, 05 Sep 2014 10:10:04 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-27.messagelabs.com!1409911803!10337101!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8281 invoked from network); 5 Sep 2014 10:10:03 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-11.tower-27.messagelabs.com with SMTP; 5 Sep 2014 10:10:03 -0000 Received: (qmail 13373 invoked from network); 5 Sep 2014 10:10:02 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 5 Sep 2014 10:10:02 -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 11989-04 for ; Fri, 5 Sep 2014 11:09:55 +0100 (BST) Received: (qmail 13010 invoked by uid 599); 5 Sep 2014 10:09:54 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 05 Sep 2014 11:09:54 +0100 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 1XPqSn-0001Dc-3e; Fri, 05 Sep 2014 11:09:53 +0100 From: Richard Mortier To: Dave Scott , Aaron Quamme Date: Fri, 5 Sep 2014 11:09:50 +0100 Thread-Topic: [MirageOS-devel] Mirage project suggestions for another newcomer Thread-Index: Ac/I8YjEYpvphV1fSeeSDgC68qfamw== Message-ID: References: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> In-Reply-To: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5316470813195267061==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5316470813195267061== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 hi aaron; On 5 Sep 2014, at 10:54, Dave Scott wrote: > On 5 Sep 2014, at 01:10, Aaron Quamme wrote: >=20 >> I'm looking for suggestions in the vein of Stephen's project - = something relatively small and non-critical but still useful. I = discovered Mirage and unikernels last week and find topic rather = fascinating, so I decided to make it the focus of my undergraduate = research project this semester. I don't have much experience with OCaml = or with functional languages in general, but I've started on Real World = OCaml. >>=20 >> I'd greatly appreciate any suggestions you provide! >=20 > How about a DHCP server implementation? We already have a DHCP client: >=20 > https://github.com/mirage/mirage-tcpip/tree/master/dhcp >=20 > A DHCP server would be handy if we want to do fancy network stuff in = future e.g. for some kind of DHCP + NAT + VPN appliance. >=20 > I=92m sure other people have other suggestions too! +1 for dhcp server :) caveat: i don't know what the usual scope or content of ug projects are = at your institution, and i haven't thought in detail about scoping the = following suggestions so they may require far more than is reasonable = for a good ug project anywhere. ...but other things that i think would be useful at some point would be = an ipv6 stack, a vpn client, nat support, upnp. basically, name a = network protocol that's not already supported, and an implementation = will probably be useful at some point to someone :) a thorough performance eval (range of conditions, range of platforms) of = the mirage stack (network and/or block) would also be useful and might = make a good ug project. continuing some of the work that mindy preston did during her opw = internship fuzz-testing the network stack would probably also be useful. --=20 Cheers, R. --Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUCYvuAAoJEOLF27JWwSg3FuQP+gMTaN3/GLCprnWI4r1JCbvB 1X61iHHPqy22g3YiiMw7AeRPItlItYXwH6Tw0woH2AojS5itE6lo7kPVmhSjXtYF Tr/kIu/iRBvRCcNt0bVtz0WtGL2YPM9F+i68C8RkO3wJmbwUAw9ZfBsquR4aEOLA 8MHMPR3f+CGkci0ODkwA5lS8UHOMvhqdyfssPsG0mqYD6EWhnxYHe8H8VWdsFUCz LDZZ4/97niyBgvQfCIJw52l7YWsPjRYfNsMgUlcSMjYP7jYscwzUKg0uQCBdF770 BzW2X65Gpj8/0BSHpqyRmq0klKlZnRux1uCzdUX5tNNJqutQ5IkBteFBhHEYutCP uuWpFliprlkpteZ7s/yS7bZ+xJIb7Uy5WqfOp5y7NBOZPTWH08mGjzcBvORD9JfY 1jEZBuyy3SAq5FJLxqku4sQR1W3bzEWW6C4RbRCqrI/FwbbzEaHWxT8o8H3ln0kk 7PQ7+M+hfUIfracOi9KI9xmCyMRIm2kLaVAmStxdIXaTZdshfeMSs0KJ0v06m9Rc 8860rVP8eUbMqeshJVzqeu8hPk9HYCXDaLOjHnwXMqURh7n5LkFeeKp2jZdiGpKU mUZUrYLYDZKPMLJCSmrfg+zgjw3+9C+I34dbMfZwzb6Ye+LgWNy4HGH6hLi/6DdI oxU+2fbtDmP1d7xXZHRa =EJ6o -----END PGP SIGNATURE----- --Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08-- --===============5316470813195267061== 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 --===============5316470813195267061==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 10:10:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:10:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqT7-0002XO-Dv; Fri, 05 Sep 2014 10:10:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqSz-0002Wx-1q for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:10:11 +0000 Received: from [193.109.254.147:33475] by server-8.bemta-14.messagelabs.com id 97/8B-01875-CFB89045; Fri, 05 Sep 2014 10:10:04 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-27.messagelabs.com!1409911803!10337101!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8281 invoked from network); 5 Sep 2014 10:10:03 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-11.tower-27.messagelabs.com with SMTP; 5 Sep 2014 10:10:03 -0000 Received: (qmail 13373 invoked from network); 5 Sep 2014 10:10:02 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 5 Sep 2014 10:10:02 -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 11989-04 for ; Fri, 5 Sep 2014 11:09:55 +0100 (BST) Received: (qmail 13010 invoked by uid 599); 5 Sep 2014 10:09:54 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 05 Sep 2014 11:09:54 +0100 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 1XPqSn-0001Dc-3e; Fri, 05 Sep 2014 11:09:53 +0100 From: Richard Mortier To: Dave Scott , Aaron Quamme Date: Fri, 5 Sep 2014 11:09:50 +0100 Thread-Topic: [MirageOS-devel] Mirage project suggestions for another newcomer Thread-Index: Ac/I8YjEYpvphV1fSeeSDgC68qfamw== Message-ID: References: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> In-Reply-To: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5316470813195267061==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5316470813195267061== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 hi aaron; On 5 Sep 2014, at 10:54, Dave Scott wrote: > On 5 Sep 2014, at 01:10, Aaron Quamme wrote: >=20 >> I'm looking for suggestions in the vein of Stephen's project - = something relatively small and non-critical but still useful. I = discovered Mirage and unikernels last week and find topic rather = fascinating, so I decided to make it the focus of my undergraduate = research project this semester. I don't have much experience with OCaml = or with functional languages in general, but I've started on Real World = OCaml. >>=20 >> I'd greatly appreciate any suggestions you provide! >=20 > How about a DHCP server implementation? We already have a DHCP client: >=20 > https://github.com/mirage/mirage-tcpip/tree/master/dhcp >=20 > A DHCP server would be handy if we want to do fancy network stuff in = future e.g. for some kind of DHCP + NAT + VPN appliance. >=20 > I=92m sure other people have other suggestions too! +1 for dhcp server :) caveat: i don't know what the usual scope or content of ug projects are = at your institution, and i haven't thought in detail about scoping the = following suggestions so they may require far more than is reasonable = for a good ug project anywhere. ...but other things that i think would be useful at some point would be = an ipv6 stack, a vpn client, nat support, upnp. basically, name a = network protocol that's not already supported, and an implementation = will probably be useful at some point to someone :) a thorough performance eval (range of conditions, range of platforms) of = the mirage stack (network and/or block) would also be useful and might = make a good ug project. continuing some of the work that mindy preston did during her opw = internship fuzz-testing the network stack would probably also be useful. --=20 Cheers, R. --Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUCYvuAAoJEOLF27JWwSg3FuQP+gMTaN3/GLCprnWI4r1JCbvB 1X61iHHPqy22g3YiiMw7AeRPItlItYXwH6Tw0woH2AojS5itE6lo7kPVmhSjXtYF Tr/kIu/iRBvRCcNt0bVtz0WtGL2YPM9F+i68C8RkO3wJmbwUAw9ZfBsquR4aEOLA 8MHMPR3f+CGkci0ODkwA5lS8UHOMvhqdyfssPsG0mqYD6EWhnxYHe8H8VWdsFUCz LDZZ4/97niyBgvQfCIJw52l7YWsPjRYfNsMgUlcSMjYP7jYscwzUKg0uQCBdF770 BzW2X65Gpj8/0BSHpqyRmq0klKlZnRux1uCzdUX5tNNJqutQ5IkBteFBhHEYutCP uuWpFliprlkpteZ7s/yS7bZ+xJIb7Uy5WqfOp5y7NBOZPTWH08mGjzcBvORD9JfY 1jEZBuyy3SAq5FJLxqku4sQR1W3bzEWW6C4RbRCqrI/FwbbzEaHWxT8o8H3ln0kk 7PQ7+M+hfUIfracOi9KI9xmCyMRIm2kLaVAmStxdIXaTZdshfeMSs0KJ0v06m9Rc 8860rVP8eUbMqeshJVzqeu8hPk9HYCXDaLOjHnwXMqURh7n5LkFeeKp2jZdiGpKU mUZUrYLYDZKPMLJCSmrfg+zgjw3+9C+I34dbMfZwzb6Ye+LgWNy4HGH6hLi/6DdI oxU+2fbtDmP1d7xXZHRa =EJ6o -----END PGP SIGNATURE----- --Apple-Mail=_F24096E7-B392-45FA-96C7-53F39E52DA08-- --===============5316470813195267061== 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 --===============5316470813195267061==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 10:32:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:32: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 1XPqoj-000394-KQ; Fri, 05 Sep 2014 10:32:33 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqoh-00038v-Q6 for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:32:31 +0000 Received: from [85.158.143.35:55702] by server-3.bemta-4.messagelabs.com id BD/DC-06192-F3199045; Fri, 05 Sep 2014 10:32:31 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1409913150!11885383!1 X-Originating-IP: [157.55.1.156] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25610 invoked from network); 5 Sep 2014 10:32:30 -0000 Received: from dub004-omc2s17.hotmail.com (HELO DUB004-OMC2S17.hotmail.com) (157.55.1.156) by server-8.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2014 10:32:30 -0000 Received: from DUB128-W3 ([157.55.1.137]) by DUB004-OMC2S17.hotmail.com with Microsoft SMTPSVC(7.5.7601.22724); Fri, 5 Sep 2014 03:32:30 -0700 X-TMN: [wYUP/o6WiqHilIhtt/Z5gsCoxaS64mft] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: Aaron Quamme Date: Fri, 5 Sep 2014 10:32:30 +0000 Importance: Normal In-Reply-To: References: , <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com>, MIME-Version: 1.0 X-OriginalArrivalTime: 05 Sep 2014 10:32:30.0462 (UTC) FILETIME=[B237F1E0:01CFC8F4] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8460994048829731259==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8460994048829731259== Content-Type: multipart/alternative; boundary="_824363d3-1972-4016-a70e-e0e55114283a_" --_824363d3-1972-4016-a70e-e0e55114283a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Aaron=2C Just seconding Richard's suggestion of the ipv6 stack - this would be inval= uable=2C especially in the context of sensors=2C hardware etc. Cheers=2C Nick = --_824363d3-1972-4016-a70e-e0e55114283a_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Aaron=2C

Just secondin= g Richard's suggestion of the ipv6 stack - this would be invaluable=2C espe= cially in the context of sensors=2C hardware etc.

Cheers=2C
Nick<= br>

= --_824363d3-1972-4016-a70e-e0e55114283a_-- --===============8460994048829731259== 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 --===============8460994048829731259==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 10:32:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:32: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 1XPqoj-000394-KQ; Fri, 05 Sep 2014 10:32:33 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqoh-00038v-Q6 for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:32:31 +0000 Received: from [85.158.143.35:55702] by server-3.bemta-4.messagelabs.com id BD/DC-06192-F3199045; Fri, 05 Sep 2014 10:32:31 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1409913150!11885383!1 X-Originating-IP: [157.55.1.156] X-SpamReason: No, hits=0.2 required=7.0 tests=FORGED_HOTMAIL_RCVD, HTML_50_60, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12, ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25610 invoked from network); 5 Sep 2014 10:32:30 -0000 Received: from dub004-omc2s17.hotmail.com (HELO DUB004-OMC2S17.hotmail.com) (157.55.1.156) by server-8.tower-21.messagelabs.com with AES256-SHA encrypted SMTP; 5 Sep 2014 10:32:30 -0000 Received: from DUB128-W3 ([157.55.1.137]) by DUB004-OMC2S17.hotmail.com with Microsoft SMTPSVC(7.5.7601.22724); Fri, 5 Sep 2014 03:32:30 -0700 X-TMN: [wYUP/o6WiqHilIhtt/Z5gsCoxaS64mft] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: Aaron Quamme Date: Fri, 5 Sep 2014 10:32:30 +0000 Importance: Normal In-Reply-To: References: , <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com>, MIME-Version: 1.0 X-OriginalArrivalTime: 05 Sep 2014 10:32:30.0462 (UTC) FILETIME=[B237F1E0:01CFC8F4] Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8460994048829731259==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8460994048829731259== Content-Type: multipart/alternative; boundary="_824363d3-1972-4016-a70e-e0e55114283a_" --_824363d3-1972-4016-a70e-e0e55114283a_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Aaron=2C Just seconding Richard's suggestion of the ipv6 stack - this would be inval= uable=2C especially in the context of sensors=2C hardware etc. Cheers=2C Nick = --_824363d3-1972-4016-a70e-e0e55114283a_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Aaron=2C

Just secondin= g Richard's suggestion of the ipv6 stack - this would be invaluable=2C espe= cially in the context of sensors=2C hardware etc.

Cheers=2C
Nick<= br>

= --_824363d3-1972-4016-a70e-e0e55114283a_-- --===============8460994048829731259== 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 --===============8460994048829731259==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 05 10:41:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:41: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 1XPqxP-0003xm-LZ; Fri, 05 Sep 2014 10:41:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqxN-0003xb-Pn for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:41:29 +0000 Received: from [85.158.137.68:21412] by server-12.bemta-3.messagelabs.com id F5/3A-01574-95399045; Fri, 05 Sep 2014 10:41:29 +0000 X-Env-Sender: jac22@cl.cam.ac.uk X-Msg-Ref: server-3.tower-31.messagelabs.com!1409913688!12029810!1 X-Originating-IP: [128.232.25.20] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11901 invoked from network); 5 Sep 2014 10:41:28 -0000 Received: from mta0.cl.cam.ac.uk (HELO mta0.cl.cam.ac.uk) (128.232.25.20) by server-3.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2014 10:41:28 -0000 Received: from ssh-remote-0.cl.cam.ac.uk ([128.232.0.69] helo=cl.cam.ac.uk) by mta0.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1XPqxL-00025R-A8; Fri, 05 Sep 2014 11:41:27 +0100 To: Dave Scott In-reply-to: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> References: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> Comments: In-reply-to Dave Scott message dated "Fri, 05 Sep 2014 09:54:39 -0000." MIME-Version: 1.0 Content-ID: <24857.1409913687.1@cl.cam.ac.uk> Date: Fri, 05 Sep 2014 11:41:27 +0100 From: Jon Crowcroft Message-Id: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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 oh es- a mini dhcp/bootserver for other appliances would def. be a nice project In missive <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com>, Dave Scott typed: >>Hi Aaron. >> >>On 5 Sep 2014, at 01:10, Aaron Quamme wrote: >> >>> Hello, >>> = >> >>> I'm looking for suggestions in the vein of Stephen's project - something = >>relatively small and non-critical but still useful. I discovered Mirage and= >> unikernels last week and find topic rather fascinating, so I decided to ma= >>ke it the focus of my undergraduate research project this semester. I don't= >> have much experience with OCaml or with functional languages in general, b= >>ut I've started on Real World OCaml. >>> = >> >>> I'd greatly appreciate any suggestions you provide! >> >>How about a DHCP server implementation? We already have a DHCP client: >> >>https://github.com/mirage/mirage-tcpip/tree/master/dhcp >> >>A DHCP server would be handy if we want to do fancy network stuff in future= >> e.g. for some kind of DHCP + NAT + VPN appliance. >> >>I=92m sure other people have other suggestions too! >> >>Cheers, >>Dave >>_______________________________________________ >>MirageOS-devel mailing list >>MirageOS-devel@lists.xenproject.org >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel cheers jon _______________________________________________ MirageOS-devel 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 Sep 05 10:41:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 10:41: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 1XPqxP-0003xm-LZ; Fri, 05 Sep 2014 10:41:31 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPqxN-0003xb-Pn for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 10:41:29 +0000 Received: from [85.158.137.68:21412] by server-12.bemta-3.messagelabs.com id F5/3A-01574-95399045; Fri, 05 Sep 2014 10:41:29 +0000 X-Env-Sender: jac22@cl.cam.ac.uk X-Msg-Ref: server-3.tower-31.messagelabs.com!1409913688!12029810!1 X-Originating-IP: [128.232.25.20] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11901 invoked from network); 5 Sep 2014 10:41:28 -0000 Received: from mta0.cl.cam.ac.uk (HELO mta0.cl.cam.ac.uk) (128.232.25.20) by server-3.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Sep 2014 10:41:28 -0000 Received: from ssh-remote-0.cl.cam.ac.uk ([128.232.0.69] helo=cl.cam.ac.uk) by mta0.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1XPqxL-00025R-A8; Fri, 05 Sep 2014 11:41:27 +0100 To: Dave Scott In-reply-to: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> References: <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com> Comments: In-reply-to Dave Scott message dated "Fri, 05 Sep 2014 09:54:39 -0000." MIME-Version: 1.0 Content-ID: <24857.1409913687.1@cl.cam.ac.uk> Date: Fri, 05 Sep 2014 11:41:27 +0100 From: Jon Crowcroft Message-Id: Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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 oh es- a mini dhcp/bootserver for other appliances would def. be a nice project In missive <26190889-A054-4BF5-B705-716850A3F6CA@citrix.com>, Dave Scott typed: >>Hi Aaron. >> >>On 5 Sep 2014, at 01:10, Aaron Quamme wrote: >> >>> Hello, >>> = >> >>> I'm looking for suggestions in the vein of Stephen's project - something = >>relatively small and non-critical but still useful. I discovered Mirage and= >> unikernels last week and find topic rather fascinating, so I decided to ma= >>ke it the focus of my undergraduate research project this semester. I don't= >> have much experience with OCaml or with functional languages in general, b= >>ut I've started on Real World OCaml. >>> = >> >>> I'd greatly appreciate any suggestions you provide! >> >>How about a DHCP server implementation? We already have a DHCP client: >> >>https://github.com/mirage/mirage-tcpip/tree/master/dhcp >> >>A DHCP server would be handy if we want to do fancy network stuff in future= >> e.g. for some kind of DHCP + NAT + VPN appliance. >> >>I=92m sure other people have other suggestions too! >> >>Cheers, >>Dave >>_______________________________________________ >>MirageOS-devel mailing list >>MirageOS-devel@lists.xenproject.org >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel cheers jon _______________________________________________ MirageOS-devel 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 Sep 05 13:21:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 13:21: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 1XPtRk-0007wz-G9; Fri, 05 Sep 2014 13:21:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPtRi-0007wu-J0 for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 13:20:58 +0000 Received: from [193.109.254.147:38814] by server-15.bemta-14.messagelabs.com id 40/F8-30948-9B8B9045; Fri, 05 Sep 2014 13:20:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1409923257!13690117!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8689 invoked from network); 5 Sep 2014 13:20:57 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-27.messagelabs.com with SMTP; 5 Sep 2014 13:20:57 -0000 Received: (qmail 13663 invoked by uid 634); 5 Sep 2014 13:20:56 -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 Unknown (HELO [172.25.42.133]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 05 Sep 2014 14:20:55 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 5 Sep 2014 15:20:54 +0200 Message-Id: References: To: Jon Crowcroft X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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 Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml $ opam install dns $ (build mldig from mirage/ocaml-dns, it's not installed by default) $ mldig txt recoil.org ;; <<>> MLDiG 1.0 <<>> ;; global options: ;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;recoil.org. IN TXT ;; ANSWER SECTION: recoil.org. 10800 IN TXT "Llamaz United" +1 to the DHCP server though -- that would be most useful! -anil On 5 Sep 2014, at 12:03, Jon Crowcroft wrote: > Rewrite dig in ocaml, maybe? > > On Sep 5, 2014 1:11 AM, "Aaron Quamme" wrote: > Hello, > > I'm looking for suggestions in the vein of Stephen's project - something relatively small and non-critical but still useful. I discovered Mirage and unikernels last week and find topic rather fascinating, so I decided to make it the focus of my undergraduate research project this semester. I don't have much experience with OCaml or with functional languages in general, but I've started on Real World OCaml. > > I'd greatly appreciate any suggestions you provide! > > -- Aaron > > _______________________________________________ > 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 Fri Sep 05 13:21:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 13:21: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 1XPtRk-0007wz-G9; Fri, 05 Sep 2014 13:21:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XPtRi-0007wu-J0 for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 13:20:58 +0000 Received: from [193.109.254.147:38814] by server-15.bemta-14.messagelabs.com id 40/F8-30948-9B8B9045; Fri, 05 Sep 2014 13:20:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1409923257!13690117!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8689 invoked from network); 5 Sep 2014 13:20:57 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-27.messagelabs.com with SMTP; 5 Sep 2014 13:20:57 -0000 Received: (qmail 13663 invoked by uid 634); 5 Sep 2014 13:20:56 -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 Unknown (HELO [172.25.42.133]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 05 Sep 2014 14:20:55 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 5 Sep 2014 15:20:54 +0200 Message-Id: References: To: Jon Crowcroft X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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 Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml $ opam install dns $ (build mldig from mirage/ocaml-dns, it's not installed by default) $ mldig txt recoil.org ;; <<>> MLDiG 1.0 <<>> ;; global options: ;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;recoil.org. IN TXT ;; ANSWER SECTION: recoil.org. 10800 IN TXT "Llamaz United" +1 to the DHCP server though -- that would be most useful! -anil On 5 Sep 2014, at 12:03, Jon Crowcroft wrote: > Rewrite dig in ocaml, maybe? > > On Sep 5, 2014 1:11 AM, "Aaron Quamme" wrote: > Hello, > > I'm looking for suggestions in the vein of Stephen's project - something relatively small and non-critical but still useful. I discovered Mirage and unikernels last week and find topic rather fascinating, so I decided to make it the focus of my undergraduate research project this semester. I don't have much experience with OCaml or with functional languages in general, but I've started on Real World OCaml. > > I'd greatly appreciate any suggestions you provide! > > -- Aaron > > _______________________________________________ > 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 Fri Sep 05 20:27:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 20:27: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 1XQ05w-00019k-JP; Fri, 05 Sep 2014 20:26:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQ05v-00019f-0b for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 20:26:55 +0000 Received: from [85.158.139.211:31244] by server-14.bemta-5.messagelabs.com id CD/46-12422-E8C1A045; Fri, 05 Sep 2014 20:26:54 +0000 X-Env-Sender: kiwamu@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1409948812!12780312!1 X-Originating-IP: [209.85.220.174] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15580 invoked from network); 5 Sep 2014 20:26:53 -0000 Received: from mail-vc0-f174.google.com (HELO mail-vc0-f174.google.com) (209.85.220.174) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 20:26:53 -0000 Received: by mail-vc0-f174.google.com with SMTP id hy4so12744663vcb.5 for ; Fri, 05 Sep 2014 13:26:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=3//Yyiypb93kRnHd76TyJmmw/Ebw1rxQJ04WrxSm0tA=; b=wYGIixeeSiSW+CAbnsBjqTBgILxStsk5PHUeVL+5NkNLiGZQG2MVhDN9KfgVxDk6Vz /49AzG2lHtmN+5v52Odp/r05G99LpPoAlb+yuCWO27lQwHf5o9VkI65YGl9/JF9L/7fl PmHLUP1fMDHzQqnVBJPz2VpLX4qiKrzipFR7eLj1TTIM46EB2pn5cv9ERiaAoD/Bl0r1 8FIDVcv4r/nwleoTjWgNs7M6biUQ+uHeR16yaqLaiwWD9RlCyB+oHi0ImgRBoMS/V2tm 6IsSyrr4egcs2NPfkhzAspWWppR0xHd3uBlib7UWNn9Ms/6ZF7LhnE2DjjITVbpje/jI COpQ== X-Received: by 10.220.184.70 with SMTP id cj6mr12224738vcb.5.1409948812002; Fri, 05 Sep 2014 13:26:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.223.206 with HTTP; Fri, 5 Sep 2014 13:26:31 -0700 (PDT) From: Kiwamu Okabe Date: Fri, 5 Sep 2014 22:26:31 +0200 X-Google-Sender-Auth: WiZjaK1Xm-BSrf8NqWxeNfcispQ Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] MirageOS can shape reentrancy in Unix-like kernel? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, I'm interested in your Mirage OS running on Bare Metal hardware. My question is that it can shape reentrancy in Unix-like kernel? I found http://metasepi.org/ that aim to be Unix-like OS with strong type. Today we choose ATS language. http://www.ats-lang.org/ However, ATS is hard for normal programmer. If Mirage OS can write Unix kernel in future, our project is so happy. Thank's, -- Kiwamu Okabe at METASEPI DESIGN _______________________________________________ MirageOS-devel 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 Sep 05 20:27:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 05 Sep 2014 20:27: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 1XQ05w-00019k-JP; Fri, 05 Sep 2014 20:26:56 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQ05v-00019f-0b for mirageos-devel@lists.xenproject.org; Fri, 05 Sep 2014 20:26:55 +0000 Received: from [85.158.139.211:31244] by server-14.bemta-5.messagelabs.com id CD/46-12422-E8C1A045; Fri, 05 Sep 2014 20:26:54 +0000 X-Env-Sender: kiwamu@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1409948812!12780312!1 X-Originating-IP: [209.85.220.174] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15580 invoked from network); 5 Sep 2014 20:26:53 -0000 Received: from mail-vc0-f174.google.com (HELO mail-vc0-f174.google.com) (209.85.220.174) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Sep 2014 20:26:53 -0000 Received: by mail-vc0-f174.google.com with SMTP id hy4so12744663vcb.5 for ; Fri, 05 Sep 2014 13:26:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=3//Yyiypb93kRnHd76TyJmmw/Ebw1rxQJ04WrxSm0tA=; b=wYGIixeeSiSW+CAbnsBjqTBgILxStsk5PHUeVL+5NkNLiGZQG2MVhDN9KfgVxDk6Vz /49AzG2lHtmN+5v52Odp/r05G99LpPoAlb+yuCWO27lQwHf5o9VkI65YGl9/JF9L/7fl PmHLUP1fMDHzQqnVBJPz2VpLX4qiKrzipFR7eLj1TTIM46EB2pn5cv9ERiaAoD/Bl0r1 8FIDVcv4r/nwleoTjWgNs7M6biUQ+uHeR16yaqLaiwWD9RlCyB+oHi0ImgRBoMS/V2tm 6IsSyrr4egcs2NPfkhzAspWWppR0xHd3uBlib7UWNn9Ms/6ZF7LhnE2DjjITVbpje/jI COpQ== X-Received: by 10.220.184.70 with SMTP id cj6mr12224738vcb.5.1409948812002; Fri, 05 Sep 2014 13:26:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.223.206 with HTTP; Fri, 5 Sep 2014 13:26:31 -0700 (PDT) From: Kiwamu Okabe Date: Fri, 5 Sep 2014 22:26:31 +0200 X-Google-Sender-Auth: WiZjaK1Xm-BSrf8NqWxeNfcispQ Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] MirageOS can shape reentrancy in Unix-like kernel? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, I'm interested in your Mirage OS running on Bare Metal hardware. My question is that it can shape reentrancy in Unix-like kernel? I found http://metasepi.org/ that aim to be Unix-like OS with strong type. Today we choose ATS language. http://www.ats-lang.org/ However, ATS is hard for normal programmer. If Mirage OS can write Unix kernel in future, our project is so happy. Thank's, -- Kiwamu Okabe at METASEPI DESIGN _______________________________________________ MirageOS-devel 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 Sep 06 00:40:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 00:40: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 1XQ435-0008Pn-Ql; Sat, 06 Sep 2014 00:40:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQ432-0008Pf-Dt for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 00:40:13 +0000 Received: from [85.158.143.35:33272] by server-2.bemta-4.messagelabs.com id 60/7C-04525-BE75A045; Sat, 06 Sep 2014 00:40:11 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1409964011!11977290!1 X-Originating-IP: [74.125.82.44] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6484 invoked from network); 6 Sep 2014 00:40:11 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2014 00:40:11 -0000 Received: by mail-wg0-f44.google.com with SMTP id m15so12409624wgh.15 for ; Fri, 05 Sep 2014 17:40:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VO8docYHIh/Ms9oq2f1E33AYpYZsYlIKj9xq7jCebuc=; b=deThW2WmvL74/geTEuvpVp0SS49RqeQIhL7MwnMlhb921sZRpbvbcjFjnomdOt4loP VGkHJf/qY/n3HjI20o30x/nPgO0t0JD0l/Mr2OHih3ZpnL9nhyb37qhB1yHLVIy94J0C HuL+UB/WKXXHasVOfQB92x41rVmo+5rVWACjIA7II0ddIHZp93bwJw3g1om8l9ZJ5R8P gmHkrz+c2ADhGItasQ8Yd1zGT4EINPHZ5ZjCSBAnX9GbJJIku7qCaqPEFo+jMAadRe2D FSGrVjm3iHSEkLkd4xHxLf/wfl6aFpXCf62D1SmSE9AbhkCB/HjqunpEAq+pQbP+ABbu LAqw== MIME-Version: 1.0 X-Received: by 10.194.122.6 with SMTP id lo6mr18209721wjb.17.1409964010574; Fri, 05 Sep 2014 17:40:10 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Fri, 5 Sep 2014 17:40:10 -0700 (PDT) Date: Fri, 5 Sep 2014 20:40:10 -0400 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Thinking out loud about secure unikernal communication over the internet X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7154438817056297543==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7154438817056297543== Content-Type: multipart/alternative; boundary=089e0117643dff17c005025ad379 --089e0117643dff17c005025ad379 Content-Type: text/plain; charset=UTF-8 Hello everyone, With all the buzz about hacking lately, I have been thinking a lot about security. Since our mirage unikernals will be living all over the internet, they will be needing a secure way to talk to each and to move data around. There are of course a lot of different protocols such as HTTPS or the alphabet soup of VPN protocols. It would however be nice to keep to our unikernal roots and have a quick and secure protocol that could be spun up and used quickly and efficiently then destroyed. I would love to hear ideas from the community. I have recently discovered a new IM protocol being developed by Silent Circle called SCIMP. One of it's benefits is that the secret key changes with each message so if someone is recording and saving your traffic, they can never get access to old messages with the current key. https://silentcircle.com/scimp-protocol It would be good for Mirage to be secure out of the box. --Stephen --089e0117643dff17c005025ad379 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone,

With all the buzz about= hacking lately, I have been thinking a lot about security. =C2=A0Since our= mirage unikernals will be living all over the internet, they will be needi= ng a secure way to talk to each and to move data around.

There are of course a lot of different protocols such as HTTPS or th= e alphabet soup of VPN protocols.

It would however= be nice to keep to our unikernal roots and have a quick and secure protoco= l that could be spun up and used quickly and efficiently then destroyed.

I would love to hear ideas from the community.
=

I have recently discovered a new IM protocol being deve= loped by Silent Circle called SCIMP. =C2=A0One of it's benefits is that= the secret key changes with each message so if someone is recording and sa= ving your traffic, they can never get access to old messages with the curre= nt key.


It would be good for Mirage to be secure out of the box.
=
--Stephen
--089e0117643dff17c005025ad379-- --===============7154438817056297543== 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 --===============7154438817056297543==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 00:40:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 00:40: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 1XQ435-0008Pn-Ql; Sat, 06 Sep 2014 00:40:15 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQ432-0008Pf-Dt for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 00:40:13 +0000 Received: from [85.158.143.35:33272] by server-2.bemta-4.messagelabs.com id 60/7C-04525-BE75A045; Sat, 06 Sep 2014 00:40:11 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1409964011!11977290!1 X-Originating-IP: [74.125.82.44] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6484 invoked from network); 6 Sep 2014 00:40:11 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2014 00:40:11 -0000 Received: by mail-wg0-f44.google.com with SMTP id m15so12409624wgh.15 for ; Fri, 05 Sep 2014 17:40:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=VO8docYHIh/Ms9oq2f1E33AYpYZsYlIKj9xq7jCebuc=; b=deThW2WmvL74/geTEuvpVp0SS49RqeQIhL7MwnMlhb921sZRpbvbcjFjnomdOt4loP VGkHJf/qY/n3HjI20o30x/nPgO0t0JD0l/Mr2OHih3ZpnL9nhyb37qhB1yHLVIy94J0C HuL+UB/WKXXHasVOfQB92x41rVmo+5rVWACjIA7II0ddIHZp93bwJw3g1om8l9ZJ5R8P gmHkrz+c2ADhGItasQ8Yd1zGT4EINPHZ5ZjCSBAnX9GbJJIku7qCaqPEFo+jMAadRe2D FSGrVjm3iHSEkLkd4xHxLf/wfl6aFpXCf62D1SmSE9AbhkCB/HjqunpEAq+pQbP+ABbu LAqw== MIME-Version: 1.0 X-Received: by 10.194.122.6 with SMTP id lo6mr18209721wjb.17.1409964010574; Fri, 05 Sep 2014 17:40:10 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Fri, 5 Sep 2014 17:40:10 -0700 (PDT) Date: Fri, 5 Sep 2014 20:40:10 -0400 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Thinking out loud about secure unikernal communication over the internet X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7154438817056297543==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7154438817056297543== Content-Type: multipart/alternative; boundary=089e0117643dff17c005025ad379 --089e0117643dff17c005025ad379 Content-Type: text/plain; charset=UTF-8 Hello everyone, With all the buzz about hacking lately, I have been thinking a lot about security. Since our mirage unikernals will be living all over the internet, they will be needing a secure way to talk to each and to move data around. There are of course a lot of different protocols such as HTTPS or the alphabet soup of VPN protocols. It would however be nice to keep to our unikernal roots and have a quick and secure protocol that could be spun up and used quickly and efficiently then destroyed. I would love to hear ideas from the community. I have recently discovered a new IM protocol being developed by Silent Circle called SCIMP. One of it's benefits is that the secret key changes with each message so if someone is recording and saving your traffic, they can never get access to old messages with the current key. https://silentcircle.com/scimp-protocol It would be good for Mirage to be secure out of the box. --Stephen --089e0117643dff17c005025ad379 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone,

With all the buzz about= hacking lately, I have been thinking a lot about security. =C2=A0Since our= mirage unikernals will be living all over the internet, they will be needi= ng a secure way to talk to each and to move data around.

There are of course a lot of different protocols such as HTTPS or th= e alphabet soup of VPN protocols.

It would however= be nice to keep to our unikernal roots and have a quick and secure protoco= l that could be spun up and used quickly and efficiently then destroyed.

I would love to hear ideas from the community.
=

I have recently discovered a new IM protocol being deve= loped by Silent Circle called SCIMP. =C2=A0One of it's benefits is that= the secret key changes with each message so if someone is recording and sa= ving your traffic, they can never get access to old messages with the curre= nt key.


It would be good for Mirage to be secure out of the box.
=
--Stephen
--089e0117643dff17c005025ad379-- --===============7154438817056297543== 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 --===============7154438817056297543==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 06:17:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 06:17: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 1XQ9J5-0003Se-OH; Sat, 06 Sep 2014 06:17:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQ9J4-0003SZ-7T for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 06:17:06 +0000 Received: from [85.158.139.211:10589] by server-15.bemta-5.messagelabs.com id 68/A6-12002-1E6AA045; Sat, 06 Sep 2014 06:17:05 +0000 X-Env-Sender: aaron.quamme@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1409984222!7507771!1 X-Originating-IP: [209.85.223.173] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3412 invoked from network); 6 Sep 2014 06:17:04 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2014 06:17:04 -0000 Received: by mail-ie0-f173.google.com with SMTP id lx4so15320141iec.18 for ; Fri, 05 Sep 2014 23:17:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7CoAEo3ljppxzXRUTZDUAZsSUBckIUfbRK9ffhJX7Oc=; b=n84e2wYwMUDc84JB+vPIseyzEe8WSfvJXEZep0wfx/FybWlAVwKBn6tHRWN78OTrEV OTW3T7uDhS6KIHVzHPu7UDwtPxIdiQX+HFJhXadGYfs6Iox4Fkwr1U8xkS1XszD1fRL3 ACrCHXqInkM4Ep8S4xddz/n3Wbd3tuf9hSuON8tVWZj8++YzEPeB1TxQ1q/5+9RFuxA1 MFiJdAwcLdWsjI0HdGW9gpS19xKWn4uQtu3rDS6ROf9h4DFo+5liEUHNMs2JO9tLWrD1 Kdtrw3VjtvlODy9WOq7HaG+oH2SWztCbOmJewbf5GSdHh0lmCARhBB0cOAuV7ZxudXk7 sO9A== MIME-Version: 1.0 X-Received: by 10.42.58.65 with SMTP id g1mr19585013ich.38.1409984222576; Fri, 05 Sep 2014 23:17:02 -0700 (PDT) Received: by 10.64.117.229 with HTTP; Fri, 5 Sep 2014 23:17:02 -0700 (PDT) Received: by 10.64.117.229 with HTTP; Fri, 5 Sep 2014 23:17:02 -0700 (PDT) In-Reply-To: References: Date: Sat, 6 Sep 2014 01:17:02 -0500 Message-ID: From: Aaron Quamme To: Anil Madhavapeddy Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0834964418479326812==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0834964418479326812== Content-Type: multipart/alternative; boundary=485b397dd1f3b9c79f05025f88b5 --485b397dd1f3b9c79f05025f88b5 Content-Type: text/plain; charset=UTF-8 Thanks for the suggestions -- a DHCP server sounds like a good challenge! I'm thinking I'll start by reviewing the protocol and reading the source of some preexisting implementation - and by continuing with Real World OCaml, of course. I'm sure I'll have plenty of questions in the coming months. Thanks again! --Aaron Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml $ opam install dns $ (build mldig from mirage/ocaml-dns, it's not installed by default) $ mldig txt recoil.org ;; <<>> MLDiG 1.0 <<>> ;; global options: ;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;recoil.org. IN TXT ;; ANSWER SECTION: recoil.org. 10800 IN TXT "Llamaz United" +1 to the DHCP server though -- that would be most useful! -anil On 5 Sep 2014, at 12:03, Jon Crowcroft wrote: > Rewrite dig in ocaml, maybe? > > On Sep 5, 2014 1:11 AM, "Aaron Quamme" wrote: > Hello, > > I'm looking for suggestions in the vein of Stephen's project - something relatively small and non-critical but still useful. I discovered Mirage and unikernels last week and find topic rather fascinating, so I decided to make it the focus of my undergraduate research project this semester. I don't have much experience with OCaml or with functional languages in general, but I've started on Real World OCaml. > > I'd greatly appreciate any suggestions you provide! > > -- Aaron > > _______________________________________________ > 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 --485b397dd1f3b9c79f05025f88b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks for the suggestions -- a DHCP server sounds like a go= od challenge!=C2=A0

I'm thinking I'll start by reviewing the protocol an= d reading the source of some preexisting implementation - and by continuing= with Real World OCaml, of course. I'm sure I'll have plenty of que= stions in the coming months. Thanks again!

--Aaron

Sorry :-) htt= ps://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml

$ opam install dns
$ (build mldig from mirage/ocaml-dns, it's not installed by default) $ mldig txt recoil.org<= br> ;; <<>> MLDiG 1.0 <<>>
;; global options:
;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;recoil.org.=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IN=C2=A0= =C2=A0 =C2=A0 =C2=A0TXT

;; ANSWER SECTION:
recoil.org.=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 10800=C2=A0 =C2=A0 IN=C2=A0 =C2=A0 = =C2=A0 =C2=A0TXT=C2=A0 =C2=A0 =C2=A0 "Llamaz United"

+1 to the DHCP server though -- that would be most useful!

-anil

On 5 Sep 2014, at 12:03, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> wrote:

> Rewrite dig in ocaml, maybe?
>
> On Sep 5, 2014 1:11 AM, "Aaron Quamme" <aaron.quamme@gmail.com> wrote:
> Hello,
>
> I'm looking for suggestions in the vein of Stephen's project -= something relatively small and non-critical but still useful. I discovered= Mirage and unikernels last week and find topic rather fascinating, so I de= cided to make it the focus of my undergraduate research project this semest= er. I don't have much experience with OCaml or with functional language= s in general, but I've started on Real World OCaml.
>
> I'd greatly appreciate any suggestions you provide!
>
> -- Aaron
>
> _______________________________________________
> 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
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel

--485b397dd1f3b9c79f05025f88b5-- --===============0834964418479326812== 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 --===============0834964418479326812==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 06:17:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 06:17: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 1XQ9J5-0003Se-OH; Sat, 06 Sep 2014 06:17:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQ9J4-0003SZ-7T for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 06:17:06 +0000 Received: from [85.158.139.211:10589] by server-15.bemta-5.messagelabs.com id 68/A6-12002-1E6AA045; Sat, 06 Sep 2014 06:17:05 +0000 X-Env-Sender: aaron.quamme@gmail.com X-Msg-Ref: server-10.tower-206.messagelabs.com!1409984222!7507771!1 X-Originating-IP: [209.85.223.173] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3412 invoked from network); 6 Sep 2014 06:17:04 -0000 Received: from mail-ie0-f173.google.com (HELO mail-ie0-f173.google.com) (209.85.223.173) by server-10.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 6 Sep 2014 06:17:04 -0000 Received: by mail-ie0-f173.google.com with SMTP id lx4so15320141iec.18 for ; Fri, 05 Sep 2014 23:17:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7CoAEo3ljppxzXRUTZDUAZsSUBckIUfbRK9ffhJX7Oc=; b=n84e2wYwMUDc84JB+vPIseyzEe8WSfvJXEZep0wfx/FybWlAVwKBn6tHRWN78OTrEV OTW3T7uDhS6KIHVzHPu7UDwtPxIdiQX+HFJhXadGYfs6Iox4Fkwr1U8xkS1XszD1fRL3 ACrCHXqInkM4Ep8S4xddz/n3Wbd3tuf9hSuON8tVWZj8++YzEPeB1TxQ1q/5+9RFuxA1 MFiJdAwcLdWsjI0HdGW9gpS19xKWn4uQtu3rDS6ROf9h4DFo+5liEUHNMs2JO9tLWrD1 Kdtrw3VjtvlODy9WOq7HaG+oH2SWztCbOmJewbf5GSdHh0lmCARhBB0cOAuV7ZxudXk7 sO9A== MIME-Version: 1.0 X-Received: by 10.42.58.65 with SMTP id g1mr19585013ich.38.1409984222576; Fri, 05 Sep 2014 23:17:02 -0700 (PDT) Received: by 10.64.117.229 with HTTP; Fri, 5 Sep 2014 23:17:02 -0700 (PDT) Received: by 10.64.117.229 with HTTP; Fri, 5 Sep 2014 23:17:02 -0700 (PDT) In-Reply-To: References: Date: Sat, 6 Sep 2014 01:17:02 -0500 Message-ID: From: Aaron Quamme To: Anil Madhavapeddy Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0834964418479326812==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0834964418479326812== Content-Type: multipart/alternative; boundary=485b397dd1f3b9c79f05025f88b5 --485b397dd1f3b9c79f05025f88b5 Content-Type: text/plain; charset=UTF-8 Thanks for the suggestions -- a DHCP server sounds like a good challenge! I'm thinking I'll start by reviewing the protocol and reading the source of some preexisting implementation - and by continuing with Real World OCaml, of course. I'm sure I'll have plenty of questions in the coming months. Thanks again! --Aaron Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml $ opam install dns $ (build mldig from mirage/ocaml-dns, it's not installed by default) $ mldig txt recoil.org ;; <<>> MLDiG 1.0 <<>> ;; global options: ;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;recoil.org. IN TXT ;; ANSWER SECTION: recoil.org. 10800 IN TXT "Llamaz United" +1 to the DHCP server though -- that would be most useful! -anil On 5 Sep 2014, at 12:03, Jon Crowcroft wrote: > Rewrite dig in ocaml, maybe? > > On Sep 5, 2014 1:11 AM, "Aaron Quamme" wrote: > Hello, > > I'm looking for suggestions in the vein of Stephen's project - something relatively small and non-critical but still useful. I discovered Mirage and unikernels last week and find topic rather fascinating, so I decided to make it the focus of my undergraduate research project this semester. I don't have much experience with OCaml or with functional languages in general, but I've started on Real World OCaml. > > I'd greatly appreciate any suggestions you provide! > > -- Aaron > > _______________________________________________ > 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 --485b397dd1f3b9c79f05025f88b5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Thanks for the suggestions -- a DHCP server sounds like a go= od challenge!=C2=A0

I'm thinking I'll start by reviewing the protocol an= d reading the source of some preexisting implementation - and by continuing= with Real World OCaml, of course. I'm sure I'll have plenty of que= stions in the coming months. Thanks again!

--Aaron

Sorry :-) htt= ps://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml

$ opam install dns
$ (build mldig from mirage/ocaml-dns, it's not installed by default) $ mldig txt recoil.org<= br> ;; <<>> MLDiG 1.0 <<>>
;; global options:
;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;recoil.org.=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IN=C2=A0= =C2=A0 =C2=A0 =C2=A0TXT

;; ANSWER SECTION:
recoil.org.=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 10800=C2=A0 =C2=A0 IN=C2=A0 =C2=A0 = =C2=A0 =C2=A0TXT=C2=A0 =C2=A0 =C2=A0 "Llamaz United"

+1 to the DHCP server though -- that would be most useful!

-anil

On 5 Sep 2014, at 12:03, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk> wrote:

> Rewrite dig in ocaml, maybe?
>
> On Sep 5, 2014 1:11 AM, "Aaron Quamme" <aaron.quamme@gmail.com> wrote:
> Hello,
>
> I'm looking for suggestions in the vein of Stephen's project -= something relatively small and non-critical but still useful. I discovered= Mirage and unikernels last week and find topic rather fascinating, so I de= cided to make it the focus of my undergraduate research project this semest= er. I don't have much experience with OCaml or with functional language= s in general, but I've started on Real World OCaml.
>
> I'd greatly appreciate any suggestions you provide!
>
> -- Aaron
>
> _______________________________________________
> 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
> http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel

--485b397dd1f3b9c79f05025f88b5-- --===============0834964418479326812== 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 --===============0834964418479326812==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 10:26:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 10:26: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 1XQDCf-0001Yf-QT; Sat, 06 Sep 2014 10:26:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQDCf-0001Ya-45 for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 10:26:45 +0000 Received: from [85.158.139.211:2769] by server-12.bemta-5.messagelabs.com id 5D/AF-22251-461EA045; Sat, 06 Sep 2014 10:26:44 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1409999203!8718926!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19899 invoked from network); 6 Sep 2014 10:26:43 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-206.messagelabs.com with SMTP; 6 Sep 2014 10:26:43 -0000 Received: (qmail 2710 invoked by uid 634); 6 Sep 2014 10:26:42 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 11:26:40 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 12:26:39 +0200 Message-Id: References: To: Kiwamu Okabe X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] MirageOS can shape reentrancy in Unix-like kernel? X-BeenThere: mirageos-devel@lists.xenproject.org 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 Kiwamu, Metasepi is a very cool project, and it's great to see it making progress. We do have a plan for how to implement a Unix-like OS in Mirage. The best way to think about this that the userspace ABI for POSIX is mostly via the syscall ABI and memory mappings. Therefore, if we can provide an "OCaml syscall server" that is ABI compatible, it's possible to implement the wider ABI. To build these ABI-compatible interfaces, we have a library called "Ctypes" that's written by Jeremy Yallop, available from https://github.com/ocamllabs/ocaml-ctypes In addition to making calls *to* foreign libraries, it can also work in reverse mode to expose a C ABI from an OCaml library. See: https://github.com/yallop/ocaml-ctypes-inverted-stubs-example This is a very brief answer to a much more complex problem, but I thought I would point you at the first step along the path :-) Feel free to ask more questions as you run across them! best, Anil On 5 Sep 2014, at 22:26, Kiwamu Okabe wrote: > Hi all, > > I'm interested in your Mirage OS running on Bare Metal hardware. > My question is that it can shape reentrancy in Unix-like kernel? > > I found http://metasepi.org/ that aim to be Unix-like OS with strong type. > Today we choose ATS language. > > http://www.ats-lang.org/ > > However, ATS is hard for normal programmer. > If Mirage OS can write Unix kernel in future, our project is so happy. > > Thank's, > -- > Kiwamu Okabe at METASEPI DESIGN > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 10:26:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 10:26: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 1XQDCf-0001Yf-QT; Sat, 06 Sep 2014 10:26:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQDCf-0001Ya-45 for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 10:26:45 +0000 Received: from [85.158.139.211:2769] by server-12.bemta-5.messagelabs.com id 5D/AF-22251-461EA045; Sat, 06 Sep 2014 10:26:44 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1409999203!8718926!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19899 invoked from network); 6 Sep 2014 10:26:43 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-206.messagelabs.com with SMTP; 6 Sep 2014 10:26:43 -0000 Received: (qmail 2710 invoked by uid 634); 6 Sep 2014 10:26:42 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 11:26:40 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 12:26:39 +0200 Message-Id: References: To: Kiwamu Okabe X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] MirageOS can shape reentrancy in Unix-like kernel? X-BeenThere: mirageos-devel@lists.xenproject.org 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 Kiwamu, Metasepi is a very cool project, and it's great to see it making progress. We do have a plan for how to implement a Unix-like OS in Mirage. The best way to think about this that the userspace ABI for POSIX is mostly via the syscall ABI and memory mappings. Therefore, if we can provide an "OCaml syscall server" that is ABI compatible, it's possible to implement the wider ABI. To build these ABI-compatible interfaces, we have a library called "Ctypes" that's written by Jeremy Yallop, available from https://github.com/ocamllabs/ocaml-ctypes In addition to making calls *to* foreign libraries, it can also work in reverse mode to expose a C ABI from an OCaml library. See: https://github.com/yallop/ocaml-ctypes-inverted-stubs-example This is a very brief answer to a much more complex problem, but I thought I would point you at the first step along the path :-) Feel free to ask more questions as you run across them! best, Anil On 5 Sep 2014, at 22:26, Kiwamu Okabe wrote: > Hi all, > > I'm interested in your Mirage OS running on Bare Metal hardware. > My question is that it can shape reentrancy in Unix-like kernel? > > I found http://metasepi.org/ that aim to be Unix-like OS with strong type. > Today we choose ATS language. > > http://www.ats-lang.org/ > > However, ATS is hard for normal programmer. > If Mirage OS can write Unix kernel in future, our project is so happy. > > Thank's, > -- > Kiwamu Okabe at METASEPI DESIGN > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 12:07:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 12:07:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQElx-0004IO-B3; Sat, 06 Sep 2014 12:07:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQElv-0004IJ-UD for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 12:07:16 +0000 Received: from [85.158.143.35:48371] by server-1.bemta-4.messagelabs.com id B6/94-05872-3F8FA045; Sat, 06 Sep 2014 12:07:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1410005234!11723012!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20437 invoked from network); 6 Sep 2014 12:07:14 -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; 6 Sep 2014 12:07:14 -0000 Received: (qmail 24550 invoked by uid 634); 6 Sep 2014 12:07:13 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 13:07:10 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 12:26:39 +0200 Message-Id: References: To: Kiwamu Okabe X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] MirageOS can shape reentrancy in Unix-like kernel? X-BeenThere: mirageos-devel@lists.xenproject.org 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 Kiwamu, Metasepi is a very cool project, and it's great to see it making progress. We do have a plan for how to implement a Unix-like OS in Mirage. The best way to think about this that the userspace ABI for POSIX is mostly via the syscall ABI and memory mappings. Therefore, if we can provide an "OCaml syscall server" that is ABI compatible, it's possible to implement the wider ABI. To build these ABI-compatible interfaces, we have a library called "Ctypes" that's written by Jeremy Yallop, available from https://github.com/ocamllabs/ocaml-ctypes In addition to making calls *to* foreign libraries, it can also work in reverse mode to expose a C ABI from an OCaml library. See: https://github.com/yallop/ocaml-ctypes-inverted-stubs-example This is a very brief answer to a much more complex problem, but I thought I would point you at the first step along the path :-) Feel free to ask more questions as you run across them! best, Anil On 5 Sep 2014, at 22:26, Kiwamu Okabe wrote: > Hi all, > > I'm interested in your Mirage OS running on Bare Metal hardware. > My question is that it can shape reentrancy in Unix-like kernel? > > I found http://metasepi.org/ that aim to be Unix-like OS with strong type. > Today we choose ATS language. > > http://www.ats-lang.org/ > > However, ATS is hard for normal programmer. > If Mirage OS can write Unix kernel in future, our project is so happy. > > Thank's, > -- > Kiwamu Okabe at METASEPI DESIGN > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 12:07:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 12:07:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQElx-0004IO-B3; Sat, 06 Sep 2014 12:07:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQElv-0004IJ-UD for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 12:07:16 +0000 Received: from [85.158.143.35:48371] by server-1.bemta-4.messagelabs.com id B6/94-05872-3F8FA045; Sat, 06 Sep 2014 12:07:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1410005234!11723012!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20437 invoked from network); 6 Sep 2014 12:07:14 -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; 6 Sep 2014 12:07:14 -0000 Received: (qmail 24550 invoked by uid 634); 6 Sep 2014 12:07:13 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 13:07:10 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 12:26:39 +0200 Message-Id: References: To: Kiwamu Okabe X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] MirageOS can shape reentrancy in Unix-like kernel? X-BeenThere: mirageos-devel@lists.xenproject.org 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 Kiwamu, Metasepi is a very cool project, and it's great to see it making progress. We do have a plan for how to implement a Unix-like OS in Mirage. The best way to think about this that the userspace ABI for POSIX is mostly via the syscall ABI and memory mappings. Therefore, if we can provide an "OCaml syscall server" that is ABI compatible, it's possible to implement the wider ABI. To build these ABI-compatible interfaces, we have a library called "Ctypes" that's written by Jeremy Yallop, available from https://github.com/ocamllabs/ocaml-ctypes In addition to making calls *to* foreign libraries, it can also work in reverse mode to expose a C ABI from an OCaml library. See: https://github.com/yallop/ocaml-ctypes-inverted-stubs-example This is a very brief answer to a much more complex problem, but I thought I would point you at the first step along the path :-) Feel free to ask more questions as you run across them! best, Anil On 5 Sep 2014, at 22:26, Kiwamu Okabe wrote: > Hi all, > > I'm interested in your Mirage OS running on Bare Metal hardware. > My question is that it can shape reentrancy in Unix-like kernel? > > I found http://metasepi.org/ that aim to be Unix-like OS with strong type. > Today we choose ATS language. > > http://www.ats-lang.org/ > > However, ATS is hard for normal programmer. > If Mirage OS can write Unix kernel in future, our project is so happy. > > Thank's, > -- > Kiwamu Okabe at METASEPI DESIGN > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 12:07:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 12:07: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 1XQEm7-0004Ir-Dl; Sat, 06 Sep 2014 12:07:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQEm5-0004Ig-NY for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 12:07:25 +0000 Received: from [85.158.143.35:31862] by server-1.bemta-4.messagelabs.com id 62/A4-05872-DF8FA045; Sat, 06 Sep 2014 12:07:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-21.messagelabs.com!1410005243!12093119!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3991 invoked from network); 6 Sep 2014 12:07:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-21.messagelabs.com with SMTP; 6 Sep 2014 12:07:23 -0000 Received: (qmail 10088 invoked by uid 634); 6 Sep 2014 12:07: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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 13:07:19 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 12:26:41 +0200 Message-Id: References: To: Aaron Quamme X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4855115253970619168==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4855115253970619168== Content-Type: multipart/alternative; boundary="Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660" --Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Remember also that it's ok to rewrite the existing code too! Mindy Preston can confirm that the DHCP code is rather crufty (and was = written very early in Mirage, so it doesn't use modern libraries like = cstruct): = http://www.somerandomidiot.com/blog/2014/03/24/arriving-at-the-mirage/ -anil On 6 Sep 2014, at 08:17, Aaron Quamme wrote: > Thanks for the suggestions -- a DHCP server sounds like a good = challenge!=20 >=20 > I'm thinking I'll start by reviewing the protocol and reading the = source of some preexisting implementation - and by continuing with Real = World OCaml, of course. I'm sure I'll have plenty of questions in the = coming months. Thanks again! >=20 > --Aaron >=20 > Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml >=20 > $ opam install dns > $ (build mldig from mirage/ocaml-dns, it's not installed by default) > $ mldig txt recoil.org > ;; <<>> MLDiG 1.0 <<>> > ;; global options: > ;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 > ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 >=20 > ;; QUESTION SECTION: > ;recoil.org. IN TXT >=20 > ;; ANSWER SECTION: > recoil.org. 10800 IN TXT "Llamaz United" >=20 > +1 to the DHCP server though -- that would be most useful! >=20 > -anil >=20 > On 5 Sep 2014, at 12:03, Jon Crowcroft = wrote: >=20 > > Rewrite dig in ocaml, maybe? > > > > On Sep 5, 2014 1:11 AM, "Aaron Quamme" = wrote: > > Hello, > > > > I'm looking for suggestions in the vein of Stephen's project - = something relatively small and non-critical but still useful. I = discovered Mirage and unikernels last week and find topic rather = fascinating, so I decided to make it the focus of my undergraduate = research project this semester. I don't have much experience with OCaml = or with functional languages in general, but I've started on Real World = OCaml. > > > > I'd greatly appreciate any suggestions you provide! > > > > -- Aaron > > > > _______________________________________________ > > 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 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Remember also that it's ok to rewrite the existing = code too!

Mindy Preston can confirm that the DHCP = code is rather crufty (and was written very early in Mirage, so it = doesn't use modern libraries like cstruct): http://www.somerandomidiot.com/blog/2014/03/24/arriving-at-the-mirag= e/

-anil

On 6 Sep 2014, = at 08:17, Aaron Quamme <aaron.quamme@gmail.com> = wrote:

Thanks for the suggestions -- a DHCP server = sounds like a good challenge! 

I'm thinking I'll = start by reviewing the protocol and reading the source of some = preexisting implementation - and by continuing with Real World OCaml, of = course. I'm sure I'll have plenty of questions in the coming months. = Thanks again!

--Aaron

Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldi= g.ml

$ opam install dns
$ (build mldig from mirage/ocaml-dns, it's not installed by default)
$ mldig txt recoil.org
;; <<>> MLDiG 1.0 <<>>
;; global options:
;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: = 57877
;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;recoil.org.  =                     = IN       TXT

;; ANSWER SECTION:
recoil.org.  =             10800    IN  =      TXT      "Llamaz United"

+1 to the DHCP server though -- that would be most useful!

-anil

On 5 Sep 2014, at 12:03, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk&= gt; wrote:

> Rewrite dig in ocaml, maybe?
>
> On Sep 5, 2014 1:11 AM, "Aaron Quamme" <aaron.quamme@gmail.com> = wrote:
> Hello,
>
> I'm looking for suggestions in the vein of Stephen's project - = something relatively small and non-critical but still useful. I = discovered Mirage and unikernels last week and find topic rather = fascinating, so I decided to make it the focus of my undergraduate = research project this semester. I don't have much experience with OCaml = or with functional languages in general, but I've started on Real World = OCaml.
>
> I'd greatly appreciate any suggestions you provide!
>
> -- Aaron
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.x= enproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.x= enproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel

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

= --Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660-- --===============4855115253970619168== 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 --===============4855115253970619168==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 12:07:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 12:07: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 1XQEm7-0004Ir-Dl; Sat, 06 Sep 2014 12:07:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQEm5-0004Ig-NY for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 12:07:25 +0000 Received: from [85.158.143.35:31862] by server-1.bemta-4.messagelabs.com id 62/A4-05872-DF8FA045; Sat, 06 Sep 2014 12:07:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-21.messagelabs.com!1410005243!12093119!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3991 invoked from network); 6 Sep 2014 12:07:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-21.messagelabs.com with SMTP; 6 Sep 2014 12:07:23 -0000 Received: (qmail 10088 invoked by uid 634); 6 Sep 2014 12:07: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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 13:07:19 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 12:26:41 +0200 Message-Id: References: To: Aaron Quamme X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage project suggestions for another newcomer X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4855115253970619168==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4855115253970619168== Content-Type: multipart/alternative; boundary="Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660" --Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Remember also that it's ok to rewrite the existing code too! Mindy Preston can confirm that the DHCP code is rather crufty (and was = written very early in Mirage, so it doesn't use modern libraries like = cstruct): = http://www.somerandomidiot.com/blog/2014/03/24/arriving-at-the-mirage/ -anil On 6 Sep 2014, at 08:17, Aaron Quamme wrote: > Thanks for the suggestions -- a DHCP server sounds like a good = challenge!=20 >=20 > I'm thinking I'll start by reviewing the protocol and reading the = source of some preexisting implementation - and by continuing with Real = World OCaml, of course. I'm sure I'll have plenty of questions in the = coming months. Thanks again! >=20 > --Aaron >=20 > Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldig.ml >=20 > $ opam install dns > $ (build mldig from mirage/ocaml-dns, it's not installed by default) > $ mldig txt recoil.org > ;; <<>> MLDiG 1.0 <<>> > ;; global options: > ;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: 57877 > ;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 >=20 > ;; QUESTION SECTION: > ;recoil.org. IN TXT >=20 > ;; ANSWER SECTION: > recoil.org. 10800 IN TXT "Llamaz United" >=20 > +1 to the DHCP server though -- that would be most useful! >=20 > -anil >=20 > On 5 Sep 2014, at 12:03, Jon Crowcroft = wrote: >=20 > > Rewrite dig in ocaml, maybe? > > > > On Sep 5, 2014 1:11 AM, "Aaron Quamme" = wrote: > > Hello, > > > > I'm looking for suggestions in the vein of Stephen's project - = something relatively small and non-critical but still useful. I = discovered Mirage and unikernels last week and find topic rather = fascinating, so I decided to make it the focus of my undergraduate = research project this semester. I don't have much experience with OCaml = or with functional languages in general, but I've started on Real World = OCaml. > > > > I'd greatly appreciate any suggestions you provide! > > > > -- Aaron > > > > _______________________________________________ > > 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 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Remember also that it's ok to rewrite the existing = code too!

Mindy Preston can confirm that the DHCP = code is rather crufty (and was written very early in Mirage, so it = doesn't use modern libraries like cstruct): http://www.somerandomidiot.com/blog/2014/03/24/arriving-at-the-mirag= e/

-anil

On 6 Sep 2014, = at 08:17, Aaron Quamme <aaron.quamme@gmail.com> = wrote:

Thanks for the suggestions -- a DHCP server = sounds like a good challenge! 

I'm thinking I'll = start by reviewing the protocol and reading the source of some = preexisting implementation - and by continuing with Real World OCaml, of = course. I'm sure I'll have plenty of questions in the coming months. = Thanks again!

--Aaron

Sorry :-) https://github.com/mirage/ocaml-dns/blob/master/lwt/mldi= g.ml

$ opam install dns
$ (build mldig from mirage/ocaml-dns, it's not installed by default)
$ mldig txt recoil.org
;; <<>> MLDiG 1.0 <<>>
;; global options:
;; ->>HEADER<<- opcode: STANDARD, status: NOERROR, id: = 57877
;; flags: tc aa qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;recoil.org.  =                     = IN       TXT

;; ANSWER SECTION:
recoil.org.  =             10800    IN  =      TXT      "Llamaz United"

+1 to the DHCP server though -- that would be most useful!

-anil

On 5 Sep 2014, at 12:03, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk&= gt; wrote:

> Rewrite dig in ocaml, maybe?
>
> On Sep 5, 2014 1:11 AM, "Aaron Quamme" <aaron.quamme@gmail.com> = wrote:
> Hello,
>
> I'm looking for suggestions in the vein of Stephen's project - = something relatively small and non-critical but still useful. I = discovered Mirage and unikernels last week and find topic rather = fascinating, so I decided to make it the focus of my undergraduate = research project this semester. I don't have much experience with OCaml = or with functional languages in general, but I've started on Real World = OCaml.
>
> I'd greatly appreciate any suggestions you provide!
>
> -- Aaron
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.x= enproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel
>
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.x= enproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel

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

= --Apple-Mail=_BCEC2592-6F7D-45B1-A5F6-08C35F840660-- --===============4855115253970619168== 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 --===============4855115253970619168==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 12:45:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 12:45: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 1XQFMb-0005QR-SL; Sat, 06 Sep 2014 12:45:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQFMa-0005QM-Pp for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 12:45:09 +0000 Received: from [85.158.143.35:12956] by server-2.bemta-4.messagelabs.com id B4/7B-04525-3D10B045; Sat, 06 Sep 2014 12:45:07 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1410007506!12001276!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9518 invoked from network); 6 Sep 2014 12:45:06 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-21.messagelabs.com with SMTP; 6 Sep 2014 12:45:06 -0000 Received: (qmail 17861 invoked by uid 634); 6 Sep 2014 12:45:06 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 13:45:05 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 14:45:03 +0200 Message-Id: <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org> References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Thinking out loud about secure unikernal communication over the internet X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7306049420106967410==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7306049420106967410== Content-Type: multipart/alternative; boundary="Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63" --Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Stephen, It's definitely possible to come up with new protocols, but you need to = be very careful when designing them. Where possible, we're currently = preferring to follow existing protocols to ensure that we don't end up = in a situation of having experimental protocols layered on experimental = implementations, leading to overall instability. This doesn't stop any interested community members from building = independent implementations of protocols such as the Silent Circle one = below -- feel free to ask any questions here as you go about the = implementation! I'm personally working on integrating the OCaml TLS = stack into our I/O layer first though, to give us SSL interop as a good = baseline protocol. best, Anil On 6 Sep 2014, at 02:40, Stephen Mack wrote: > Hello everyone, >=20 > With all the buzz about hacking lately, I have been thinking a lot = about security. Since our mirage unikernals will be living all over the = internet, they will be needing a secure way to talk to each and to move = data around. >=20 > There are of course a lot of different protocols such as HTTPS or the = alphabet soup of VPN protocols. >=20 > It would however be nice to keep to our unikernal roots and have a = quick and secure protocol that could be spun up and used quickly and = efficiently then destroyed. >=20 > I would love to hear ideas from the community. >=20 > I have recently discovered a new IM protocol being developed by Silent = Circle called SCIMP. One of it's benefits is that the secret key = changes with each message so if someone is recording and saving your = traffic, they can never get access to old messages with the current key. >=20 > https://silentcircle.com/scimp-protocol >=20 > It would be good for Mirage to be secure out of the box. >=20 > --Stephen > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Stephen,

It's = definitely possible to come up with new protocols, but you need to be = very careful when designing them.  Where possible, we're currently = preferring to follow existing protocols to ensure that we don't end up = in a situation of having experimental protocols layered on experimental = implementations, leading to overall = instability.

This doesn't stop any interested = community members from building independent implementations of protocols = such as the Silent Circle one below -- feel free to ask any questions = here as you go about the implementation!  I'm personally working on = integrating the OCaml TLS stack into our I/O layer first though, to give = us SSL interop as a good baseline = protocol.

best,
Anil

On 6 Sep 2014, at 02:40, Stephen Mack <smack815@gmail.com> = wrote:

Hello everyone,

With = all the buzz about hacking lately, I have been thinking a lot about = security.  Since our mirage unikernals will be living all over the = internet, they will be needing a secure way to talk to each and to move = data around.

There are of course a lot of = different protocols such as HTTPS or the alphabet soup of VPN = protocols.

It would however be nice to keep to = our unikernal roots and have a quick and secure protocol that could be = spun up and used quickly and efficiently then = destroyed.

I would love to hear ideas from the = community.

I have recently discovered a new IM = protocol being developed by Silent Circle called SCIMP.  One of = it's benefits is that the secret key changes with each message so if = someone is recording and saving your traffic, they can never get access = to old messages with the current key.


It would be good for = Mirage to be secure out of the = box.

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

= --Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63-- --===============7306049420106967410== 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 --===============7306049420106967410==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 12:45:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 12:45: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 1XQFMb-0005QR-SL; Sat, 06 Sep 2014 12:45:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQFMa-0005QM-Pp for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 12:45:09 +0000 Received: from [85.158.143.35:12956] by server-2.bemta-4.messagelabs.com id B4/7B-04525-3D10B045; Sat, 06 Sep 2014 12:45:07 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1410007506!12001276!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9518 invoked from network); 6 Sep 2014 12:45:06 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-21.messagelabs.com with SMTP; 6 Sep 2014 12:45:06 -0000 Received: (qmail 17861 invoked by uid 634); 6 Sep 2014 12:45:06 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 13:45:05 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 14:45:03 +0200 Message-Id: <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org> References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Thinking out loud about secure unikernal communication over the internet X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7306049420106967410==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7306049420106967410== Content-Type: multipart/alternative; boundary="Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63" --Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Stephen, It's definitely possible to come up with new protocols, but you need to = be very careful when designing them. Where possible, we're currently = preferring to follow existing protocols to ensure that we don't end up = in a situation of having experimental protocols layered on experimental = implementations, leading to overall instability. This doesn't stop any interested community members from building = independent implementations of protocols such as the Silent Circle one = below -- feel free to ask any questions here as you go about the = implementation! I'm personally working on integrating the OCaml TLS = stack into our I/O layer first though, to give us SSL interop as a good = baseline protocol. best, Anil On 6 Sep 2014, at 02:40, Stephen Mack wrote: > Hello everyone, >=20 > With all the buzz about hacking lately, I have been thinking a lot = about security. Since our mirage unikernals will be living all over the = internet, they will be needing a secure way to talk to each and to move = data around. >=20 > There are of course a lot of different protocols such as HTTPS or the = alphabet soup of VPN protocols. >=20 > It would however be nice to keep to our unikernal roots and have a = quick and secure protocol that could be spun up and used quickly and = efficiently then destroyed. >=20 > I would love to hear ideas from the community. >=20 > I have recently discovered a new IM protocol being developed by Silent = Circle called SCIMP. One of it's benefits is that the secret key = changes with each message so if someone is recording and saving your = traffic, they can never get access to old messages with the current key. >=20 > https://silentcircle.com/scimp-protocol >=20 > It would be good for Mirage to be secure out of the box. >=20 > --Stephen > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Stephen,

It's = definitely possible to come up with new protocols, but you need to be = very careful when designing them.  Where possible, we're currently = preferring to follow existing protocols to ensure that we don't end up = in a situation of having experimental protocols layered on experimental = implementations, leading to overall = instability.

This doesn't stop any interested = community members from building independent implementations of protocols = such as the Silent Circle one below -- feel free to ask any questions = here as you go about the implementation!  I'm personally working on = integrating the OCaml TLS stack into our I/O layer first though, to give = us SSL interop as a good baseline = protocol.

best,
Anil

On 6 Sep 2014, at 02:40, Stephen Mack <smack815@gmail.com> = wrote:

Hello everyone,

With = all the buzz about hacking lately, I have been thinking a lot about = security.  Since our mirage unikernals will be living all over the = internet, they will be needing a secure way to talk to each and to move = data around.

There are of course a lot of = different protocols such as HTTPS or the alphabet soup of VPN = protocols.

It would however be nice to keep to = our unikernal roots and have a quick and secure protocol that could be = spun up and used quickly and efficiently then = destroyed.

I would love to hear ideas from the = community.

I have recently discovered a new IM = protocol being developed by Silent Circle called SCIMP.  One of = it's benefits is that the secret key changes with each message so if = someone is recording and saving your traffic, they can never get access = to old messages with the current key.


It would be good for = Mirage to be secure out of the = box.

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

= --Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63-- --===============7306049420106967410== 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 --===============7306049420106967410==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 06 13:00:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 13:00:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQFbX-0005sK-1Q; Sat, 06 Sep 2014 13:00:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQFbV-0005sF-DN for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 13:00:33 +0000 Received: from [85.158.137.68:9543] by server-10.bemta-3.messagelabs.com id 62/3B-01456-0750B045; Sat, 06 Sep 2014 13:00:32 +0000 X-Env-Sender: jac22@cl.cam.ac.uk X-Msg-Ref: server-8.tower-31.messagelabs.com!1410008431!12909895!1 X-Originating-IP: [128.232.25.20] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8299 invoked from network); 6 Sep 2014 13:00:31 -0000 Received: from mta0.cl.cam.ac.uk (HELO mta0.cl.cam.ac.uk) (128.232.25.20) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2014 13:00:31 -0000 Received: from sandy.cl.cam.ac.uk ([128.232.64.182] ident=jac22) by mta0.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1XQFbS-0002K1-B2; Sat, 06 Sep 2014 14:00:30 +0100 From: Jon Crowcroft To: Anil Madhavapeddy In-reply-to: <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org> References: <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org> Comments: In-reply-to Anil Madhavapeddy message dated "Sat, 06 Sep 2014 14:45:03 +0200." MIME-Version: 1.0 Content-ID: <10824.1410008430.1@sandy.cl.cam.ac.uk> Date: Sat, 06 Sep 2014 14:00:30 +0100 Message-Id: Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Thinking out loud about secure unikernal communication over the internet X-BeenThere: mirageos-devel@lists.xenproject.org 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 nice simple protocol to try is TFTP In missive <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org>, Anil Madhavapeddy typed: >>Content-Type: text/plain; >> charset=us-ascii >> >>Hi Stephen, >> >>It's definitely possible to come up with new protocols, but you need to = >>be very careful when designing them. Where possible, we're currently = >>preferring to follow existing protocols to ensure that we don't end up = >>in a situation of having experimental protocols layered on experimental = >>implementations, leading to overall instability. >> >>This doesn't stop any interested community members from building = >>independent implementations of protocols such as the Silent Circle one = >>below -- feel free to ask any questions here as you go about the = >>implementation! I'm personally working on integrating the OCaml TLS = >>stack into our I/O layer first though, to give us SSL interop as a good = >>baseline protocol. >> >>best, >>Anil >> >>On 6 Sep 2014, at 02:40, Stephen Mack wrote: >> >>> Hello everyone, >>>=20 >>> With all the buzz about hacking lately, I have been thinking a lot = >>about security. Since our mirage unikernals will be living all over the = >>internet, they will be needing a secure way to talk to each and to move = >>data around. >>>=20 >>> There are of course a lot of different protocols such as HTTPS or the = >>alphabet soup of VPN protocols. >>>=20 >>> It would however be nice to keep to our unikernal roots and have a = >>quick and secure protocol that could be spun up and used quickly and = >>efficiently then destroyed. >>>=20 >>> I would love to hear ideas from the community. >>>=20 >>> I have recently discovered a new IM protocol being developed by Silent = >>Circle called SCIMP. One of it's benefits is that the secret key = >>changes with each message so if someone is recording and saving your = >>traffic, they can never get access to old messages with the current key. >>>=20 >>> https://silentcircle.com/scimp-protocol >>>=20 >>> It would be good for Mirage to be secure out of the box. >>>=20 >>> --Stephen >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >>--Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63 >>Content-Transfer-Encoding: quoted-printable >>Content-Type: text/html; >> charset=us-ascii >> >>>charset=3Dus-ascii">>-webkit-nbsp-mode: space; -webkit-line-break: = >>after-white-space;">
Hi Stephen,

It's = >>definitely possible to come up with new protocols, but you need to be = >>very careful when designing them.  Where possible, we're currently = >>preferring to follow existing protocols to ensure that we don't end up = >>in a situation of having experimental protocols layered on experimental = >>implementations, leading to overall = >>instability.

This doesn't stop any interested = >>community members from building independent implementations of protocols = >>such as the Silent Circle one below -- feel free to ask any questions = >>here as you go about the implementation!  I'm personally working on = >>integrating the OCaml TLS stack into our I/O layer first though, to give = >>us SSL interop as a good baseline = >>protocol.

best,
Anil

>v>On 6 Sep 2014, at 02:40, Stephen Mack <>href=3D"mailto:smack815@gmail.com">smack815@gmail.com> = >>wrote:

>type=3D"cite">
Hello everyone,

With = >>all the buzz about hacking lately, I have been thinking a lot about = >>security.  Since our mirage unikernals will be living all over the = >>internet, they will be needing a secure way to talk to each and to move = >>data around.

There are of course a lot of = >>different protocols such as HTTPS or the alphabet soup of VPN = >>protocols.

It would however be nice to keep to = >>our unikernal roots and have a quick and secure protocol that could be = >>spun up and used quickly and efficiently then = >>destroyed.

I would love to hear ideas from the = >>community.

I have recently discovered a new IM = >>protocol being developed by Silent Circle called SCIMP.  One of = >>it's benefits is that the secret key changes with each message so if = >>someone is recording and saving your traffic, they can never get access = >>to old messages with the current key.


It would be good for = >>Mirage to be secure out of the = >>box.

--Stephen
>>_______________________________________________
MirageOS-devel = >>mailing list
>href=3D"mailto:MirageOS-devel@lists.xenproject.org">MirageOS-devel@lists.x= >>enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= >>mirageos-devel

= >> >>--Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63-- >> >> >>--===============7306049420106967410== >>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 >> >>--===============7306049420106967410==-- >> cheers jon _______________________________________________ MirageOS-devel 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 Sep 06 13:00:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 13:00:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQFbX-0005sK-1Q; Sat, 06 Sep 2014 13:00:35 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQFbV-0005sF-DN for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 13:00:33 +0000 Received: from [85.158.137.68:9543] by server-10.bemta-3.messagelabs.com id 62/3B-01456-0750B045; Sat, 06 Sep 2014 13:00:32 +0000 X-Env-Sender: jac22@cl.cam.ac.uk X-Msg-Ref: server-8.tower-31.messagelabs.com!1410008431!12909895!1 X-Originating-IP: [128.232.25.20] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8299 invoked from network); 6 Sep 2014 13:00:31 -0000 Received: from mta0.cl.cam.ac.uk (HELO mta0.cl.cam.ac.uk) (128.232.25.20) by server-8.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Sep 2014 13:00:31 -0000 Received: from sandy.cl.cam.ac.uk ([128.232.64.182] ident=jac22) by mta0.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1XQFbS-0002K1-B2; Sat, 06 Sep 2014 14:00:30 +0100 From: Jon Crowcroft To: Anil Madhavapeddy In-reply-to: <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org> References: <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org> Comments: In-reply-to Anil Madhavapeddy message dated "Sat, 06 Sep 2014 14:45:03 +0200." MIME-Version: 1.0 Content-ID: <10824.1410008430.1@sandy.cl.cam.ac.uk> Date: Sat, 06 Sep 2014 14:00:30 +0100 Message-Id: Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Thinking out loud about secure unikernal communication over the internet X-BeenThere: mirageos-devel@lists.xenproject.org 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 nice simple protocol to try is TFTP In missive <1D234FB7-E577-4FDC-96A4-B95354707B44@recoil.org>, Anil Madhavapeddy typed: >>Content-Type: text/plain; >> charset=us-ascii >> >>Hi Stephen, >> >>It's definitely possible to come up with new protocols, but you need to = >>be very careful when designing them. Where possible, we're currently = >>preferring to follow existing protocols to ensure that we don't end up = >>in a situation of having experimental protocols layered on experimental = >>implementations, leading to overall instability. >> >>This doesn't stop any interested community members from building = >>independent implementations of protocols such as the Silent Circle one = >>below -- feel free to ask any questions here as you go about the = >>implementation! I'm personally working on integrating the OCaml TLS = >>stack into our I/O layer first though, to give us SSL interop as a good = >>baseline protocol. >> >>best, >>Anil >> >>On 6 Sep 2014, at 02:40, Stephen Mack wrote: >> >>> Hello everyone, >>>=20 >>> With all the buzz about hacking lately, I have been thinking a lot = >>about security. Since our mirage unikernals will be living all over the = >>internet, they will be needing a secure way to talk to each and to move = >>data around. >>>=20 >>> There are of course a lot of different protocols such as HTTPS or the = >>alphabet soup of VPN protocols. >>>=20 >>> It would however be nice to keep to our unikernal roots and have a = >>quick and secure protocol that could be spun up and used quickly and = >>efficiently then destroyed. >>>=20 >>> I would love to hear ideas from the community. >>>=20 >>> I have recently discovered a new IM protocol being developed by Silent = >>Circle called SCIMP. One of it's benefits is that the secret key = >>changes with each message so if someone is recording and saving your = >>traffic, they can never get access to old messages with the current key. >>>=20 >>> https://silentcircle.com/scimp-protocol >>>=20 >>> It would be good for Mirage to be secure out of the box. >>>=20 >>> --Stephen >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> >> >>--Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63 >>Content-Transfer-Encoding: quoted-printable >>Content-Type: text/html; >> charset=us-ascii >> >>>charset=3Dus-ascii">>-webkit-nbsp-mode: space; -webkit-line-break: = >>after-white-space;">
Hi Stephen,

It's = >>definitely possible to come up with new protocols, but you need to be = >>very careful when designing them.  Where possible, we're currently = >>preferring to follow existing protocols to ensure that we don't end up = >>in a situation of having experimental protocols layered on experimental = >>implementations, leading to overall = >>instability.

This doesn't stop any interested = >>community members from building independent implementations of protocols = >>such as the Silent Circle one below -- feel free to ask any questions = >>here as you go about the implementation!  I'm personally working on = >>integrating the OCaml TLS stack into our I/O layer first though, to give = >>us SSL interop as a good baseline = >>protocol.

best,
Anil

>v>On 6 Sep 2014, at 02:40, Stephen Mack <>href=3D"mailto:smack815@gmail.com">smack815@gmail.com> = >>wrote:

>type=3D"cite">
Hello everyone,

With = >>all the buzz about hacking lately, I have been thinking a lot about = >>security.  Since our mirage unikernals will be living all over the = >>internet, they will be needing a secure way to talk to each and to move = >>data around.

There are of course a lot of = >>different protocols such as HTTPS or the alphabet soup of VPN = >>protocols.

It would however be nice to keep to = >>our unikernal roots and have a quick and secure protocol that could be = >>spun up and used quickly and efficiently then = >>destroyed.

I would love to hear ideas from the = >>community.

I have recently discovered a new IM = >>protocol being developed by Silent Circle called SCIMP.  One of = >>it's benefits is that the secret key changes with each message so if = >>someone is recording and saving your traffic, they can never get access = >>to old messages with the current key.


It would be good for = >>Mirage to be secure out of the = >>box.

--Stephen
>>_______________________________________________
MirageOS-devel = >>mailing list
>href=3D"mailto:MirageOS-devel@lists.xenproject.org">MirageOS-devel@lists.x= >>enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= >>mirageos-devel

= >> >>--Apple-Mail=_9B498471-CA01-4C5F-A1E6-4AC11C67DA63-- >> >> >>--===============7306049420106967410== >>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 >> >>--===============7306049420106967410==-- >> cheers jon _______________________________________________ MirageOS-devel 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 Sep 06 13:52:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 13:52: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 1XQGPK-000734-AH; Sat, 06 Sep 2014 13:52:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQGPI-00072z-FA for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 13:52:00 +0000 Received: from [85.158.139.211:21823] by server-11.bemta-5.messagelabs.com id B1/23-11011-F711B045; Sat, 06 Sep 2014 13:51:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1410011518!12855016!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28326 invoked from network); 6 Sep 2014 13:51:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 6 Sep 2014 13:51:58 -0000 Received: (qmail 28368 invoked by uid 634); 6 Sep 2014 13:51:57 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 14:51:57 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 15:51:55 +0200 Message-Id: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 3 Sep 2014, at 10:59, Thomas Leonard wrote: > On 19 August 2014 20:28, Anil Madhavapeddy wrote: >> On 19 Aug 2014, at 14:26, Thomas Gazagnaire wrote: >> >>>>> Looks good -- since V2.mli isn't tagged yet, this can just extend the call >>>>> to `write` instead of having a `write2`. >>>> >>>> I actually tried that first, but it makes V1 incompatible with V2 >>>> which complicates things a bit. As it is, if you have a V2 module you >>>> can use it with anything that wants a V1 type, which makes upgrading >>>> easier. >>> >>> I'm not too worry about that, as we need to fix the error type definition at one point as well (and the FS module type) >>> >>>>> However, would it be better to >>>>> define an interface flags type in `NETWORK`, and just let the `write` call >>>>> supply a list of flags? That would permit easier extension to other >>>>> offloads in the future. >>>> >>>> Yes, probably. Should the flags type be abstract? >>> >>> A possibility might be to define a record 'flag' with at least one field called "checksum". Not sure too much abstraction is a good thing here. > > Presumably that will break existing code when we add more flags. Is that OK? Yeah, since the code will need to handle the new flag. > >> Agreed on both counts... > > OK, but in that case how do we upgrade to the V2 API? > > Currently, if you ask mirage for e.g. a "network" then you get a V1 > NETWORK. If V2 extends V1 then it can just give you a V2 NETWORK and > everything still works, which was the path I took for testing the > checksums. But if they're not compatible (and I agree they shouldn't > need to be) then more things will have to change. > > How will I ask mirage for a V1 vs V2 NETWORK? Like this? > > let main = foreign "Unikernel.Main" (console2 @-> network2 @-> job) Yeah, we need to explicitly split the EDSL to support the new versions. This shouldn't be hard -- we can make the default 'console' and other values of 'a typ be for V2, and include a Mirage.V1 module that exposes the old versions. -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 Sep 06 13:52:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 13:52: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 1XQGPK-000734-AH; Sat, 06 Sep 2014 13:52:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQGPI-00072z-FA for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 13:52:00 +0000 Received: from [85.158.139.211:21823] by server-11.bemta-5.messagelabs.com id B1/23-11011-F711B045; Sat, 06 Sep 2014 13:51:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1410011518!12855016!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28326 invoked from network); 6 Sep 2014 13:51:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 6 Sep 2014 13:51:58 -0000 Received: (qmail 28368 invoked by uid 634); 6 Sep 2014 13:51:57 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 14:51:57 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 6 Sep 2014 15:51:55 +0200 Message-Id: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 3 Sep 2014, at 10:59, Thomas Leonard wrote: > On 19 August 2014 20:28, Anil Madhavapeddy wrote: >> On 19 Aug 2014, at 14:26, Thomas Gazagnaire wrote: >> >>>>> Looks good -- since V2.mli isn't tagged yet, this can just extend the call >>>>> to `write` instead of having a `write2`. >>>> >>>> I actually tried that first, but it makes V1 incompatible with V2 >>>> which complicates things a bit. As it is, if you have a V2 module you >>>> can use it with anything that wants a V1 type, which makes upgrading >>>> easier. >>> >>> I'm not too worry about that, as we need to fix the error type definition at one point as well (and the FS module type) >>> >>>>> However, would it be better to >>>>> define an interface flags type in `NETWORK`, and just let the `write` call >>>>> supply a list of flags? That would permit easier extension to other >>>>> offloads in the future. >>>> >>>> Yes, probably. Should the flags type be abstract? >>> >>> A possibility might be to define a record 'flag' with at least one field called "checksum". Not sure too much abstraction is a good thing here. > > Presumably that will break existing code when we add more flags. Is that OK? Yeah, since the code will need to handle the new flag. > >> Agreed on both counts... > > OK, but in that case how do we upgrade to the V2 API? > > Currently, if you ask mirage for e.g. a "network" then you get a V1 > NETWORK. If V2 extends V1 then it can just give you a V2 NETWORK and > everything still works, which was the path I took for testing the > checksums. But if they're not compatible (and I agree they shouldn't > need to be) then more things will have to change. > > How will I ask mirage for a V1 vs V2 NETWORK? Like this? > > let main = foreign "Unikernel.Main" (console2 @-> network2 @-> job) Yeah, we need to explicitly split the EDSL to support the new versions. This shouldn't be hard -- we can make the default 'console' and other values of 'a typ be for V2, and include a Mirage.V1 module that exposes the old versions. -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 Sep 06 13:52:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 13:52:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQGQ8-00074a-EO; Sat, 06 Sep 2014 13:52:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQGQ7-00074U-6Z for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 13:52:51 +0000 Received: from [85.158.139.211:22980] by server-7.bemta-5.messagelabs.com id BD/21-30869-1B11B045; Sat, 06 Sep 2014 13:52:49 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-206.messagelabs.com!1410011568!12872129!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31943 invoked from network); 6 Sep 2014 13:52:48 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-206.messagelabs.com with SMTP; 6 Sep 2014 13:52:48 -0000 Received: (qmail 11486 invoked by uid 634); 6 Sep 2014 13:52:48 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 14:52:48 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <4DE36E8B-63BD-42AE-A28B-B67D26D66A08@nottingham.ac.uk> Date: Sat, 6 Sep 2014 15:52:47 +0200 Message-Id: <9A328D7B-512C-407F-8565-E9FEFBE9C362@recoil.org> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> <4DE36E8B-63BD-42AE-A28B-B67D26D66A08@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 3 Sep 2014, at 18:21, Richard Mortier wrote: > > On 3 Sep 2014, at 09:59, Thomas Leonard wrote: > >> How will I ask mirage for a V1 vs V2 NETWORK? Like this? >> >> let main = foreign "Unikernel.Main" (console2 @-> network2 @-> job) > > would it be possible to encapsulate by just opening a different module (or even namespace if that's a thing yet), e.g. via a config/command line option? or are there cases where we might want to mix V1 and V2? (can't immediately think of any; guess they might be dealt with by making things explicit anyway, ie., V1.console @-> V2.network @-> V2.job or somesuch?!) That's correct -- we should make all the versions explicit in mirage, but it's convenient to open V2 by default in version 2. -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 Sep 06 13:52:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 06 Sep 2014 13:52:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQGQ8-00074a-EO; Sat, 06 Sep 2014 13:52:52 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XQGQ7-00074U-6Z for mirageos-devel@lists.xenproject.org; Sat, 06 Sep 2014 13:52:51 +0000 Received: from [85.158.139.211:22980] by server-7.bemta-5.messagelabs.com id BD/21-30869-1B11B045; Sat, 06 Sep 2014 13:52:49 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-206.messagelabs.com!1410011568!12872129!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31943 invoked from network); 6 Sep 2014 13:52:48 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-206.messagelabs.com with SMTP; 6 Sep 2014 13:52:48 -0000 Received: (qmail 11486 invoked by uid 634); 6 Sep 2014 13:52:48 -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 Unknown (HELO [172.25.42.193]) (93.94.208.154) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 06 Sep 2014 14:52:48 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <4DE36E8B-63BD-42AE-A28B-B67D26D66A08@nottingham.ac.uk> Date: Sat, 6 Sep 2014 15:52:47 +0200 Message-Id: <9A328D7B-512C-407F-8565-E9FEFBE9C362@recoil.org> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> <4DE36E8B-63BD-42AE-A28B-B67D26D66A08@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] TCP checksum offload with Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 3 Sep 2014, at 18:21, Richard Mortier wrote: > > On 3 Sep 2014, at 09:59, Thomas Leonard wrote: > >> How will I ask mirage for a V1 vs V2 NETWORK? Like this? >> >> let main = foreign "Unikernel.Main" (console2 @-> network2 @-> job) > > would it be possible to encapsulate by just opening a different module (or even namespace if that's a thing yet), e.g. via a config/command line option? or are there cases where we might want to mix V1 and V2? (can't immediately think of any; guess they might be dealt with by making things explicit anyway, ie., V1.console @-> V2.network @-> V2.job or somesuch?!) That's correct -- we should make all the versions explicit in mirage, but it's convenient to open V2 by default in version 2. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Sep 08 19:27:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 08 Sep 2014 19:27:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR4aa-0003L9-44; Mon, 08 Sep 2014 19:27:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR4aZ-0003L1-0K for mirageos-devel@lists.xenproject.org; Mon, 08 Sep 2014 19:26:59 +0000 Received: from [193.109.254.147:64298] by server-16.bemta-14.messagelabs.com id D4/27-16990-2030E045; Mon, 08 Sep 2014 19:26:58 +0000 X-Env-Sender: russell.pavlicek@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1410204415!14252940!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26566 invoked from network); 8 Sep 2014 19:26:57 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Sep 2014 19:26:56 -0000 X-IronPort-AV: E=Sophos;i="5.04,487,1406592000"; d="scan'208,217";a="170242329" From: Russell Pavlicek To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: Xen Project User Summit is Next Monday in New York City Thread-Index: Ac/Lmcf8tl9P1VzMS92kiPNgB78Hcw== Date: Mon, 8 Sep 2014 19:26:35 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA20501775D@SJCPEX01CL03.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: [MirageOS-devel] Xen Project User Summit is Next Monday in New York City X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1051190437404321173==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1051190437404321173== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_" --_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just a reminder that the main user event in the Xen Project ecosystem occur= s next Monday, September 15 in the heart of New York City. If you use Xen, you'll want to be there. Hear about unikernels, OpenStack,= SUSE Cloud, security, features upcoming in 4.5, OSv, HaLVM, Xen Orchestra,= XenServer, Xen4CentOS, high availability, and more. Save 50% off using the code "XenUser50off". Get a full day of technical in= fo for just $39! Detailed information here: http://blog.xenproject.org/index.php/2014/09/05/save-50-learn-about-the-nex= t-wave-of-virtualization-at-xen-project-user-summit-sept-15-in-new-york-cit= y/ We hope to see you in New York next week! Russ Pavlicek Xen Project User Summit Program Coordinator --_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just a reminder that the main user event in the Xen Project ecosyste= m occurs next Monday, September 15 in the heart of New York City.

If you use Xen, you'll want to be there.  Hear about unikernels, OpenS= tack, SUSE Cloud, security, features upcoming in 4.5, OSv, HaLVM, Xen Orche= stra, XenServer, Xen4CentOS, high availability, and more.

Save 50% off using the code "XenUser50off".  Get a full day = of technical info for just $39!

Detailed information here:

http://blog.xenproject.org/index.php/2014/09/05/save-50-learn-about-the-nex= t-wave-of-virtualization-at-xen-project-user-summit-sept-15-in-new-york-cit= y/

We hope to see you in New York next week!

Russ Pavlicek
Xen Project User Summit Program Coordinator
--_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_-- --===============1051190437404321173== 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 --===============1051190437404321173==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 08 19:27:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 08 Sep 2014 19:27:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR4aa-0003L9-44; Mon, 08 Sep 2014 19:27:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR4aZ-0003L1-0K for mirageos-devel@lists.xenproject.org; Mon, 08 Sep 2014 19:26:59 +0000 Received: from [193.109.254.147:64298] by server-16.bemta-14.messagelabs.com id D4/27-16990-2030E045; Mon, 08 Sep 2014 19:26:58 +0000 X-Env-Sender: russell.pavlicek@citrix.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1410204415!14252940!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26566 invoked from network); 8 Sep 2014 19:26:57 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 8 Sep 2014 19:26:56 -0000 X-IronPort-AV: E=Sophos;i="5.04,487,1406592000"; d="scan'208,217";a="170242329" From: Russell Pavlicek To: "xen-devel@lists.xen.org" , "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Thread-Topic: Xen Project User Summit is Next Monday in New York City Thread-Index: Ac/Lmcf8tl9P1VzMS92kiPNgB78Hcw== Date: Mon, 8 Sep 2014 19:26:35 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA20501775D@SJCPEX01CL03.citrite.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: MIME-Version: 1.0 Subject: [MirageOS-devel] Xen Project User Summit is Next Monday in New York City X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1051190437404321173==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1051190437404321173== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_" --_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Just a reminder that the main user event in the Xen Project ecosystem occur= s next Monday, September 15 in the heart of New York City. If you use Xen, you'll want to be there. Hear about unikernels, OpenStack,= SUSE Cloud, security, features upcoming in 4.5, OSv, HaLVM, Xen Orchestra,= XenServer, Xen4CentOS, high availability, and more. Save 50% off using the code "XenUser50off". Get a full day of technical in= fo for just $39! Detailed information here: http://blog.xenproject.org/index.php/2014/09/05/save-50-learn-about-the-nex= t-wave-of-virtualization-at-xen-project-user-summit-sept-15-in-new-york-cit= y/ We hope to see you in New York next week! Russ Pavlicek Xen Project User Summit Program Coordinator --_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Just a reminder that the main user event in the Xen Project ecosyste= m occurs next Monday, September 15 in the heart of New York City.

If you use Xen, you'll want to be there.  Hear about unikernels, OpenS= tack, SUSE Cloud, security, features upcoming in 4.5, OSv, HaLVM, Xen Orche= stra, XenServer, Xen4CentOS, high availability, and more.

Save 50% off using the code "XenUser50off".  Get a full day = of technical info for just $39!

Detailed information here:

http://blog.xenproject.org/index.php/2014/09/05/save-50-learn-about-the-nex= t-wave-of-virtualization-at-xen-project-user-summit-sept-15-in-new-york-cit= y/

We hope to see you in New York next week!

Russ Pavlicek
Xen Project User Summit Program Coordinator
--_000_55E78A57290FB64FA0D3CF672F9F3DA20501775DSJCPEX01CL03cit_-- --===============1051190437404321173== 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 --===============1051190437404321173==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 08 22:24:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 08 Sep 2014 22:24:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR7Lu-0001hI-0E; Mon, 08 Sep 2014 22:24:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR7Ls-0001hC-84 for mirageos-devel@lists.xenproject.org; Mon, 08 Sep 2014 22:24:00 +0000 Received: from [85.158.139.211:40578] by server-9.bemta-5.messagelabs.com id 0F/7A-20744-F7C2E045; Mon, 08 Sep 2014 22:23:59 +0000 X-Env-Sender: jamesjb@galois.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1410215037!13219673!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13595 invoked from network); 8 Sep 2014 22:23:58 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Sep 2014 22:23:58 -0000 Received: from hurricane.galois.com (hurricane.galois.com [IPv6:2001:4870:e08e:200:5054:ff:fefa:ce41]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id s88MNqQV011077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 8 Sep 2014 15:23:56 -0700 Received: from [IPv6:2001:4870:e08e:201:8d59:eee5:1c3f:ec59] ([IPv6:2001:4870:e08e:201:8d59:eee5:1c3f:ec59]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id s88MNpes020531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 8 Sep 2014 15:23:52 -0700 Message-ID: <540E2C77.6050007@galois.com> Date: Mon, 08 Sep 2014 15:23:51 -0700 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Spam-Status: No, score=-3.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com Subject: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list 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'm doing some investigation into what it will take to merge our XenStore mandatory access control patches into the latest Mirage XenStore code base. My plan is to first submit a proposed interface for security modules to XenStore, pushing as much as possible into the external Flask module to keep the patch size down. After some time looking at the Irmin-based Xenstore, I have a few questions: - Is the repository at https://github.com/mirage/ocaml-xenstore-server the one I should be tracking, or is there a development repository? - I've been unable to compile a standalone Xen kernel because "mirage-xen" wants to install "xenstore" via OPAM, which conflicts with "ocaml-xenstore-server". Should that be working? Do I need to update to Mirage 2.x? - I see some code that appears to support mounting virtual trees of some sort (in server/mount.ml), but it doesn't seem to be used currently? One feature I need to do this integration is a virtual "/label" tree for reading/writing nodes security labels. What is the best way to implement a virtual subtree like this currently? - Likewise, I see code doing DAC checks in some modules, but those modules don't appear to be included in the build. Am I missing something or is the current version not performing access checks? Perhaps because the interdomain transport isn't being used? Thanks! James _______________________________________________ MirageOS-devel 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 Sep 08 22:24:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 08 Sep 2014 22:24:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR7Lu-0001hI-0E; Mon, 08 Sep 2014 22:24:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XR7Ls-0001hC-84 for mirageos-devel@lists.xenproject.org; Mon, 08 Sep 2014 22:24:00 +0000 Received: from [85.158.139.211:40578] by server-9.bemta-5.messagelabs.com id 0F/7A-20744-F7C2E045; Mon, 08 Sep 2014 22:23:59 +0000 X-Env-Sender: jamesjb@galois.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1410215037!13219673!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13595 invoked from network); 8 Sep 2014 22:23:58 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-5.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Sep 2014 22:23:58 -0000 Received: from hurricane.galois.com (hurricane.galois.com [IPv6:2001:4870:e08e:200:5054:ff:fefa:ce41]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id s88MNqQV011077 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 8 Sep 2014 15:23:56 -0700 Received: from [IPv6:2001:4870:e08e:201:8d59:eee5:1c3f:ec59] ([IPv6:2001:4870:e08e:201:8d59:eee5:1c3f:ec59]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id s88MNpes020531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Mon, 8 Sep 2014 15:23:52 -0700 Message-ID: <540E2C77.6050007@galois.com> Date: Mon, 08 Sep 2014 15:23:51 -0700 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Spam-Status: No, score=-3.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com Subject: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list 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'm doing some investigation into what it will take to merge our XenStore mandatory access control patches into the latest Mirage XenStore code base. My plan is to first submit a proposed interface for security modules to XenStore, pushing as much as possible into the external Flask module to keep the patch size down. After some time looking at the Irmin-based Xenstore, I have a few questions: - Is the repository at https://github.com/mirage/ocaml-xenstore-server the one I should be tracking, or is there a development repository? - I've been unable to compile a standalone Xen kernel because "mirage-xen" wants to install "xenstore" via OPAM, which conflicts with "ocaml-xenstore-server". Should that be working? Do I need to update to Mirage 2.x? - I see some code that appears to support mounting virtual trees of some sort (in server/mount.ml), but it doesn't seem to be used currently? One feature I need to do this integration is a virtual "/label" tree for reading/writing nodes security labels. What is the best way to implement a virtual subtree like this currently? - Likewise, I see code doing DAC checks in some modules, but those modules don't appear to be included in the build. Am I missing something or is the current version not performing access checks? Perhaps because the interdomain transport isn't being used? Thanks! James _______________________________________________ MirageOS-devel 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 Sep 09 12:02:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 12:02:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRK8L-0006MR-IP; Tue, 09 Sep 2014 12:02:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRK8K-0006MM-Me for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 12:02:53 +0000 Received: from [193.109.254.147:14967] by server-8.bemta-14.messagelabs.com id 1D/D3-01875-C6CEE045; Tue, 09 Sep 2014 12:02:52 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-14.tower-27.messagelabs.com!1410264170!14404076!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19563 invoked from network); 9 Sep 2014 12:02:51 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2014 12:02:51 -0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by gateway2.nyi.internal (Postfix) with ESMTP id 5872620DBE for ; Tue, 9 Sep 2014 08:02:50 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute1.internal (MEProxy); Tue, 09 Sep 2014 08:02:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= message-id:from:to:cc:mime-version:content-transfer-encoding :content-type:subject:date; s=mesmtp; bh=cI8tj5uwo4o0dmVfxSPUAaA KkE0=; b=d58t1dqIitIV0Zvtoryc60UF2meB6M5xxoYzkpBRsh5jMC0KGrFaJ1I okfeLV1ldaaaAvNFymoAJ1QaEedAgWbVJp5zwSidWIVFxsLchZtuhXonlX6G/BU1 6X19SYfKpHonPPQTsihuS7q6yJsAOFMovbNQuU1o5sMZsyNxkTCA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=cI8tj5uwo4o0dmVfxSPUAaAKkE0=; b=DSuXn6YDRrNpPsyIB8fuUbh8vVbB nMktALdI0oc8+/rQ/6G8wjE3xtWvNFPFAAyMNxEBXxB16/E+0tUAeSU/bCg57het wPsg9nPz50BVSWlbyN2FqhQVqzlm/w04I7O+oajEnqX6WFqZDUglRd2QIyD1JAGg 8+BK7QPl6m+0aQI= Received: by web3.nyi.internal (Postfix, from userid 99) id 3B7B01150E6; Tue, 9 Sep 2014 08:02:50 -0400 (EDT) Message-Id: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> X-Sasl-Enc: tPCQTxK41NdLE6+CqcQPCy5iEGIcYGg0hDVhGeT4Y2Dq 1410264170 From: Magnus Skjegstad To: mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-f82de2e6 Date: Tue, 09 Sep 2014 14:02:50 +0200 Subject: [MirageOS-devel] Just-In-Time Summoning of Unikernels X-BeenThere: mirageos-devel@lists.xenproject.org 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 have written a small forwarding DNS server that starts virtual machines on demand, which may be of interest to this list. The server is called Jitsu - or Just-In-Time Summoning of Unikernels. Before forwarding a DNS query, Jitsu checks if the requested domain matches a known unikernel. If it does, the unikernel is started and its IP is returned to the client. Jitsu continues to respond with the IP of the unikernel for as long as it is running. If no requests have been received for the domain within a timeout the unikernel is automatically stopped. The code is available here: https://github.com/MagnusS/jitsu Jitsu has been tested with Mirage VMs on a Cubietruck w/Xen and libvirt. For installing libvirt with Xen-support I recommend following Nick's instructions: http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00178.html. The code is proof-of-concept at this point, so there is probably plenty of room for optimizations. Contributions are welcome. Magnus _______________________________________________ MirageOS-devel 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 Sep 09 12:02:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 12:02:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRK8L-0006MR-IP; Tue, 09 Sep 2014 12:02:53 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRK8K-0006MM-Me for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 12:02:53 +0000 Received: from [193.109.254.147:14967] by server-8.bemta-14.messagelabs.com id 1D/D3-01875-C6CEE045; Tue, 09 Sep 2014 12:02:52 +0000 X-Env-Sender: magnus@v0.no X-Msg-Ref: server-14.tower-27.messagelabs.com!1410264170!14404076!1 X-Originating-IP: [66.111.4.28] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19563 invoked from network); 9 Sep 2014 12:02:51 -0000 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2014 12:02:51 -0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by gateway2.nyi.internal (Postfix) with ESMTP id 5872620DBE for ; Tue, 9 Sep 2014 08:02:50 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute1.internal (MEProxy); Tue, 09 Sep 2014 08:02:50 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=v0.no; h= message-id:from:to:cc:mime-version:content-transfer-encoding :content-type:subject:date; s=mesmtp; bh=cI8tj5uwo4o0dmVfxSPUAaA KkE0=; b=d58t1dqIitIV0Zvtoryc60UF2meB6M5xxoYzkpBRsh5jMC0KGrFaJ1I okfeLV1ldaaaAvNFymoAJ1QaEedAgWbVJp5zwSidWIVFxsLchZtuhXonlX6G/BU1 6X19SYfKpHonPPQTsihuS7q6yJsAOFMovbNQuU1o5sMZsyNxkTCA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=cI8tj5uwo4o0dmVfxSPUAaAKkE0=; b=DSuXn6YDRrNpPsyIB8fuUbh8vVbB nMktALdI0oc8+/rQ/6G8wjE3xtWvNFPFAAyMNxEBXxB16/E+0tUAeSU/bCg57het wPsg9nPz50BVSWlbyN2FqhQVqzlm/w04I7O+oajEnqX6WFqZDUglRd2QIyD1JAGg 8+BK7QPl6m+0aQI= Received: by web3.nyi.internal (Postfix, from userid 99) id 3B7B01150E6; Tue, 9 Sep 2014 08:02:50 -0400 (EDT) Message-Id: <1410264170.174581.165363333.55F8570A@webmail.messagingengine.com> X-Sasl-Enc: tPCQTxK41NdLE6+CqcQPCy5iEGIcYGg0hDVhGeT4Y2Dq 1410264170 From: Magnus Skjegstad To: mirageos-devel@lists.xenproject.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-f82de2e6 Date: Tue, 09 Sep 2014 14:02:50 +0200 Subject: [MirageOS-devel] Just-In-Time Summoning of Unikernels X-BeenThere: mirageos-devel@lists.xenproject.org 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 have written a small forwarding DNS server that starts virtual machines on demand, which may be of interest to this list. The server is called Jitsu - or Just-In-Time Summoning of Unikernels. Before forwarding a DNS query, Jitsu checks if the requested domain matches a known unikernel. If it does, the unikernel is started and its IP is returned to the client. Jitsu continues to respond with the IP of the unikernel for as long as it is running. If no requests have been received for the domain within a timeout the unikernel is automatically stopped. The code is available here: https://github.com/MagnusS/jitsu Jitsu has been tested with Mirage VMs on a Cubietruck w/Xen and libvirt. For installing libvirt with Xen-support I recommend following Nick's instructions: http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00178.html. The code is proof-of-concept at this point, so there is probably plenty of room for optimizations. Contributions are welcome. Magnus _______________________________________________ MirageOS-devel 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 Sep 09 15:07:29 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:07:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN0u-0006a1-0U; Tue, 09 Sep 2014 15:07:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN0s-0006Zl-Mo for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:07:22 +0000 Received: from [85.158.143.35:12294] by server-3.bemta-4.messagelabs.com id DD/89-06192-AA71F045; Tue, 09 Sep 2014 15:07:22 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1410275239!12665108!1 X-Originating-IP: [209.85.220.46] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11358 invoked from network); 9 Sep 2014 15:07:20 -0000 Received: from mail-pa0-f46.google.com (HELO mail-pa0-f46.google.com) (209.85.220.46) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2014 15:07:20 -0000 Received: by mail-pa0-f46.google.com with SMTP id kq14so2582067pab.33 for ; Tue, 09 Sep 2014 08:07:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=35bwNw485fax3R3AoITknaRejN6vS11KGDX3o4Fxumc=; b=X/rYmEADMnUXjSBkwu6ZG9iFk0K9D+q4JXQRH8MrTj4Ndjd40kHGhSzgB8sCkMWs2/ LB+7mXV9wkEwOGaYjVUXlqX9h/rIpiEO7QZFfY4kRV8zo5sY3N2axkZX6QT4c0eYSGmb W1ohVAW5Km+QrDpSynWPxkJ0Md4/umYWWgR4yG0kES9gy1KyuI7iM45AW8OYgsonbGAf hp2Gy2Oq0S4OVf4eXz2tTKp9ysFL79jzTb/gOS4DLjvTbX92WMnEUuUJgWaEvh3NCF5p e+oCpcNZDN0igW1PR+t8YZSJX3C/2+KRlegwP4aHK/i6SAHsAeGL0gV+jg6HsE35XOfP syrA== MIME-Version: 1.0 X-Received: by 10.68.238.137 with SMTP id vk9mr6231891pbc.165.1410275238953; Tue, 09 Sep 2014 08:07:18 -0700 (PDT) Received: by 10.70.87.8 with HTTP; Tue, 9 Sep 2014 08:07:18 -0700 (PDT) In-Reply-To: <540E2C77.6050007@galois.com> References: <540E2C77.6050007@galois.com> Date: Tue, 9 Sep 2014 16:07:18 +0100 Message-ID: From: David Scott To: James Bielman Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5345017458648472821==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5345017458648472821== Content-Type: multipart/alternative; boundary=047d7b33cc18a748e50502a34a61 --047d7b33cc18a748e50502a34a61 Content-Type: text/plain; charset=UTF-8 Hi James, On Mon, Sep 8, 2014 at 11:23 PM, James Bielman wrote: > Hi all, > > I'm doing some investigation into what it will take to merge our XenStore > mandatory access control patches into the latest Mirage XenStore code > base. My plan is to first submit a proposed interface for security modules > to XenStore, pushing as much as possible into the external Flask module to > keep the patch size down. > > After some time looking at the Irmin-based Xenstore, I have a few > questions: > > - Is the repository at https://github.com/mirage/ocaml-xenstore-server > the one I should be tracking, or is there a development repository? > Yes, that's the latest one. Note it's not in a fully working state-- when integrating irmin I unhooked a bunch of stuff so that I could refactor the core more quickly. The following features are (temporarily) unhooked: - interdomain rings (unix domain socket still works) - ACLs - watches - Xen kernel build Now that the irmin core is working it's probably time to start re-adding these. If you had complete freedom, what would your ideal interface be? > - I've been unable to compile a standalone Xen kernel because "mirage-xen" > wants to install "xenstore" via OPAM, which conflicts with > "ocaml-xenstore-server". Should that be working? Do I need to update to > Mirage 2.x? > Ideally I'd like to remove the dependency between mirage-xen and xenstore-- it's currently needed by the suspend/resume code but it complicates the build of the Xen xenstore kernel. The current version of irmin depends on core_kernel, which we need to make sure will work in a Xen environment -- there may be a stray C binding needed. For the moment I've been testing via the unix domain socket and had been planning to recreate the kernel version later. Does this work for you? > - I see some code that appears to support mounting virtual trees of some > sort (in server/mount.ml), but it doesn't seem to be used currently? One > feature I need to do this integration is a virtual "/label" tree for > reading/writing nodes security labels. What is the best way to implement a > virtual subtree like this currently? > Ah yeah, that's been unhooked too. I need to hook it back in. Would your tree be entirely virtual or would you want to write-through to irmin beneath? > - Likewise, I see code doing DAC checks in some modules, but those modules > don't appear to be included in the build. Am I missing something or is the > current version not performing access checks? Perhaps because the > interdomain transport isn't being used? That's right -- it's certainly not in a production-ready state! The irmin bits are working quite nicely though :-) Cheers, -- Dave Scott --047d7b33cc18a748e50502a34a61 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi James,

On Mon, Sep 8, 2014 at 11:23 PM, James Bielman &= lt;jamesjb@galois.c= om> wrote:
Hi all,

I'm doing some investigation into what it will take to merge our XenSto= re mandatory access control patches into the latest Mirage XenStore code ba= se.=C2=A0 My plan is to first submit a proposed interface for security modu= les to XenStore, pushing as much as possible into the external Flask module= to keep the patch size down.

After some time looking at the Irmin-based Xenstore, I have a few questions= :

- Is the repository at https://github.com/mirage/ocaml-xenstore-s= erver the one I should be tracking, or is there a development repositor= y?

Yes, that's the latest one. Note= it's not in a fully working state-- when integrating irmin I unhooked = a bunch of stuff so that I could refactor the core more quickly. The follow= ing features are (temporarily) unhooked:

- interdo= main rings (unix domain socket still works)
- ACLs
- wa= tches
- Xen kernel build

Now that the ir= min core is working it's probably time to start re-adding these.
<= div>
If you had complete freedom, what would your ideal inter= face be?
=C2=A0
- I've been unable to compile a standalone Xen kernel because "mir= age-xen" wants to install "xenstore" via OPAM, which conflic= ts with "ocaml-xenstore-server".=C2=A0 Should that be working?=C2= =A0 Do I need to update to Mirage 2.x?

= Ideally I'd like to remove the dependency between mirage-xen and xensto= re-- it's currently needed by the suspend/resume code but it complicate= s the build of the Xen xenstore kernel.

The curren= t version of irmin depends on core_kernel, which we need to make sure will = work in a Xen environment -- there may be a stray C binding needed.

For the moment I've been testing via the unix domain = socket and had been planning to recreate the kernel version later. Does thi= s work for you?
=C2=A0
- I see some code that appears to support mounting virtual trees of some so= rt (in server/mount.ml), = but it doesn't seem to be used currently?=C2=A0 One feature I need to d= o this integration is a virtual "/label" tree for reading/writing= nodes security labels.=C2=A0 What is the best way to implement a virtual s= ubtree like this currently?

Ah yeah, th= at's been unhooked too. I need to hook it back in. Would your tree be e= ntirely virtual or would you want to write-through to irmin beneath?
<= div>=C2=A0
- Likewise, I see code doing DAC checks in some modules, but those modules = don't appear to be included in the build.=C2=A0 Am I missing something = or is the current version not performing access checks? Perhaps because the= interdomain transport isn't being used?

That's right -- it's certainly not in a production-ready state! T= he irmin bits are working quite nicely though :-)

= Cheers,
--
Dave Scott
--047d7b33cc18a748e50502a34a61-- --===============5345017458648472821== 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 --===============5345017458648472821==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 15:07:29 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:07:29 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN0u-0006a1-0U; Tue, 09 Sep 2014 15:07:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN0s-0006Zl-Mo for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:07:22 +0000 Received: from [85.158.143.35:12294] by server-3.bemta-4.messagelabs.com id DD/89-06192-AA71F045; Tue, 09 Sep 2014 15:07:22 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-12.tower-21.messagelabs.com!1410275239!12665108!1 X-Originating-IP: [209.85.220.46] X-SpamReason: No, hits=0.9 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11358 invoked from network); 9 Sep 2014 15:07:20 -0000 Received: from mail-pa0-f46.google.com (HELO mail-pa0-f46.google.com) (209.85.220.46) by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2014 15:07:20 -0000 Received: by mail-pa0-f46.google.com with SMTP id kq14so2582067pab.33 for ; Tue, 09 Sep 2014 08:07:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=35bwNw485fax3R3AoITknaRejN6vS11KGDX3o4Fxumc=; b=X/rYmEADMnUXjSBkwu6ZG9iFk0K9D+q4JXQRH8MrTj4Ndjd40kHGhSzgB8sCkMWs2/ LB+7mXV9wkEwOGaYjVUXlqX9h/rIpiEO7QZFfY4kRV8zo5sY3N2axkZX6QT4c0eYSGmb W1ohVAW5Km+QrDpSynWPxkJ0Md4/umYWWgR4yG0kES9gy1KyuI7iM45AW8OYgsonbGAf hp2Gy2Oq0S4OVf4eXz2tTKp9ysFL79jzTb/gOS4DLjvTbX92WMnEUuUJgWaEvh3NCF5p e+oCpcNZDN0igW1PR+t8YZSJX3C/2+KRlegwP4aHK/i6SAHsAeGL0gV+jg6HsE35XOfP syrA== MIME-Version: 1.0 X-Received: by 10.68.238.137 with SMTP id vk9mr6231891pbc.165.1410275238953; Tue, 09 Sep 2014 08:07:18 -0700 (PDT) Received: by 10.70.87.8 with HTTP; Tue, 9 Sep 2014 08:07:18 -0700 (PDT) In-Reply-To: <540E2C77.6050007@galois.com> References: <540E2C77.6050007@galois.com> Date: Tue, 9 Sep 2014 16:07:18 +0100 Message-ID: From: David Scott To: James Bielman Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5345017458648472821==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5345017458648472821== Content-Type: multipart/alternative; boundary=047d7b33cc18a748e50502a34a61 --047d7b33cc18a748e50502a34a61 Content-Type: text/plain; charset=UTF-8 Hi James, On Mon, Sep 8, 2014 at 11:23 PM, James Bielman wrote: > Hi all, > > I'm doing some investigation into what it will take to merge our XenStore > mandatory access control patches into the latest Mirage XenStore code > base. My plan is to first submit a proposed interface for security modules > to XenStore, pushing as much as possible into the external Flask module to > keep the patch size down. > > After some time looking at the Irmin-based Xenstore, I have a few > questions: > > - Is the repository at https://github.com/mirage/ocaml-xenstore-server > the one I should be tracking, or is there a development repository? > Yes, that's the latest one. Note it's not in a fully working state-- when integrating irmin I unhooked a bunch of stuff so that I could refactor the core more quickly. The following features are (temporarily) unhooked: - interdomain rings (unix domain socket still works) - ACLs - watches - Xen kernel build Now that the irmin core is working it's probably time to start re-adding these. If you had complete freedom, what would your ideal interface be? > - I've been unable to compile a standalone Xen kernel because "mirage-xen" > wants to install "xenstore" via OPAM, which conflicts with > "ocaml-xenstore-server". Should that be working? Do I need to update to > Mirage 2.x? > Ideally I'd like to remove the dependency between mirage-xen and xenstore-- it's currently needed by the suspend/resume code but it complicates the build of the Xen xenstore kernel. The current version of irmin depends on core_kernel, which we need to make sure will work in a Xen environment -- there may be a stray C binding needed. For the moment I've been testing via the unix domain socket and had been planning to recreate the kernel version later. Does this work for you? > - I see some code that appears to support mounting virtual trees of some > sort (in server/mount.ml), but it doesn't seem to be used currently? One > feature I need to do this integration is a virtual "/label" tree for > reading/writing nodes security labels. What is the best way to implement a > virtual subtree like this currently? > Ah yeah, that's been unhooked too. I need to hook it back in. Would your tree be entirely virtual or would you want to write-through to irmin beneath? > - Likewise, I see code doing DAC checks in some modules, but those modules > don't appear to be included in the build. Am I missing something or is the > current version not performing access checks? Perhaps because the > interdomain transport isn't being used? That's right -- it's certainly not in a production-ready state! The irmin bits are working quite nicely though :-) Cheers, -- Dave Scott --047d7b33cc18a748e50502a34a61 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi James,

On Mon, Sep 8, 2014 at 11:23 PM, James Bielman &= lt;jamesjb@galois.c= om> wrote:
Hi all,

I'm doing some investigation into what it will take to merge our XenSto= re mandatory access control patches into the latest Mirage XenStore code ba= se.=C2=A0 My plan is to first submit a proposed interface for security modu= les to XenStore, pushing as much as possible into the external Flask module= to keep the patch size down.

After some time looking at the Irmin-based Xenstore, I have a few questions= :

- Is the repository at https://github.com/mirage/ocaml-xenstore-s= erver the one I should be tracking, or is there a development repositor= y?

Yes, that's the latest one. Note= it's not in a fully working state-- when integrating irmin I unhooked = a bunch of stuff so that I could refactor the core more quickly. The follow= ing features are (temporarily) unhooked:

- interdo= main rings (unix domain socket still works)
- ACLs
- wa= tches
- Xen kernel build

Now that the ir= min core is working it's probably time to start re-adding these.
<= div>
If you had complete freedom, what would your ideal inter= face be?
=C2=A0
- I've been unable to compile a standalone Xen kernel because "mir= age-xen" wants to install "xenstore" via OPAM, which conflic= ts with "ocaml-xenstore-server".=C2=A0 Should that be working?=C2= =A0 Do I need to update to Mirage 2.x?

= Ideally I'd like to remove the dependency between mirage-xen and xensto= re-- it's currently needed by the suspend/resume code but it complicate= s the build of the Xen xenstore kernel.

The curren= t version of irmin depends on core_kernel, which we need to make sure will = work in a Xen environment -- there may be a stray C binding needed.

For the moment I've been testing via the unix domain = socket and had been planning to recreate the kernel version later. Does thi= s work for you?
=C2=A0
- I see some code that appears to support mounting virtual trees of some so= rt (in server/mount.ml), = but it doesn't seem to be used currently?=C2=A0 One feature I need to d= o this integration is a virtual "/label" tree for reading/writing= nodes security labels.=C2=A0 What is the best way to implement a virtual s= ubtree like this currently?

Ah yeah, th= at's been unhooked too. I need to hook it back in. Would your tree be e= ntirely virtual or would you want to write-through to irmin beneath?
<= div>=C2=A0
- Likewise, I see code doing DAC checks in some modules, but those modules = don't appear to be included in the build.=C2=A0 Am I missing something = or is the current version not performing access checks? Perhaps because the= interdomain transport isn't being used?

That's right -- it's certainly not in a production-ready state! T= he irmin bits are working quite nicely though :-)

= Cheers,
--
Dave Scott
--047d7b33cc18a748e50502a34a61-- --===============5345017458648472821== 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 --===============5345017458648472821==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 15:10:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:10:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN3u-0006nV-RK; Tue, 09 Sep 2014 15:10:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN3u-0006nL-3Z for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:10:30 +0000 Received: from [85.158.143.35:41436] by server-3.bemta-4.messagelabs.com id 7E/4F-06192-5681F045; Tue, 09 Sep 2014 15:10:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1410275428!12337351!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9535 invoked from network); 9 Sep 2014 15:10:28 -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; 9 Sep 2014 15:10:28 -0000 Received: (qmail 5577 invoked by uid 634); 9 Sep 2014 15:10: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.109]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 09 Sep 2014 16:10:28 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 9 Sep 2014 16:10:27 +0100 Message-Id: <41C3937D-9DEB-4ABD-A27F-B97C21B1703D@recoil.org> References: <540E2C77.6050007@galois.com> To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5273238500893328552==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5273238500893328552== Content-Type: multipart/alternative; boundary="Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7" --Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 9 Sep 2014, at 16:07, David Scott wrote: > The current version of irmin depends on core_kernel, which we need to = make sure will work in a Xen environment -- there may be a stray C = binding needed. Thomas Gazagnaire has been working on removing this dependency from = Irmin. It won't affect the external interface, which is already = Core-independent. -anil --Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 9 = Sep 2014, at 16:07, David Scott <scott.dj@gmail.com> = wrote:

The = current version of irmin depends on core_kernel, which we need to make = sure will work in a Xen environment -- there may be a stray C binding = needed.

Thomas Gazagnaire has been = working on removing this dependency from Irmin.  It won't affect = the external interface, which is already = Core-independent.

-anil

= --Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7-- --===============5273238500893328552== 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 --===============5273238500893328552==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 15:10:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:10:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN3u-0006nV-RK; Tue, 09 Sep 2014 15:10:30 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRN3u-0006nL-3Z for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:10:30 +0000 Received: from [85.158.143.35:41436] by server-3.bemta-4.messagelabs.com id 7E/4F-06192-5681F045; Tue, 09 Sep 2014 15:10:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-21.messagelabs.com!1410275428!12337351!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9535 invoked from network); 9 Sep 2014 15:10:28 -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; 9 Sep 2014 15:10:28 -0000 Received: (qmail 5577 invoked by uid 634); 9 Sep 2014 15:10: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.109]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 09 Sep 2014 16:10:28 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 9 Sep 2014 16:10:27 +0100 Message-Id: <41C3937D-9DEB-4ABD-A27F-B97C21B1703D@recoil.org> References: <540E2C77.6050007@galois.com> To: David Scott X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5273238500893328552==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5273238500893328552== Content-Type: multipart/alternative; boundary="Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7" --Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 9 Sep 2014, at 16:07, David Scott wrote: > The current version of irmin depends on core_kernel, which we need to = make sure will work in a Xen environment -- there may be a stray C = binding needed. Thomas Gazagnaire has been working on removing this dependency from = Irmin. It won't affect the external interface, which is already = Core-independent. -anil --Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 9 = Sep 2014, at 16:07, David Scott <scott.dj@gmail.com> = wrote:

The = current version of irmin depends on core_kernel, which we need to make = sure will work in a Xen environment -- there may be a stray C binding = needed.

Thomas Gazagnaire has been = working on removing this dependency from Irmin.  It won't affect = the external interface, which is already = Core-independent.

-anil

= --Apple-Mail=_E4FBF92E-A335-43DD-96AC-C8631EF95FE7-- --===============5273238500893328552== 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 --===============5273238500893328552==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 15:29:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:29:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNMR-0007cI-0O; Tue, 09 Sep 2014 15:29:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNMP-0007cD-JW for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:29:37 +0000 Received: from [85.158.137.68:49455] by server-17.bemta-3.messagelabs.com id 28/25-01689-0EC1F045; Tue, 09 Sep 2014 15:29:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1410276575!12772410!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11349 invoked from network); 9 Sep 2014 15:29:36 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2014 15:29:36 -0000 Received: by mail-wi0-f171.google.com with SMTP id hi2so4692597wib.4 for ; Tue, 09 Sep 2014 08:29:33 -0700 (PDT) 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=e9H2OTsNugrk1OMUDyE2/lKiko0P16zCIzaNNY9EkmM=; b=IxN4qahDwISelz6noQAgDcR3B7Z5g4RZh2b0HzywBMSFnlXCKk6fJwEFP53hRCR8kX Hd0maxzMSYn5mPX5KMAoVFqq4+rybC8YdemzSsB4oxNteshW9x724hV0xECGIHaB2q5r bCEuDIONARY+Ewy+k+jPfXG8TxlJDmw8Ty4idsm7mESFtvWZ73wdJHpuRN1DJDVVb+C0 Lz+AUCy5Aa6hkphuThOkY4DXxwh1+DxJLYmLeYUozro0F3dCTUsJo/ZjKd6FUR2QP31f fU60tY0JPP1nMYB0Dz4TjSByM2GL6OmJt3GavMyqGhjJtQvXVLTqYmK3A6dZcJkCDT3u D5qw== X-Received: by 10.180.73.6 with SMTP id h6mr30685105wiv.65.1410276573660; Tue, 09 Sep 2014 08:29:33 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id y5sm15282829wje.32.2014.09.09.08.29.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Sep 2014 08:29:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <41C3937D-9DEB-4ABD-A27F-B97C21B1703D@recoil.org> Date: Tue, 9 Sep 2014 16:29:31 +0100 Message-Id: References: <540E2C77.6050007@galois.com> <41C3937D-9DEB-4ABD-A27F-B97C21B1703D@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8605032460717033851==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8605032460717033851== Content-Type: multipart/alternative; boundary="Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA" --Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii >> The current version of irmin depends on core_kernel, which we need to = make sure will work in a Xen environment -- there may be a stray C = binding needed. >=20 > Thomas Gazagnaire has been working on removing this dependency from = Irmin. It won't affect the external interface, which is already = Core-independent. Indeed, I hope to release something in the next few days. My top = priority currently is to make Irmin works nicely on Xen. Thomas --Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
The = current version of irmin depends on core_kernel, which we need to make = sure will work in a Xen environment -- there may be a stray C binding = needed.

Thomas Gazagnaire has been = working on removing this dependency from Irmin.  It won't affect = the external interface, which is already = Core-independent.

Indeed, I hope = to release something in the next few days. My top priority currently is = to make Irmin works nicely on = Xen.

Thomas

= --Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA-- --===============8605032460717033851== 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 --===============8605032460717033851==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 15:29:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:29:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNMR-0007cI-0O; Tue, 09 Sep 2014 15:29:39 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNMP-0007cD-JW for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:29:37 +0000 Received: from [85.158.137.68:49455] by server-17.bemta-3.messagelabs.com id 28/25-01689-0EC1F045; Tue, 09 Sep 2014 15:29:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1410276575!12772410!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11349 invoked from network); 9 Sep 2014 15:29:36 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2014 15:29:36 -0000 Received: by mail-wi0-f171.google.com with SMTP id hi2so4692597wib.4 for ; Tue, 09 Sep 2014 08:29:33 -0700 (PDT) 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=e9H2OTsNugrk1OMUDyE2/lKiko0P16zCIzaNNY9EkmM=; b=IxN4qahDwISelz6noQAgDcR3B7Z5g4RZh2b0HzywBMSFnlXCKk6fJwEFP53hRCR8kX Hd0maxzMSYn5mPX5KMAoVFqq4+rybC8YdemzSsB4oxNteshW9x724hV0xECGIHaB2q5r bCEuDIONARY+Ewy+k+jPfXG8TxlJDmw8Ty4idsm7mESFtvWZ73wdJHpuRN1DJDVVb+C0 Lz+AUCy5Aa6hkphuThOkY4DXxwh1+DxJLYmLeYUozro0F3dCTUsJo/ZjKd6FUR2QP31f fU60tY0JPP1nMYB0Dz4TjSByM2GL6OmJt3GavMyqGhjJtQvXVLTqYmK3A6dZcJkCDT3u D5qw== X-Received: by 10.180.73.6 with SMTP id h6mr30685105wiv.65.1410276573660; Tue, 09 Sep 2014 08:29:33 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id y5sm15282829wje.32.2014.09.09.08.29.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Sep 2014 08:29:32 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <41C3937D-9DEB-4ABD-A27F-B97C21B1703D@recoil.org> Date: Tue, 9 Sep 2014 16:29:31 +0100 Message-Id: References: <540E2C77.6050007@galois.com> <41C3937D-9DEB-4ABD-A27F-B97C21B1703D@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8605032460717033851==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8605032460717033851== Content-Type: multipart/alternative; boundary="Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA" --Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii >> The current version of irmin depends on core_kernel, which we need to = make sure will work in a Xen environment -- there may be a stray C = binding needed. >=20 > Thomas Gazagnaire has been working on removing this dependency from = Irmin. It won't affect the external interface, which is already = Core-independent. Indeed, I hope to release something in the next few days. My top = priority currently is to make Irmin works nicely on Xen. Thomas --Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
The = current version of irmin depends on core_kernel, which we need to make = sure will work in a Xen environment -- there may be a stray C binding = needed.

Thomas Gazagnaire has been = working on removing this dependency from Irmin.  It won't affect = the external interface, which is already = Core-independent.

Indeed, I hope = to release something in the next few days. My top priority currently is = to make Irmin works nicely on = Xen.

Thomas

= --Apple-Mail=_E6281582-D98D-4798-909A-3E2EEC4604BA-- --===============8605032460717033851== 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 --===============8605032460717033851==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 15:57:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:57:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNnh-0000sd-BF; Tue, 09 Sep 2014 15:57:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNnf-0000sY-AV for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:57:47 +0000 Received: from [85.158.137.68:49518] by server-11.bemta-3.messagelabs.com id FA/2E-01568-A732F045; Tue, 09 Sep 2014 15:57:46 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1410278265!13391759!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20785 invoked from network); 9 Sep 2014 15:57:45 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2014 15:57:45 -0000 Received: by mail-wg0-f42.google.com with SMTP id x12so4831735wgg.13 for ; Tue, 09 Sep 2014 08:57:45 -0700 (PDT) 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=jcYvx28BWNJ2mol5KrrFQW687JSEtfvNajG5QC0KgFE=; b=pmmRjRc3opivaxZBRaOCqr/EWQwCL2RVRKPv9HN28UvHIJ+UVDLu0CSr8aVMFQ1Wxc 2s1yKl3niEUJJrEMMi9QTVELBU5qXkFk7NTonSd+R6ZOT4JILeglyyqMapbpUawzG0RJ sJMtb9sn7FOOgU2RzAaLB5cH6DrK/uuVNk0SHmtfc6AxpWAZzWGJjkB81ZxzfOhePXYP bMQOyt37RjGUrnv941aKmgscO44d1DvgBvwv+JhL7iHxHm/1Lx9dVUdftx6rELIgKQDG 4CI/4nNj/2yCz4fETyKSEAaMN48fYrLLfVo+kiYhk9bzs2xUGomwSDv2H6OEhI8sP780 REBw== X-Received: by 10.180.87.161 with SMTP id az1mr31372625wib.13.1410278265230; Tue, 09 Sep 2014 08:57:45 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id xn15sm16050930wib.13.2014.09.09.08.57.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Sep 2014 08:57:44 -0700 (PDT) From: Thomas Gazagnaire Message-Id: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> Date: Tue, 9 Sep 2014 16:57:43 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, Lots of people starting asked me about the status of Irmin. As you might have notice, I'vent had much time to spend on Irmin last month, but I plan to fix that. My current priorities are: 1/ make Irmin compiles on the Xen backend of Mirage. https://github.com/mirage/irmin/issues/81 This means dropping the dependency to core_kernel (for now on). The external API will not change. 2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80 Currently, we only have a JSON API for the low-level stores, and the very partial implementation of the higher-level calls. Needs to complete and document that. 3/ implement a pure-ocaml Git server to be able to at least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15 Together with 1/ this will make possible to query the state of a running Mirage unikernel with a simple `git pull ` 4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82 Could use Benjamin's rope implementation, that I first need to release properly. 5/ try to come up with a solution to the "unlimited" memory/storage usage issues https://github.com/mirage/irmin/issues/83 This is the most uncertain part of the short-term roadmap. I'll need to check again what are the limitation of Git shallow copies and see how we can use them to limit the history size to remember. There are also few open embarrassing bugs that I want to fix as well (regarding fd leaks ...). If anyone is interested to help me on any of these topics, please feel free to comment on the related issues on Github -- I'll gladly share the workload. Also, feel free to reply to that email if you think there is any important Imrin features that you think are missing now. Best, 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 Sep 09 15:57:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 15:57:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNnh-0000sd-BF; Tue, 09 Sep 2014 15:57:49 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRNnf-0000sY-AV for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 15:57:47 +0000 Received: from [85.158.137.68:49518] by server-11.bemta-3.messagelabs.com id FA/2E-01568-A732F045; Tue, 09 Sep 2014 15:57:46 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1410278265!13391759!1 X-Originating-IP: [74.125.82.42] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20785 invoked from network); 9 Sep 2014 15:57:45 -0000 Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com) (74.125.82.42) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 9 Sep 2014 15:57:45 -0000 Received: by mail-wg0-f42.google.com with SMTP id x12so4831735wgg.13 for ; Tue, 09 Sep 2014 08:57:45 -0700 (PDT) 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=jcYvx28BWNJ2mol5KrrFQW687JSEtfvNajG5QC0KgFE=; b=pmmRjRc3opivaxZBRaOCqr/EWQwCL2RVRKPv9HN28UvHIJ+UVDLu0CSr8aVMFQ1Wxc 2s1yKl3niEUJJrEMMi9QTVELBU5qXkFk7NTonSd+R6ZOT4JILeglyyqMapbpUawzG0RJ sJMtb9sn7FOOgU2RzAaLB5cH6DrK/uuVNk0SHmtfc6AxpWAZzWGJjkB81ZxzfOhePXYP bMQOyt37RjGUrnv941aKmgscO44d1DvgBvwv+JhL7iHxHm/1Lx9dVUdftx6rELIgKQDG 4CI/4nNj/2yCz4fETyKSEAaMN48fYrLLfVo+kiYhk9bzs2xUGomwSDv2H6OEhI8sP780 REBw== X-Received: by 10.180.87.161 with SMTP id az1mr31372625wib.13.1410278265230; Tue, 09 Sep 2014 08:57:45 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id xn15sm16050930wib.13.2014.09.09.08.57.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Sep 2014 08:57:44 -0700 (PDT) From: Thomas Gazagnaire Message-Id: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> Date: Tue, 9 Sep 2014 16:57:43 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, Lots of people starting asked me about the status of Irmin. As you might have notice, I'vent had much time to spend on Irmin last month, but I plan to fix that. My current priorities are: 1/ make Irmin compiles on the Xen backend of Mirage. https://github.com/mirage/irmin/issues/81 This means dropping the dependency to core_kernel (for now on). The external API will not change. 2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80 Currently, we only have a JSON API for the low-level stores, and the very partial implementation of the higher-level calls. Needs to complete and document that. 3/ implement a pure-ocaml Git server to be able to at least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15 Together with 1/ this will make possible to query the state of a running Mirage unikernel with a simple `git pull ` 4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82 Could use Benjamin's rope implementation, that I first need to release properly. 5/ try to come up with a solution to the "unlimited" memory/storage usage issues https://github.com/mirage/irmin/issues/83 This is the most uncertain part of the short-term roadmap. I'll need to check again what are the limitation of Git shallow copies and see how we can use them to limit the history size to remember. There are also few open embarrassing bugs that I want to fix as well (regarding fd leaks ...). If anyone is interested to help me on any of these topics, please feel free to comment on the related issues on Github -- I'll gladly share the workload. Also, feel free to reply to that email if you think there is any important Imrin features that you think are missing now. Best, 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 Sep 09 17:05:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 17:05: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 1XROqy-0007e6-3y; Tue, 09 Sep 2014 17:05:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XROqv-0007dx-OA for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 17:05:13 +0000 Received: from [85.158.139.211:41058] by server-4.bemta-5.messagelabs.com id D3/4F-10551-8433F045; Tue, 09 Sep 2014 17:05:12 +0000 X-Env-Sender: jamesjb@galois.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1410282310!9312862!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16349 invoked from network); 9 Sep 2014 17:05:12 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2014 17:05:12 -0000 Received: from hurricane.galois.com (hurricane.galois.com [IPv6:2001:4870:e08e:200:5054:ff:fefa:ce41]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id s89H54UN015930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 9 Sep 2014 10:05:08 -0700 Received: from [IPv6:2001:4870:e08e:201:5c19:3915:d07a:599f] ([IPv6:2001:4870:e08e:201:5c19:3915:d07a:599f]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id s89H54TG023840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 9 Sep 2014 10:05:04 -0700 Message-ID: <540F3340.2060400@galois.com> Date: Tue, 09 Sep 2014 10:05:04 -0700 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: David Scott References: <540E2C77.6050007@galois.com> In-Reply-To: X-Spam-Status: No, score=-3.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list 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 Dave, On 09/09/2014 08:07 AM, David Scott wrote: > Hi James, > > Yes, that's the latest one. Note it's not in a fully working state-- > when integrating irmin I unhooked a bunch of stuff so that I could > refactor the core more quickly. The following features are > (temporarily) unhooked: > > - interdomain rings (unix domain socket still works) > - ACLs > - watches > - Xen kernel build > > Now that the irmin core is working it's probably time to start > re-adding these. > > If you had complete freedom, what would your ideal interface be? I'm doing a quick update of the security interface away from a "record-of-functions" approach to a proper OCaml module type (leading to another module parameter to Server.Make for the security module). Once I have something that looks good I'll send a pull request and hopefully we can come up with an interface that works well on both sides. My thinking is that I will backport this interface to our current code based on the older XenStore tree and we will continue to use that internally. Having the interface available in the newer tree going forward should hopefully let us switch to the newer version when it is ready without too much pain. > > - I've been unable to compile a standalone Xen kernel because > "mirage-xen" wants to install "xenstore" via OPAM, which conflicts > with "ocaml-xenstore-server". Should that be working? Do I need > to update to Mirage 2.x? > > > Ideally I'd like to remove the dependency between mirage-xen and > xenstore-- it's currently needed by the suspend/resume code but it > complicates the build of the Xen xenstore kernel. Indeed, this has been a problem for us too. A similar issue we ran into is the assumption that a console is available in Mirage. I have some patches floating around for a dummy console that I should get into shape for submitting (IMO ideally there'd be a way to fall back to the hypervisor console for domains like XenStore that may be started before the console is ready). > For the moment I've been testing via the unix domain socket and had > been planning to recreate the kernel version later. Does this work for > you? Yes, I think this is fine for getting the basic interface tested. I'm inclined to postpone adding all the calls to security hooks on each access check until the DAC checks are in place, though. It'd be nice to come up with a framework for doing the DAC checks and calling the security module in a unified way. Since the DAC checks are likely a subset of the checks we're doing for MAC, we may be able to implement DAC using the security module interface and come up with a way to compose them. > - I see some code that appears to support mounting virtual trees > of some sort (in server/mount.ml ), but it > doesn't seem to be used currently? One feature I need to do this > integration is a virtual "/label" tree for reading/writing nodes > security labels. What is the best way to implement a virtual > subtree like this currently? > > > Ah yeah, that's been unhooked too. I need to hook it back in. Would > your tree be entirely virtual or would you want to write-through to > irmin beneath? Hmm, I'm not actually sure yet on this one. In the in-memory case, its simple because we know if MAC is enabled before we create any nodes, so everything is always labeled anew each time we start XenStore. If there is a situation where we could persist the XenStore tree without MAC then reload it with MAC enabled then we'd probably need to implement relabelling. Right now there's an assumption that the tree is created fresh each boot so it never has to be relabelled. Our case is a little unusual in that we want to expose the security label of /local/domain/1/name as a virtual path: /label/local/domain/1/name So we'll definitely need access to the underlying node. To be conservative, I think we'd probably want to assume we need to write security labels along with node values to the underlying storage, but I'll need to think through the relabelling issue. Thanks! James _______________________________________________ MirageOS-devel 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 Sep 09 17:05:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 17:05: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 1XROqy-0007e6-3y; Tue, 09 Sep 2014 17:05:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XROqv-0007dx-OA for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 17:05:13 +0000 Received: from [85.158.139.211:41058] by server-4.bemta-5.messagelabs.com id D3/4F-10551-8433F045; Tue, 09 Sep 2014 17:05:12 +0000 X-Env-Sender: jamesjb@galois.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1410282310!9312862!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16349 invoked from network); 9 Sep 2014 17:05:12 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2014 17:05:12 -0000 Received: from hurricane.galois.com (hurricane.galois.com [IPv6:2001:4870:e08e:200:5054:ff:fefa:ce41]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id s89H54UN015930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 9 Sep 2014 10:05:08 -0700 Received: from [IPv6:2001:4870:e08e:201:5c19:3915:d07a:599f] ([IPv6:2001:4870:e08e:201:5c19:3915:d07a:599f]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id s89H54TG023840 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 9 Sep 2014 10:05:04 -0700 Message-ID: <540F3340.2060400@galois.com> Date: Tue, 09 Sep 2014 10:05:04 -0700 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: David Scott References: <540E2C77.6050007@galois.com> In-Reply-To: X-Spam-Status: No, score=-3.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list 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 Dave, On 09/09/2014 08:07 AM, David Scott wrote: > Hi James, > > Yes, that's the latest one. Note it's not in a fully working state-- > when integrating irmin I unhooked a bunch of stuff so that I could > refactor the core more quickly. The following features are > (temporarily) unhooked: > > - interdomain rings (unix domain socket still works) > - ACLs > - watches > - Xen kernel build > > Now that the irmin core is working it's probably time to start > re-adding these. > > If you had complete freedom, what would your ideal interface be? I'm doing a quick update of the security interface away from a "record-of-functions" approach to a proper OCaml module type (leading to another module parameter to Server.Make for the security module). Once I have something that looks good I'll send a pull request and hopefully we can come up with an interface that works well on both sides. My thinking is that I will backport this interface to our current code based on the older XenStore tree and we will continue to use that internally. Having the interface available in the newer tree going forward should hopefully let us switch to the newer version when it is ready without too much pain. > > - I've been unable to compile a standalone Xen kernel because > "mirage-xen" wants to install "xenstore" via OPAM, which conflicts > with "ocaml-xenstore-server". Should that be working? Do I need > to update to Mirage 2.x? > > > Ideally I'd like to remove the dependency between mirage-xen and > xenstore-- it's currently needed by the suspend/resume code but it > complicates the build of the Xen xenstore kernel. Indeed, this has been a problem for us too. A similar issue we ran into is the assumption that a console is available in Mirage. I have some patches floating around for a dummy console that I should get into shape for submitting (IMO ideally there'd be a way to fall back to the hypervisor console for domains like XenStore that may be started before the console is ready). > For the moment I've been testing via the unix domain socket and had > been planning to recreate the kernel version later. Does this work for > you? Yes, I think this is fine for getting the basic interface tested. I'm inclined to postpone adding all the calls to security hooks on each access check until the DAC checks are in place, though. It'd be nice to come up with a framework for doing the DAC checks and calling the security module in a unified way. Since the DAC checks are likely a subset of the checks we're doing for MAC, we may be able to implement DAC using the security module interface and come up with a way to compose them. > - I see some code that appears to support mounting virtual trees > of some sort (in server/mount.ml ), but it > doesn't seem to be used currently? One feature I need to do this > integration is a virtual "/label" tree for reading/writing nodes > security labels. What is the best way to implement a virtual > subtree like this currently? > > > Ah yeah, that's been unhooked too. I need to hook it back in. Would > your tree be entirely virtual or would you want to write-through to > irmin beneath? Hmm, I'm not actually sure yet on this one. In the in-memory case, its simple because we know if MAC is enabled before we create any nodes, so everything is always labeled anew each time we start XenStore. If there is a situation where we could persist the XenStore tree without MAC then reload it with MAC enabled then we'd probably need to implement relabelling. Right now there's an assumption that the tree is created fresh each boot so it never has to be relabelled. Our case is a little unusual in that we want to expose the security label of /local/domain/1/name as a virtual path: /label/local/domain/1/name So we'll definitely need access to the underlying node. To be conservative, I think we'd probably want to assume we need to write security labels along with node values to the underlying storage, but I'll need to think through the relabelling issue. Thanks! James _______________________________________________ MirageOS-devel 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 Sep 09 18:09:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 18:09:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRPr4-0002pi-4X; Tue, 09 Sep 2014 18:09:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRPr3-0002ow-Ex for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 18:09:25 +0000 Received: from [193.109.254.147:54166] by server-16.bemta-14.messagelabs.com id 08/03-16990-4524F045; Tue, 09 Sep 2014 18:09:24 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1410286162!14466853!1 X-Originating-IP: [98.138.229.31] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30857 invoked from network); 9 Sep 2014 18:09:23 -0000 Received: from nm38.bullet.mail.ne1.yahoo.com (HELO nm38.bullet.mail.ne1.yahoo.com) (98.138.229.31) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2014 18:09:23 -0000 Received: from [127.0.0.1] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 09 Sep 2014 18:09:22 -0000 Received: from [98.138.101.130] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 Received: from [98.139.215.140] by tm18.bullet.mail.ne1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 Received: from [98.139.212.213] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 Received: from [127.0.0.1] by omp1022.mail.bf1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 51471.96919.bm@omp1022.mail.bf1.yahoo.com Received: (qmail 64292 invoked by uid 60001); 9 Sep 2014 18:06:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410285992; bh=xBwmnt0zP51YB176tQ1K47GBUfmeClLiLdC3hEpVekU=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=sZjZ1vIQpJw1N/towrfZHsjxIx5golcI9jEmTL7eO7In39mDSRbPOX1meqOghAqLzyzApwwnjIV+hyIbM224kKS74LaAevkRxhXKOHZwxnyTwYDE9/0rg1+tqJ7SUEJJO2P0WKg66s18vLsMp4k/+ea7SGvv/28Til43mOUOr4M= X-YMail-OSG: i3o5LBYVM1k7B.geHfwwFkeKSTrj9NPjkfN78am_Q4DH.Yw 6QYXG6bPr5YyJtr8UZKWz4ExrEgriyBKKJpr_MYCUd9bR2YFHyi2Khyjm89S JMe3caOtt_1IxQlgvO6GucMeM.xz7zNLNgqww2_Bj8TyncybfWt2KZlDee.L CsjL3VuZGsbMM054g6JOVHUix9i_8ul2y8EysMQJ.fmBXsuZxGgRNkWvcPOG x5045ddSZaot74TPtUbb.pbP7O2QyF5zAAFssrqU6Ona8e6lwvQlvwiFkATi 3iz9Ode.fY7B1Lu6eeJpObpR5TUeDKJqA94QRO.7tccIdOO0EzZEHiS2hYdm MDC9DbE1czGR7c5_5E2M6aeRwy.t0J6jgdnFmdPmUwZJD9LSeS6b3rx7wRAD EZ4aa4zOCIw1E7u8weghj9FKBoR42dIvSBXo3DrfDJPj7SSCl9rTEBJ8zMQN KqqM4hXfUC2X16ObWINSxnPSRKzS2zSc7Gqm2GKe_yeaU57yW1ttTRESTakG FXZhW6wp.Q_Ke Received: from [217.12.199.209] by web142402.mail.bf1.yahoo.com via HTTP; Tue, 09 Sep 2014 11:06:31 PDT X-Rocket-MIMEInfo: 002.001, SGVsbG8gZ3V5cywKCldoZW4gSSBjb21waWxlIG15IG1pcmFnZSBhcHBsaWNhdGlvbiBmb3IgeGVuLCB0aGUgZm9sbG93aW5nIGVycm9yIGhhcHBlbnM6CgpGaWxlICJfbm9uZV8iLCBsaW5lIDE6CkVycm9yOiBObyBpbXBsZW1lbnRhdGlvbnMgcHJvdmlkZWQgZm9yIHRoZSBmb2xsb3dpbmcgbW9kdWxlczoKICAgICAgICAgVW5peExhYmVscyByZWZlcmVuY2VkIGZyb20gL2hvbWUvdXNlci8ub3BhbS9zeXN0ZW0vbGliL2NvcmUvY29yZS5jbXhhKENvcmUpCiAgICAgICAgIFVuaXggcmVmZXJlbmNlZCBmcm9tIC8BMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 Message-ID: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> Date: Tue, 9 Sep 2014 11:06:31 -0700 From: Ania Skorupa To: "mirageos-devel@lists.xenproject.org" MIME-Version: 1.0 Subject: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0203295463538417731==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0203295463538417731== Content-Type: multipart/alternative; boundary="-1115942004-1726543740-1410285991=:50936" ---1115942004-1726543740-1410285991=:50936 Content-Type: text/plain; charset=us-ascii Hello guys, When I compile my mirage application for xen, the following error happens: File "_none_", line 1: Error: No implementations provided for the following modules: UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core) Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), /home/user/.opam/system/lib/core/core.cmxa(Core) Command exited with code 2. Am I using libraries that can not be used to for xen unikernel? ---1115942004-1726543740-1410285991=:50936 Content-Type: text/html; charset=us-ascii
Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


---1115942004-1726543740-1410285991=:50936-- --===============0203295463538417731== 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 --===============0203295463538417731==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 18:09:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 18:09:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRPr4-0002pi-4X; Tue, 09 Sep 2014 18:09:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRPr3-0002ow-Ex for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 18:09:25 +0000 Received: from [193.109.254.147:54166] by server-16.bemta-14.messagelabs.com id 08/03-16990-4524F045; Tue, 09 Sep 2014 18:09:24 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1410286162!14466853!1 X-Originating-IP: [98.138.229.31] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30857 invoked from network); 9 Sep 2014 18:09:23 -0000 Received: from nm38.bullet.mail.ne1.yahoo.com (HELO nm38.bullet.mail.ne1.yahoo.com) (98.138.229.31) by server-8.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2014 18:09:23 -0000 Received: from [127.0.0.1] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 09 Sep 2014 18:09:22 -0000 Received: from [98.138.101.130] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 Received: from [98.139.215.140] by tm18.bullet.mail.ne1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 Received: from [98.139.212.213] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 Received: from [127.0.0.1] by omp1022.mail.bf1.yahoo.com with NNFMP; 09 Sep 2014 18:06:32 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 51471.96919.bm@omp1022.mail.bf1.yahoo.com Received: (qmail 64292 invoked by uid 60001); 9 Sep 2014 18:06:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410285992; bh=xBwmnt0zP51YB176tQ1K47GBUfmeClLiLdC3hEpVekU=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=sZjZ1vIQpJw1N/towrfZHsjxIx5golcI9jEmTL7eO7In39mDSRbPOX1meqOghAqLzyzApwwnjIV+hyIbM224kKS74LaAevkRxhXKOHZwxnyTwYDE9/0rg1+tqJ7SUEJJO2P0WKg66s18vLsMp4k/+ea7SGvv/28Til43mOUOr4M= X-YMail-OSG: i3o5LBYVM1k7B.geHfwwFkeKSTrj9NPjkfN78am_Q4DH.Yw 6QYXG6bPr5YyJtr8UZKWz4ExrEgriyBKKJpr_MYCUd9bR2YFHyi2Khyjm89S JMe3caOtt_1IxQlgvO6GucMeM.xz7zNLNgqww2_Bj8TyncybfWt2KZlDee.L CsjL3VuZGsbMM054g6JOVHUix9i_8ul2y8EysMQJ.fmBXsuZxGgRNkWvcPOG x5045ddSZaot74TPtUbb.pbP7O2QyF5zAAFssrqU6Ona8e6lwvQlvwiFkATi 3iz9Ode.fY7B1Lu6eeJpObpR5TUeDKJqA94QRO.7tccIdOO0EzZEHiS2hYdm MDC9DbE1czGR7c5_5E2M6aeRwy.t0J6jgdnFmdPmUwZJD9LSeS6b3rx7wRAD EZ4aa4zOCIw1E7u8weghj9FKBoR42dIvSBXo3DrfDJPj7SSCl9rTEBJ8zMQN KqqM4hXfUC2X16ObWINSxnPSRKzS2zSc7Gqm2GKe_yeaU57yW1ttTRESTakG FXZhW6wp.Q_Ke Received: from [217.12.199.209] by web142402.mail.bf1.yahoo.com via HTTP; Tue, 09 Sep 2014 11:06:31 PDT X-Rocket-MIMEInfo: 002.001, SGVsbG8gZ3V5cywKCldoZW4gSSBjb21waWxlIG15IG1pcmFnZSBhcHBsaWNhdGlvbiBmb3IgeGVuLCB0aGUgZm9sbG93aW5nIGVycm9yIGhhcHBlbnM6CgpGaWxlICJfbm9uZV8iLCBsaW5lIDE6CkVycm9yOiBObyBpbXBsZW1lbnRhdGlvbnMgcHJvdmlkZWQgZm9yIHRoZSBmb2xsb3dpbmcgbW9kdWxlczoKICAgICAgICAgVW5peExhYmVscyByZWZlcmVuY2VkIGZyb20gL2hvbWUvdXNlci8ub3BhbS9zeXN0ZW0vbGliL2NvcmUvY29yZS5jbXhhKENvcmUpCiAgICAgICAgIFVuaXggcmVmZXJlbmNlZCBmcm9tIC8BMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 Message-ID: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> Date: Tue, 9 Sep 2014 11:06:31 -0700 From: Ania Skorupa To: "mirageos-devel@lists.xenproject.org" MIME-Version: 1.0 Subject: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0203295463538417731==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0203295463538417731== Content-Type: multipart/alternative; boundary="-1115942004-1726543740-1410285991=:50936" ---1115942004-1726543740-1410285991=:50936 Content-Type: text/plain; charset=us-ascii Hello guys, When I compile my mirage application for xen, the following error happens: File "_none_", line 1: Error: No implementations provided for the following modules: UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core) Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), /home/user/.opam/system/lib/core/core.cmxa(Core) Command exited with code 2. Am I using libraries that can not be used to for xen unikernel? ---1115942004-1726543740-1410285991=:50936 Content-Type: text/html; charset=us-ascii
Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


---1115942004-1726543740-1410285991=:50936-- --===============0203295463538417731== 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 --===============0203295463538417731==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 18:33:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 18:33: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 1XRQDr-0004Vs-KI; Tue, 09 Sep 2014 18:32:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRQDq-0004Vg-N5 for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 18:32:58 +0000 Received: from [85.158.139.211:13107] by server-9.bemta-5.messagelabs.com id E4/FF-20744-AD74F045; Tue, 09 Sep 2014 18:32:58 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-4.tower-206.messagelabs.com!1410287577!13465123!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4441 invoked from network); 9 Sep 2014 18:32:57 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-4.tower-206.messagelabs.com with SMTP; 9 Sep 2014 18:32:57 -0000 Received: (qmail 16200 invoked from network); 9 Sep 2014 18:32:56 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 9 Sep 2014 18:32:56 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15802-09 for ; Tue, 9 Sep 2014 19:32:49 +0100 (BST) Received: (qmail 15770 invoked by uid 599); 9 Sep 2014 18:32:14 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 09 Sep 2014 19:32:14 +0100 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 1XRQD8-0000eD-QO; Tue, 09 Sep 2014 19:32:14 +0100 From: Richard Mortier To: Ania Skorupa Date: Tue, 9 Sep 2014 19:32:15 +0100 Thread-Topic: [MirageOS-devel] Compile mirage application for xen Thread-Index: Ac/MXGBkctYWmhdGSwutd/B/A280OA== Message-ID: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> In-Reply-To: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5112716637607233304==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5112716637607233304== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_" --_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGksDQoNCkknZCBndWVzcyBzbywgeWVzLiAgQW55dGhpbmcgdGhhdCBkZXBlbmRzIG9uIHRoZSB1 bmRlcmx5aW5nIHBsYXRmb3JtIChVbml4KSBuZWVkcyB0byBiZSBhYnN0cmFjdGVkIHRvIHdvcmsg d2l0aCBtaXJhZ2UuDQoNClNwZWNpZmljYWxseSwgYWxsIHRob3NlIG1vZHVsZXMgaW4gdGhlIGVy cm9yIG1lc3NhZ2UgaGF2ZSB1bml4IGRlcGVuZGVuY2llcyB0aGF0IGFyZW4ndCBiZWluZyBzYXRp c2ZpZWQsIHRob3VnaCBJIGJlbGlldmUgd29yayBpcyBvbmdvaW5nIHRvIHNwbGl0IGpzIGNvcmUg dXAgdG8gaGF2ZSBhIGtlcm5lbCBwYXJ0IHRoYXQgd2lsbCBiZSBtb3JlIGNvbXBhdGlibGUgd2l0 aCBoZSBtaXJhZ2UgYXBwcm9hY2guDQoNCldoYXQgYXJlIHlvdSB0cnlpbmcgdG8gZG8/IEl0IG1p Z2h0IGJlIHRoYXQgdGhlcmUgYXJlIGFsdGVybmF0aXZlIG1pcmFnZSBjb21wYXRpYmxlIGxpYnJh cmllcyBhbHJlYWR5IGF2YWlsYWJsZSAodGhvdWdoIHRoYXQgbWlnaHQgbm90IGhlbHAgbXVjaCBp ZiB5b3UncmUgbG9va2luZyBhdCBwb3J0aW5nIGEgbGFyZ2UgY29kZWJhc2Ugb2YgY291cnNlIDop DQoNCi0tDQpDaGVlcnMsDQoNClIuDQoNCg0KDQpPbiA5IFNlcCAyMDE0LCBhdCAxOToxMywgIkFu aWEgU2tvcnVwYSIgPGFuaWEuc2tvcnVwYUB5YWhvby5jb208bWFpbHRvOmFuaWEuc2tvcnVwYUB5 YWhvby5jb20+PiB3cm90ZToNCg0KSGVsbG8gZ3V5cywNCg0KV2hlbiBJIGNvbXBpbGUgbXkgbWly YWdlIGFwcGxpY2F0aW9uIGZvciB4ZW4sIHRoZSBmb2xsb3dpbmcgZXJyb3IgaGFwcGVuczoNCg0K RmlsZSAiX25vbmVfIiwgbGluZSAxOg0KRXJyb3I6IE5vIGltcGxlbWVudGF0aW9ucyBwcm92aWRl ZCBmb3IgdGhlIGZvbGxvd2luZyBtb2R1bGVzOg0KICAgICAgICAgVW5peExhYmVscyByZWZlcmVu Y2VkIGZyb20gL2hvbWUvdXNlci8ub3BhbS9zeXN0ZW0vbGliL2NvcmUvY29yZS5jbXhhKENvcmUp DQogICAgICAgICBVbml4IHJlZmVyZW5jZWQgZnJvbSAvdXNyL2xpYi9vY2FtbC90aHJlYWRzL3Ro cmVhZHMuY214YShUaHJlYWQpLA0KICAgICAgICAgICAvaG9tZS91c2VyLy5vcGFtL3N5c3RlbS9s aWIvY29yZV9rZXJuZWwvY29yZV9rZXJuZWwuY214YShDb3JlX2tlcm5lbCksDQogICAgICAgICAg IC9ob21lL3VzZXIvLm9wYW0vc3lzdGVtL2xpYi9zZXhwbGliX3VuaXgvc2V4cGxpYl91bml4LmNt eGEoU2V4cGxpYl91bml4KSwNCiAgICAgICAgICAgL2hvbWUvdXNlci8ub3BhbS9zeXN0ZW0vbGli L2NvcmUvY29yZS5jbXhhKENvcmUpDQpDb21tYW5kIGV4aXRlZCB3aXRoIGNvZGUgMi4NCg0KQW0g SSB1c2luZyBsaWJyYXJpZXMgdGhhdCBjYW4gbm90IGJlIHVzZWQgdG8gZm9yIHhlbiB1bmlrZXJu ZWw/DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Ck1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdA0KTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJv amVjdC5vcmc8bWFpbHRvOk1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnPg0KaHR0 cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vv cy1kZXZlbA0K --_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+SGksPC9k aXY+PGRpdj48YnI+PC9kaXY+PGRpdj5JJ2QgZ3Vlc3Mgc28sIHllcy4gJm5ic3A7QW55dGhpbmcg dGhhdCBkZXBlbmRzIG9uIHRoZSB1bmRlcmx5aW5nIHBsYXRmb3JtIChVbml4KSBuZWVkcyB0byBi ZSBhYnN0cmFjdGVkIHRvIHdvcmsgd2l0aCBtaXJhZ2UuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRp dj5TcGVjaWZpY2FsbHksIGFsbCB0aG9zZSBtb2R1bGVzIGluIHRoZSBlcnJvciBtZXNzYWdlIGhh dmUgdW5peCBkZXBlbmRlbmNpZXMgdGhhdCBhcmVuJ3QgYmVpbmcgc2F0aXNmaWVkLCB0aG91Z2gg SSBiZWxpZXZlIHdvcmsgaXMgb25nb2luZyB0byBzcGxpdCBqcyBjb3JlIHVwIHRvIGhhdmUgYSBr ZXJuZWwgcGFydCB0aGF0IHdpbGwgYmUgbW9yZSBjb21wYXRpYmxlIHdpdGggaGUgbWlyYWdlIGFw cHJvYWNoLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+V2hhdCBhcmUgeW91IHRyeWluZyB0byBk bz8gSXQgbWlnaHQgYmUgdGhhdCB0aGVyZSBhcmUgYWx0ZXJuYXRpdmUgbWlyYWdlIGNvbXBhdGli bGUgbGlicmFyaWVzIGFscmVhZHkgYXZhaWxhYmxlICh0aG91Z2ggdGhhdCBtaWdodCBub3QgaGVs cCBtdWNoIGlmIHlvdSdyZSBsb29raW5nIGF0IHBvcnRpbmcgYSBsYXJnZSBjb2RlYmFzZSBvZiBj b3Vyc2UgOik8YnI+PGJyPi0tICZuYnNwOzxkaXY+Q2hlZXJzLDwvZGl2PjxkaXY+PGJyPjwvZGl2 PjxkaXY+Ui48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48L2Rpdj48ZGl2Pjxi cj5PbiA5IFNlcCAyMDE0LCBhdCAxOToxMywgIkFuaWEgU2tvcnVwYSIgJmx0OzxhIGhyZWY9Im1h aWx0bzphbmlhLnNrb3J1cGFAeWFob28uY29tIj5hbmlhLnNrb3J1cGFAeWFob28uY29tPC9hPiZn dDsgd3JvdGU6PGJyPjxicj48L2Rpdj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2PjxkaXYg c3R5bGU9ImNvbG9yOiMwMDA7IGJhY2tncm91bmQtY29sb3I6I2ZmZjsgZm9udC1mYW1pbHk6SGVs dmV0aWNhTmV1ZSwgSGVsdmV0aWNhIE5ldWUsIEhlbHZldGljYSwgQXJpYWwsIEx1Y2lkYSBHcmFu ZGUsIHNhbnMtc2VyaWY7Zm9udC1zaXplOjEycHQiPjxkaXYgc3R5bGU9IiIgY2xhc3M9IiI+SGVs bG8gZ3V5cyw8YnIgc3R5bGU9IiI+DQo8YnIgc3R5bGU9IiIgY2xhc3M9IiI+DQpXaGVuIEkgY29t cGlsZSBteSBtaXJhZ2UgYXBwbGljYXRpb24gZm9yIHhlbiwgdGhlIGZvbGxvd2luZyBlcnJvciBo YXBwZW5zOjxiciBzdHlsZT0iIiBjbGFzcz0iIj4NCjxiciBzdHlsZT0iIiBjbGFzcz0iIj4NCkZp bGUgIl9ub25lXyIsIGxpbmUgMTo8YnIgc3R5bGU9IiIgY2xhc3M9IiI+DQpFcnJvcjogTm8gaW1w bGVtZW50YXRpb25zIHByb3ZpZGVkIGZvciB0aGUgZm9sbG93aW5nIG1vZHVsZXM6PGJyIHN0eWxl PSIiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7IFVuaXhMYWJlbHMgcmVmZXJlbmNlZCBmcm9tIC9ob21lL3VzZXIvLm9wYW0vc3lzdGVt L2xpYi9jb3JlL2NvcmUuY214YShDb3JlKTxiciBzdHlsZT0iIiBjbGFzcz0iIj4NCiZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBVbml4IHJlZmVyZW5jZWQg ZnJvbSAvdXNyL2xpYi9vY2FtbC90aHJlYWRzL3RocmVhZHMuY214YShUaHJlYWQpLDxiciBzdHls ZT0iIiBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyAvaG9tZS91c2VyLy5vcGFtL3N5c3RlbS9saWIvY29yZV9rZXJu ZWwvY29yZV9rZXJuZWwuY214YShDb3JlX2tlcm5lbCksPGJyIHN0eWxlPSIiIGNsYXNzPSIiPg0K Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7IC9ob21lL3VzZXIvLm9wYW0vc3lzdGVtL2xpYi9zZXhwbGliX3VuaXgvc2V4cGxpYl91bml4 LmNteGEoU2V4cGxpYl91bml4KSw8YnIgc3R5bGU9IiIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgL2hvbWUvdXNl ci8ub3BhbS9zeXN0ZW0vbGliL2NvcmUvY29yZS5jbXhhKENvcmUpPGJyIHN0eWxlPSIiIGNsYXNz PSIiPg0KQ29tbWFuZCBleGl0ZWQgd2l0aCBjb2RlIDIuPGJyIHN0eWxlPSIiIGNsYXNzPSIiPg0K PGJyIHN0eWxlPSIiIGNsYXNzPSIiPg0KQW0gSSB1c2luZyBsaWJyYXJpZXMgdGhhdCBjYW4gbm90 IGJlIHVzZWQgdG8gZm9yIHhlbiB1bmlrZXJuZWw/PC9kaXY+PGRpdiBzdHlsZT0iIiBjbGFzcz0i Ij48YnI+PC9kaXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx NnB4OyBmb250LWZhbWlseTogSGVsdmV0aWNhTmV1ZSxIZWx2ZXRpY2EgTmV1ZSxIZWx2ZXRpY2Es QXJpYWwsTHVjaWRhIEdyYW5kZSxzYW5zLXNlcmlmOyBiYWNrZ3JvdW5kLWNvbG9yOiB0cmFuc3Bh cmVudDsgZm9udC1zdHlsZTogbm9ybWFsOyIgY2xhc3M9IiI+PGJyIHN0eWxlPSIiIGNsYXNzPSIi PjwvZGl2PjwvZGl2PjwvZGl2PjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48 ZGl2PjxzcGFuPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f PC9zcGFuPjxicj48c3Bhbj5NaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3Q8L3NwYW4+PGJyPjxz cGFuPjxhIGhyZWY9Im1haWx0bzpNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZyI+ TWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmc8L2E+PC9zcGFuPjxicj48c3Bhbj48 YSBocmVmPSJodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL21pcmFnZW9zLWRldmVsIj5odHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsPC9hPjwvc3Bhbj48YnI+PC9kaXY+PC9ibG9j a3F1b3RlPjwvYm9keT48L2h0bWw+ --_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_-- --===============5112716637607233304== 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 --===============5112716637607233304==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 09 18:33:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 09 Sep 2014 18:33: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 1XRQDr-0004Vs-KI; Tue, 09 Sep 2014 18:32:59 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRQDq-0004Vg-N5 for mirageos-devel@lists.xenproject.org; Tue, 09 Sep 2014 18:32:58 +0000 Received: from [85.158.139.211:13107] by server-9.bemta-5.messagelabs.com id E4/FF-20744-AD74F045; Tue, 09 Sep 2014 18:32:58 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-4.tower-206.messagelabs.com!1410287577!13465123!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4441 invoked from network); 9 Sep 2014 18:32:57 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-4.tower-206.messagelabs.com with SMTP; 9 Sep 2014 18:32:57 -0000 Received: (qmail 16200 invoked from network); 9 Sep 2014 18:32:56 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 9 Sep 2014 18:32:56 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15802-09 for ; Tue, 9 Sep 2014 19:32:49 +0100 (BST) Received: (qmail 15770 invoked by uid 599); 9 Sep 2014 18:32:14 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 09 Sep 2014 19:32:14 +0100 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 1XRQD8-0000eD-QO; Tue, 09 Sep 2014 19:32:14 +0100 From: Richard Mortier To: Ania Skorupa Date: Tue, 9 Sep 2014 19:32:15 +0100 Thread-Topic: [MirageOS-devel] Compile mirage application for xen Thread-Index: Ac/MXGBkctYWmhdGSwutd/B/A280OA== Message-ID: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> In-Reply-To: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> Accept-Language: en-US, en-GB Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5112716637607233304==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5112716637607233304== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_" --_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGksDQoNCkknZCBndWVzcyBzbywgeWVzLiAgQW55dGhpbmcgdGhhdCBkZXBlbmRzIG9uIHRoZSB1 bmRlcmx5aW5nIHBsYXRmb3JtIChVbml4KSBuZWVkcyB0byBiZSBhYnN0cmFjdGVkIHRvIHdvcmsg d2l0aCBtaXJhZ2UuDQoNClNwZWNpZmljYWxseSwgYWxsIHRob3NlIG1vZHVsZXMgaW4gdGhlIGVy cm9yIG1lc3NhZ2UgaGF2ZSB1bml4IGRlcGVuZGVuY2llcyB0aGF0IGFyZW4ndCBiZWluZyBzYXRp c2ZpZWQsIHRob3VnaCBJIGJlbGlldmUgd29yayBpcyBvbmdvaW5nIHRvIHNwbGl0IGpzIGNvcmUg dXAgdG8gaGF2ZSBhIGtlcm5lbCBwYXJ0IHRoYXQgd2lsbCBiZSBtb3JlIGNvbXBhdGlibGUgd2l0 aCBoZSBtaXJhZ2UgYXBwcm9hY2guDQoNCldoYXQgYXJlIHlvdSB0cnlpbmcgdG8gZG8/IEl0IG1p Z2h0IGJlIHRoYXQgdGhlcmUgYXJlIGFsdGVybmF0aXZlIG1pcmFnZSBjb21wYXRpYmxlIGxpYnJh cmllcyBhbHJlYWR5IGF2YWlsYWJsZSAodGhvdWdoIHRoYXQgbWlnaHQgbm90IGhlbHAgbXVjaCBp ZiB5b3UncmUgbG9va2luZyBhdCBwb3J0aW5nIGEgbGFyZ2UgY29kZWJhc2Ugb2YgY291cnNlIDop DQoNCi0tDQpDaGVlcnMsDQoNClIuDQoNCg0KDQpPbiA5IFNlcCAyMDE0LCBhdCAxOToxMywgIkFu aWEgU2tvcnVwYSIgPGFuaWEuc2tvcnVwYUB5YWhvby5jb208bWFpbHRvOmFuaWEuc2tvcnVwYUB5 YWhvby5jb20+PiB3cm90ZToNCg0KSGVsbG8gZ3V5cywNCg0KV2hlbiBJIGNvbXBpbGUgbXkgbWly YWdlIGFwcGxpY2F0aW9uIGZvciB4ZW4sIHRoZSBmb2xsb3dpbmcgZXJyb3IgaGFwcGVuczoNCg0K RmlsZSAiX25vbmVfIiwgbGluZSAxOg0KRXJyb3I6IE5vIGltcGxlbWVudGF0aW9ucyBwcm92aWRl ZCBmb3IgdGhlIGZvbGxvd2luZyBtb2R1bGVzOg0KICAgICAgICAgVW5peExhYmVscyByZWZlcmVu Y2VkIGZyb20gL2hvbWUvdXNlci8ub3BhbS9zeXN0ZW0vbGliL2NvcmUvY29yZS5jbXhhKENvcmUp DQogICAgICAgICBVbml4IHJlZmVyZW5jZWQgZnJvbSAvdXNyL2xpYi9vY2FtbC90aHJlYWRzL3Ro cmVhZHMuY214YShUaHJlYWQpLA0KICAgICAgICAgICAvaG9tZS91c2VyLy5vcGFtL3N5c3RlbS9s aWIvY29yZV9rZXJuZWwvY29yZV9rZXJuZWwuY214YShDb3JlX2tlcm5lbCksDQogICAgICAgICAg IC9ob21lL3VzZXIvLm9wYW0vc3lzdGVtL2xpYi9zZXhwbGliX3VuaXgvc2V4cGxpYl91bml4LmNt eGEoU2V4cGxpYl91bml4KSwNCiAgICAgICAgICAgL2hvbWUvdXNlci8ub3BhbS9zeXN0ZW0vbGli L2NvcmUvY29yZS5jbXhhKENvcmUpDQpDb21tYW5kIGV4aXRlZCB3aXRoIGNvZGUgMi4NCg0KQW0g SSB1c2luZyBsaWJyYXJpZXMgdGhhdCBjYW4gbm90IGJlIHVzZWQgdG8gZm9yIHhlbiB1bmlrZXJu ZWw/DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Ck1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdA0KTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJv amVjdC5vcmc8bWFpbHRvOk1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnPg0KaHR0 cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vv cy1kZXZlbA0K --_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBkaXI9ImF1dG8iPjxkaXY+SGksPC9k aXY+PGRpdj48YnI+PC9kaXY+PGRpdj5JJ2QgZ3Vlc3Mgc28sIHllcy4gJm5ic3A7QW55dGhpbmcg dGhhdCBkZXBlbmRzIG9uIHRoZSB1bmRlcmx5aW5nIHBsYXRmb3JtIChVbml4KSBuZWVkcyB0byBi ZSBhYnN0cmFjdGVkIHRvIHdvcmsgd2l0aCBtaXJhZ2UuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRp dj5TcGVjaWZpY2FsbHksIGFsbCB0aG9zZSBtb2R1bGVzIGluIHRoZSBlcnJvciBtZXNzYWdlIGhh dmUgdW5peCBkZXBlbmRlbmNpZXMgdGhhdCBhcmVuJ3QgYmVpbmcgc2F0aXNmaWVkLCB0aG91Z2gg SSBiZWxpZXZlIHdvcmsgaXMgb25nb2luZyB0byBzcGxpdCBqcyBjb3JlIHVwIHRvIGhhdmUgYSBr ZXJuZWwgcGFydCB0aGF0IHdpbGwgYmUgbW9yZSBjb21wYXRpYmxlIHdpdGggaGUgbWlyYWdlIGFw cHJvYWNoLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+V2hhdCBhcmUgeW91IHRyeWluZyB0byBk bz8gSXQgbWlnaHQgYmUgdGhhdCB0aGVyZSBhcmUgYWx0ZXJuYXRpdmUgbWlyYWdlIGNvbXBhdGli bGUgbGlicmFyaWVzIGFscmVhZHkgYXZhaWxhYmxlICh0aG91Z2ggdGhhdCBtaWdodCBub3QgaGVs cCBtdWNoIGlmIHlvdSdyZSBsb29raW5nIGF0IHBvcnRpbmcgYSBsYXJnZSBjb2RlYmFzZSBvZiBj b3Vyc2UgOik8YnI+PGJyPi0tICZuYnNwOzxkaXY+Q2hlZXJzLDwvZGl2PjxkaXY+PGJyPjwvZGl2 PjxkaXY+Ui48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48L2Rpdj48ZGl2Pjxi cj5PbiA5IFNlcCAyMDE0LCBhdCAxOToxMywgIkFuaWEgU2tvcnVwYSIgJmx0OzxhIGhyZWY9Im1h aWx0bzphbmlhLnNrb3J1cGFAeWFob28uY29tIj5hbmlhLnNrb3J1cGFAeWFob28uY29tPC9hPiZn dDsgd3JvdGU6PGJyPjxicj48L2Rpdj48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48ZGl2PjxkaXYg c3R5bGU9ImNvbG9yOiMwMDA7IGJhY2tncm91bmQtY29sb3I6I2ZmZjsgZm9udC1mYW1pbHk6SGVs dmV0aWNhTmV1ZSwgSGVsdmV0aWNhIE5ldWUsIEhlbHZldGljYSwgQXJpYWwsIEx1Y2lkYSBHcmFu ZGUsIHNhbnMtc2VyaWY7Zm9udC1zaXplOjEycHQiPjxkaXYgc3R5bGU9IiIgY2xhc3M9IiI+SGVs bG8gZ3V5cyw8YnIgc3R5bGU9IiI+DQo8YnIgc3R5bGU9IiIgY2xhc3M9IiI+DQpXaGVuIEkgY29t cGlsZSBteSBtaXJhZ2UgYXBwbGljYXRpb24gZm9yIHhlbiwgdGhlIGZvbGxvd2luZyBlcnJvciBo YXBwZW5zOjxiciBzdHlsZT0iIiBjbGFzcz0iIj4NCjxiciBzdHlsZT0iIiBjbGFzcz0iIj4NCkZp bGUgIl9ub25lXyIsIGxpbmUgMTo8YnIgc3R5bGU9IiIgY2xhc3M9IiI+DQpFcnJvcjogTm8gaW1w bGVtZW50YXRpb25zIHByb3ZpZGVkIGZvciB0aGUgZm9sbG93aW5nIG1vZHVsZXM6PGJyIHN0eWxl PSIiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7IFVuaXhMYWJlbHMgcmVmZXJlbmNlZCBmcm9tIC9ob21lL3VzZXIvLm9wYW0vc3lzdGVt L2xpYi9jb3JlL2NvcmUuY214YShDb3JlKTxiciBzdHlsZT0iIiBjbGFzcz0iIj4NCiZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBVbml4IHJlZmVyZW5jZWQg ZnJvbSAvdXNyL2xpYi9vY2FtbC90aHJlYWRzL3RocmVhZHMuY214YShUaHJlYWQpLDxiciBzdHls ZT0iIiBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyAvaG9tZS91c2VyLy5vcGFtL3N5c3RlbS9saWIvY29yZV9rZXJu ZWwvY29yZV9rZXJuZWwuY214YShDb3JlX2tlcm5lbCksPGJyIHN0eWxlPSIiIGNsYXNzPSIiPg0K Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7IC9ob21lL3VzZXIvLm9wYW0vc3lzdGVtL2xpYi9zZXhwbGliX3VuaXgvc2V4cGxpYl91bml4 LmNteGEoU2V4cGxpYl91bml4KSw8YnIgc3R5bGU9IiIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgL2hvbWUvdXNl ci8ub3BhbS9zeXN0ZW0vbGliL2NvcmUvY29yZS5jbXhhKENvcmUpPGJyIHN0eWxlPSIiIGNsYXNz PSIiPg0KQ29tbWFuZCBleGl0ZWQgd2l0aCBjb2RlIDIuPGJyIHN0eWxlPSIiIGNsYXNzPSIiPg0K PGJyIHN0eWxlPSIiIGNsYXNzPSIiPg0KQW0gSSB1c2luZyBsaWJyYXJpZXMgdGhhdCBjYW4gbm90 IGJlIHVzZWQgdG8gZm9yIHhlbiB1bmlrZXJuZWw/PC9kaXY+PGRpdiBzdHlsZT0iIiBjbGFzcz0i Ij48YnI+PC9kaXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx NnB4OyBmb250LWZhbWlseTogSGVsdmV0aWNhTmV1ZSxIZWx2ZXRpY2EgTmV1ZSxIZWx2ZXRpY2Es QXJpYWwsTHVjaWRhIEdyYW5kZSxzYW5zLXNlcmlmOyBiYWNrZ3JvdW5kLWNvbG9yOiB0cmFuc3Bh cmVudDsgZm9udC1zdHlsZTogbm9ybWFsOyIgY2xhc3M9IiI+PGJyIHN0eWxlPSIiIGNsYXNzPSIi PjwvZGl2PjwvZGl2PjwvZGl2PjwvYmxvY2txdW90ZT48YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48 ZGl2PjxzcGFuPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f PC9zcGFuPjxicj48c3Bhbj5NaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3Q8L3NwYW4+PGJyPjxz cGFuPjxhIGhyZWY9Im1haWx0bzpNaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZyI+ TWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmc8L2E+PC9zcGFuPjxicj48c3Bhbj48 YSBocmVmPSJodHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL21pcmFnZW9zLWRldmVsIj5odHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9t YWlsbWFuL2xpc3RpbmZvL21pcmFnZW9zLWRldmVsPC9hPjwvc3Bhbj48YnI+PC9kaXY+PC9ibG9j a3F1b3RlPjwvYm9keT48L2h0bWw+ --_000_A8A1F2FF4C0C49FB89E0F25C4658D087UniofNottmmailonmicroso_-- --===============5112716637607233304== 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 --===============5112716637607233304==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 04:51:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 04:51: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 1XRZsi-00077A-TG; Wed, 10 Sep 2014 04:51:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRZsi-000775-6f for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 04:51:48 +0000 Received: from [85.158.143.35:8022] by server-3.bemta-4.messagelabs.com id 07/E5-06192-3E8DF045; Wed, 10 Sep 2014 04:51:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1410324706!12763123!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4294 invoked from network); 10 Sep 2014 04:51:46 -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; 10 Sep 2014 04:51:46 -0000 Received: (qmail 3349 invoked by uid 634); 10 Sep 2014 04:51:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 10 Sep 2014 05:51:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 10 Sep 2014 05:51:41 +0100 Message-Id: <00A8D626-F8B3-4928-A90A-68DC08533E04@recoil.org> References: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] rebuilding blobs.openmirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 14 Aug 2014, at 16:58, Anil Madhavapeddy wrote: > On 14 Aug 2014, at 16:25, Thomas Leonard wrote: > >> On 14 August 2014 16:11, Anil Madhavapeddy wrote: >>> Just an FYI: I'm rebuilding the blobs.openmirage.org to be an Ubuntu 14.04 Trusty VM with enough disk space that it can rebuild the mirage-xen-arm builder repository from scratch. This will let us automate the deployment of the ARM images as pull requests come in with feature changes. >> >> That's a relief - it was taking about an hour to upload the image each >> time (even with rsync)! > > I've completely failed to get `git clone` of Linux to work with a 512MB > VM and Docker as well -- keeps getting killed with an OOM signal even with > a lot of swap outside the container. These container<->resource usage > interactions are just weird... > > The new VM has 2vCPUs and a native cross-toolchain without containers, so > should be much easier! The blobs.openmirage.org VM is now rebuilding the xen-arm-builder images as they are pushed. It's serving using the latest Cohttp here; http://blobs.openmirage.org/ -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 Sep 10 04:51:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 04:51: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 1XRZsi-00077A-TG; Wed, 10 Sep 2014 04:51:48 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRZsi-000775-6f for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 04:51:48 +0000 Received: from [85.158.143.35:8022] by server-3.bemta-4.messagelabs.com id 07/E5-06192-3E8DF045; Wed, 10 Sep 2014 04:51:47 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-21.messagelabs.com!1410324706!12763123!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4294 invoked from network); 10 Sep 2014 04:51:46 -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; 10 Sep 2014 04:51:46 -0000 Received: (qmail 3349 invoked by uid 634); 10 Sep 2014 04:51:46 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 10 Sep 2014 05:51:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 10 Sep 2014 05:51:41 +0100 Message-Id: <00A8D626-F8B3-4928-A90A-68DC08533E04@recoil.org> References: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] rebuilding blobs.openmirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 14 Aug 2014, at 16:58, Anil Madhavapeddy wrote: > On 14 Aug 2014, at 16:25, Thomas Leonard wrote: > >> On 14 August 2014 16:11, Anil Madhavapeddy wrote: >>> Just an FYI: I'm rebuilding the blobs.openmirage.org to be an Ubuntu 14.04 Trusty VM with enough disk space that it can rebuild the mirage-xen-arm builder repository from scratch. This will let us automate the deployment of the ARM images as pull requests come in with feature changes. >> >> That's a relief - it was taking about an hour to upload the image each >> time (even with rsync)! > > I've completely failed to get `git clone` of Linux to work with a 512MB > VM and Docker as well -- keeps getting killed with an OOM signal even with > a lot of swap outside the container. These container<->resource usage > interactions are just weird... > > The new VM has 2vCPUs and a native cross-toolchain without containers, so > should be much easier! The blobs.openmirage.org VM is now rebuilding the xen-arm-builder images as they are pushed. It's serving using the latest Cohttp here; http://blobs.openmirage.org/ -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 Sep 10 08:46:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 08:46:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRdXf-0003AH-BX; Wed, 10 Sep 2014 08:46:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRdXd-0003AC-MZ for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 08:46:17 +0000 Received: from [85.158.143.35:34820] by server-3.bemta-4.messagelabs.com id 8E/42-06192-7DF00145; Wed, 10 Sep 2014 08:46:15 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1410338773!12759119!1 X-Originating-IP: [98.138.229.26] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6978 invoked from network); 10 Sep 2014 08:46:14 -0000 Received: from nm33.bullet.mail.ne1.yahoo.com (HELO nm33.bullet.mail.ne1.yahoo.com) (98.138.229.26) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2014 08:46:14 -0000 Received: from [127.0.0.1] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 08:46:12 -0000 Received: from [98.138.101.128] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 Received: from [98.139.215.141] by tm16.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 Received: from [98.139.212.211] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 Received: from [127.0.0.1] by omp1020.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 466320.8349.bm@omp1020.mail.bf1.yahoo.com Received: (qmail 11868 invoked by uid 60001); 10 Sep 2014 08:43:20 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410338600; bh=9PfEIMxnEhnxf2nDL6WqiSaZoTaf5taMaGXdUEUQXKM=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Dq16f7tmDfvyNz2YDyslkpkiVdlVuWxf+3GRa0nPwVJE71Od00YEXGtalFleYNEzIcsamCeNmzKu1RG7qPdvLrkdyOx2GVmKDP0aN/12XasHn7ps7Xzto4u/3or4BedZjuwDR4E7CMFr0g8FWRUcKuMGn3chPxtq7ZG6Jz2NoSA= X-YMail-OSG: hr42uhsVM1kGpJdAyZ087QTvP7nMjix9LbgFhDfaTxGLGgG 1u9m4qvtfrU7OzySY4ENhvZojE3YTvgOTSxpn15hXVe.3wxl4qc1bSemRRbS cGYRYUs1U7RtoeKZKss482m.EZr8sYKECQis7QN4VvHups8BiOZpWbzT8nuD 2UryCvNd6LmaWXdM9q_oU8kCbzLSaq0a2Dn.sIWrxn_8zbtcJq4ST9YMXhJy P.fFgH.Meewvp6DO6yzSCtGoECHUSg.J4OCyW8ZZoQLHs4bT2Q4CIhZIfiE5 iO.M4wqImBwj1BYrWu9p1jRYJu5HWKyj9XpjTEunpmXi7B59R71dEq0n9e4G 3q9vTNsh4PeqxtsQWlegY6unantQ_eybWSHRIcsP49yhOwTYFv2dqvvh25Ay n7VcJlBgAfmQQjM63ODglN_HIAh0D0KnldJQZL5_k8EmFPqNfNzXt.62QJnj aWg46DVEm1y8M5nUd0jNY2hFDF781YFgxfAkfnht.SctGirnvCMBsL.R4LYI J8RFbrnkVAR_tzKEcfMdI0E9I1iGZrwIkD4Puvg-- Received: from [95.130.15.97] by web142405.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 01:43:20 PDT X-Rocket-MIMEInfo: 002.001, CgpIaSwKCnRoYW5rcyBmb3IgeW91ciByZXBseSA6KSBJIGFtIHRyeWluZyB0byBidWlsZCBhIHBpZWNlIG9mIG9jYW1sIHByb2dyYW0gaW4gbWlyYWdlLCB3aGljaCBkb2Vzbid0IGhhdmUgYSB2ZXJ5IGxhcmdlIGNvZGViYXNlLiAKCgpmcm9tIGVycm9ycywgaXQgbG9va3MgdGhhdCAKY29yZSBpcyBvbmUgb2YgdGhlIGxpYnJhcmllcyB0aGF0IHJlc3VsdHMgaW4gdGhpcyBlcnJvci4gaW4gdGhlIGNvZGUsIEkgCmZvdW5kIHRoYXQgQ29yZS5TdGQgaXMgb3BlbmVkLiBJcyB0aGF0IGEgbGlicmFyeSB0aGF0IGMBMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> Message-ID: <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 01:43:20 -0700 From: Ania Skorupa To: Richard Mortier In-Reply-To: MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6274224086557463460==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6274224086557463460== Content-Type: multipart/alternative; boundary="-892791941-444040944-1410338600=:12980" ---892791941-444040944-1410338600=:12980 Content-Type: text/plain; charset=us-ascii Hi, thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies. On Tuesday, September 9, 2014 6:32 PM, Richard Mortier wrote: Hi, I'd guess so, yes. Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage. Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach. What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :) -- Cheers, R. On 9 Sep 2014, at 19:13, "Ania Skorupa" wrote: Hello guys, > >When I compile my mirage application for xen, the following error happens: > >File "_none_", line 1: >Error: No implementations provided for the following modules: > UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core) > Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), > /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), > /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), > /home/user/.opam/system/lib/core/core.cmxa(Core) >Command exited with code 2. > >Am I using libraries that can not be used to for xen unikernel? > > > > _______________________________________________ >MirageOS-devel mailing list >MirageOS-devel@lists.xenproject.org >http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ---892791941-444040944-1410338600=:12980 Content-Type: text/html; charset=us-ascii

Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase.

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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


---892791941-444040944-1410338600=:12980-- --===============6274224086557463460== 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 --===============6274224086557463460==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 08:46:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 08:46:23 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRdXf-0003AH-BX; Wed, 10 Sep 2014 08:46:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRdXd-0003AC-MZ for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 08:46:17 +0000 Received: from [85.158.143.35:34820] by server-3.bemta-4.messagelabs.com id 8E/42-06192-7DF00145; Wed, 10 Sep 2014 08:46:15 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1410338773!12759119!1 X-Originating-IP: [98.138.229.26] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6978 invoked from network); 10 Sep 2014 08:46:14 -0000 Received: from nm33.bullet.mail.ne1.yahoo.com (HELO nm33.bullet.mail.ne1.yahoo.com) (98.138.229.26) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2014 08:46:14 -0000 Received: from [127.0.0.1] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 08:46:12 -0000 Received: from [98.138.101.128] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 Received: from [98.139.215.141] by tm16.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 Received: from [98.139.212.211] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 Received: from [127.0.0.1] by omp1020.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 08:43:20 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 466320.8349.bm@omp1020.mail.bf1.yahoo.com Received: (qmail 11868 invoked by uid 60001); 10 Sep 2014 08:43:20 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410338600; bh=9PfEIMxnEhnxf2nDL6WqiSaZoTaf5taMaGXdUEUQXKM=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Dq16f7tmDfvyNz2YDyslkpkiVdlVuWxf+3GRa0nPwVJE71Od00YEXGtalFleYNEzIcsamCeNmzKu1RG7qPdvLrkdyOx2GVmKDP0aN/12XasHn7ps7Xzto4u/3or4BedZjuwDR4E7CMFr0g8FWRUcKuMGn3chPxtq7ZG6Jz2NoSA= X-YMail-OSG: hr42uhsVM1kGpJdAyZ087QTvP7nMjix9LbgFhDfaTxGLGgG 1u9m4qvtfrU7OzySY4ENhvZojE3YTvgOTSxpn15hXVe.3wxl4qc1bSemRRbS cGYRYUs1U7RtoeKZKss482m.EZr8sYKECQis7QN4VvHups8BiOZpWbzT8nuD 2UryCvNd6LmaWXdM9q_oU8kCbzLSaq0a2Dn.sIWrxn_8zbtcJq4ST9YMXhJy P.fFgH.Meewvp6DO6yzSCtGoECHUSg.J4OCyW8ZZoQLHs4bT2Q4CIhZIfiE5 iO.M4wqImBwj1BYrWu9p1jRYJu5HWKyj9XpjTEunpmXi7B59R71dEq0n9e4G 3q9vTNsh4PeqxtsQWlegY6unantQ_eybWSHRIcsP49yhOwTYFv2dqvvh25Ay n7VcJlBgAfmQQjM63ODglN_HIAh0D0KnldJQZL5_k8EmFPqNfNzXt.62QJnj aWg46DVEm1y8M5nUd0jNY2hFDF781YFgxfAkfnht.SctGirnvCMBsL.R4LYI J8RFbrnkVAR_tzKEcfMdI0E9I1iGZrwIkD4Puvg-- Received: from [95.130.15.97] by web142405.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 01:43:20 PDT X-Rocket-MIMEInfo: 002.001, CgpIaSwKCnRoYW5rcyBmb3IgeW91ciByZXBseSA6KSBJIGFtIHRyeWluZyB0byBidWlsZCBhIHBpZWNlIG9mIG9jYW1sIHByb2dyYW0gaW4gbWlyYWdlLCB3aGljaCBkb2Vzbid0IGhhdmUgYSB2ZXJ5IGxhcmdlIGNvZGViYXNlLiAKCgpmcm9tIGVycm9ycywgaXQgbG9va3MgdGhhdCAKY29yZSBpcyBvbmUgb2YgdGhlIGxpYnJhcmllcyB0aGF0IHJlc3VsdHMgaW4gdGhpcyBlcnJvci4gaW4gdGhlIGNvZGUsIEkgCmZvdW5kIHRoYXQgQ29yZS5TdGQgaXMgb3BlbmVkLiBJcyB0aGF0IGEgbGlicmFyeSB0aGF0IGMBMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> Message-ID: <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 01:43:20 -0700 From: Ania Skorupa To: Richard Mortier In-Reply-To: MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6274224086557463460==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6274224086557463460== Content-Type: multipart/alternative; boundary="-892791941-444040944-1410338600=:12980" ---892791941-444040944-1410338600=:12980 Content-Type: text/plain; charset=us-ascii Hi, thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies. On Tuesday, September 9, 2014 6:32 PM, Richard Mortier wrote: Hi, I'd guess so, yes. Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage. Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach. What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :) -- Cheers, R. On 9 Sep 2014, at 19:13, "Ania Skorupa" wrote: Hello guys, > >When I compile my mirage application for xen, the following error happens: > >File "_none_", line 1: >Error: No implementations provided for the following modules: > UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core) > Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), > /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), > /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), > /home/user/.opam/system/lib/core/core.cmxa(Core) >Command exited with code 2. > >Am I using libraries that can not be used to for xen unikernel? > > > > _______________________________________________ >MirageOS-devel mailing list >MirageOS-devel@lists.xenproject.org >http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ---892791941-444040944-1410338600=:12980 Content-Type: text/html; charset=us-ascii

Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase.

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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


---892791941-444040944-1410338600=:12980-- --===============6274224086557463460== 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 --===============6274224086557463460==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 09:07:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 09:07: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 1XRdrx-0004U8-Dn; Wed, 10 Sep 2014 09:07:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRdrw-0004U3-2N for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 09:07:16 +0000 Received: from [85.158.143.35:55632] by server-3.bemta-4.messagelabs.com id CD/82-06192-3C410145; Wed, 10 Sep 2014 09:07:15 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1410340034!4790559!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21724 invoked from network); 10 Sep 2014 09:07:14 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-2.tower-21.messagelabs.com with SMTP; 10 Sep 2014 09:07:14 -0000 Received: (qmail 23587 invoked from network); 10 Sep 2014 09:07:12 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 10 Sep 2014 09:07:12 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 19818-10 for ; Wed, 10 Sep 2014 10:07:05 +0100 (BST) Received: (qmail 17950 invoked by uid 599); 10 Sep 2014 09:05:32 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 10 Sep 2014 10:05:32 +0100 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 1XRdqS-00015C-40; Wed, 10 Sep 2014 10:05:44 +0100 From: Richard Mortier To: Ania Skorupa Date: Wed, 10 Sep 2014 10:05:41 +0100 Thread-Topic: [MirageOS-devel] Compile mirage application for xen Thread-Index: Ac/M1max4CdgrjiFTLyj9YjogJaW8w== Message-ID: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> In-Reply-To: <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5189499470447184158==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5189499470447184158== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28 Content-Type: multipart/alternative; boundary="Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277" --Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii unfortunately, aiui, core can't presently be used to build for xen -- as = i said, i think moves are afoot to fix this but it's a non-trivial thing = to do so i don't know what the timeline is (or even if that's explicitly = on the timeline). i don't know core well, but i know at least one issue = is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. others on the list are better placed to comment on if/when Core code = will be usable with Xen :) On 10 Sep 2014, at 09:43, Ania Skorupa wrote: >=20 > Hi, >=20 > thanks for your reply :) I am trying to build a piece of ocaml program = in mirage, which doesn't have a very large codebase.=20 >=20 > from errors, it looks that core is one of the libraries that results = in this error. in the code, I found that Core.Std is opened. Is that a = library that can not be used for xen? skimming through the code, I = didn't find explicit unix dependencies. >=20 >=20 >=20 > On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >=20 >=20 > Hi, >=20 > I'd guess so, yes. Anything that depends on the underlying platform = (Unix) needs to be abstracted to work with mirage. >=20 > Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >=20 > What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >=20 > -- =20 > Cheers, >=20 > R. >=20 >=20 >=20 > On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >=20 >> Hello guys, >>=20 >> When I compile my mirage application for xen, the following error = happens: >>=20 >> File "_none_", line 1: >> Error: No implementations provided for the following modules: >> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >> /home/user/.opam/system/lib/core/core.cmxa(Core) >> Command exited with code 2. >>=20 >> Am I using libraries that can not be used to for xen unikernel? >>=20 >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 --=20 Cheers, R. --Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii unfortunately, aiui, core can't presently be used to = build for xen -- as i said, i think moves are afoot to fix this but it's = a non-trivial thing to do so i don't know what the timeline is (or even = if that's explicitly on the timeline). i don't know core well, but i = know at least one issue is that the threading library (Core.Async) is = alike to but not completely compatible with = Lwt.

others on the list are better placed to comment = on if/when Core code will be usable with Xen :)

On = 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> = wrote:


Hi,

thanks for your reply :) I am = trying to build a piece of ocaml program in mirage, which doesn't have a = very large codebase.

from = errors, it looks that=20 core is one of the libraries that results in this error. in the code, I=20= found that Core.Std is opened. Is that a library that can not be used=20 for xen? skimming through the code, I didn't find explicit unix=20 dependencies.



= On Tuesday, = September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the = underlying platform (Unix) needs to be abstracted to work with = mirage.

Specifically, all those = modules in the error message have unix dependencies that aren't being = satisfied, though I believe work is ongoing to split js core up to have = a kernel part that will be more compatible with he mirage = approach.

What are you trying to = do? It might be that there are alternative mirage compatible libraries = already available (though that might not help much if you're looking at = porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> = wrote:

Hello guys,
=
When I compile my mirage application for xen, the following error = happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced = from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread),
           = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),<= br class=3D"" style=3D"" clear=3D"none">            = /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen = unikernel?


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


=


--
Cheers,
R.


= --Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277-- --Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUEBRlAAoJEOLF27JWwSg3RMEP/ixf0vUeoIRlKRUJ1UonvJvK e/eBtsz86DttJ8Ry/Yq3vw6+pbg5GPWT7rD50IjXEvu7IxipWre8TtnMEggcEh7I V/6J61G2BU5JKSHr8W+JoRVWocpnRv8QGapKGpqx1EGjE/jvsH1WopEf/H4ogeLL zcipZkwNK/LbmBvvj1kTiojGSE3IAoqhWAms4JwS7t0UYfO0rXhY2SaXoE2mG4ZG 9goSAMZNZHz5LyhngvRrxjnvOzNftkeU9lCKc8Az7njdCepcKMm4/sXXP4pijyz0 YYXUqd8n2Nj59wYWmVm4fcakLHQ2D4VWXnHdGd31GdHJ1zm3AUuw6n9pPy5Hjsv7 iMJda1jpn+ZXhR2PKmdiRCzKhawZ2zshK2RWRPCSwzL6DzSErLI3yg1aFo5D8VUu 8TO8VH3wYoAsHKlC8bFo1vp0Qa9hvjFBZKHb+IjDxB7Gf0f9JJWk++nTGNmYKTk/ PuMGGTT2aaBVDD7RIt2LjGGHJ2CAemqkZlbtdjbzFSeJGsn7RDlNqRWNocQZ/x9v a7A9B5A1N9pUncKFp+hpERfkekgeT3DE8GQ8Rs9iGlOqWi5sx+u+Dg/VvGTcbtOs qCnxThQcY3dqrnhe0a1sIIG8bP3ZFRDFlHUpbmcLKnfJqF8fOeUBT/S0m9cpTK34 S09/qv2LGKtp2GPOngwJ =OUzG -----END PGP SIGNATURE----- --Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28-- --===============5189499470447184158== 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 --===============5189499470447184158==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 09:07:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 09:07: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 1XRdrx-0004U8-Dn; Wed, 10 Sep 2014 09:07:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRdrw-0004U3-2N for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 09:07:16 +0000 Received: from [85.158.143.35:55632] by server-3.bemta-4.messagelabs.com id CD/82-06192-3C410145; Wed, 10 Sep 2014 09:07:15 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-21.messagelabs.com!1410340034!4790559!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21724 invoked from network); 10 Sep 2014 09:07:14 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-2.tower-21.messagelabs.com with SMTP; 10 Sep 2014 09:07:14 -0000 Received: (qmail 23587 invoked from network); 10 Sep 2014 09:07:12 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 10 Sep 2014 09:07:12 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 19818-10 for ; Wed, 10 Sep 2014 10:07:05 +0100 (BST) Received: (qmail 17950 invoked by uid 599); 10 Sep 2014 09:05:32 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Wed, 10 Sep 2014 10:05:32 +0100 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 1XRdqS-00015C-40; Wed, 10 Sep 2014 10:05:44 +0100 From: Richard Mortier To: Ania Skorupa Date: Wed, 10 Sep 2014 10:05:41 +0100 Thread-Topic: [MirageOS-devel] Compile mirage application for xen Thread-Index: Ac/M1max4CdgrjiFTLyj9YjogJaW8w== Message-ID: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> In-Reply-To: <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5189499470447184158==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5189499470447184158== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28 Content-Type: multipart/alternative; boundary="Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277" --Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii unfortunately, aiui, core can't presently be used to build for xen -- as = i said, i think moves are afoot to fix this but it's a non-trivial thing = to do so i don't know what the timeline is (or even if that's explicitly = on the timeline). i don't know core well, but i know at least one issue = is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. others on the list are better placed to comment on if/when Core code = will be usable with Xen :) On 10 Sep 2014, at 09:43, Ania Skorupa wrote: >=20 > Hi, >=20 > thanks for your reply :) I am trying to build a piece of ocaml program = in mirage, which doesn't have a very large codebase.=20 >=20 > from errors, it looks that core is one of the libraries that results = in this error. in the code, I found that Core.Std is opened. Is that a = library that can not be used for xen? skimming through the code, I = didn't find explicit unix dependencies. >=20 >=20 >=20 > On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >=20 >=20 > Hi, >=20 > I'd guess so, yes. Anything that depends on the underlying platform = (Unix) needs to be abstracted to work with mirage. >=20 > Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >=20 > What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >=20 > -- =20 > Cheers, >=20 > R. >=20 >=20 >=20 > On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >=20 >> Hello guys, >>=20 >> When I compile my mirage application for xen, the following error = happens: >>=20 >> File "_none_", line 1: >> Error: No implementations provided for the following modules: >> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >> /home/user/.opam/system/lib/core/core.cmxa(Core) >> Command exited with code 2. >>=20 >> Am I using libraries that can not be used to for xen unikernel? >>=20 >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 --=20 Cheers, R. --Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii unfortunately, aiui, core can't presently be used to = build for xen -- as i said, i think moves are afoot to fix this but it's = a non-trivial thing to do so i don't know what the timeline is (or even = if that's explicitly on the timeline). i don't know core well, but i = know at least one issue is that the threading library (Core.Async) is = alike to but not completely compatible with = Lwt.

others on the list are better placed to comment = on if/when Core code will be usable with Xen :)

On = 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> = wrote:


Hi,

thanks for your reply :) I am = trying to build a piece of ocaml program in mirage, which doesn't have a = very large codebase.

from = errors, it looks that=20 core is one of the libraries that results in this error. in the code, I=20= found that Core.Std is opened. Is that a library that can not be used=20 for xen? skimming through the code, I didn't find explicit unix=20 dependencies.



= On Tuesday, = September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the = underlying platform (Unix) needs to be abstracted to work with = mirage.

Specifically, all those = modules in the error message have unix dependencies that aren't being = satisfied, though I believe work is ongoing to split js core up to have = a kernel part that will be more compatible with he mirage = approach.

What are you trying to = do? It might be that there are alternative mirage compatible libraries = already available (though that might not help much if you're looking at = porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> = wrote:

Hello guys,
=
When I compile my mirage application for xen, the following error = happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced = from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread),
           = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),<= br class=3D"" style=3D"" clear=3D"none">            = /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen = unikernel?


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


=


--
Cheers,
R.


= --Apple-Mail=_5513852E-39E2-4108-8536-90433EE9C277-- --Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUEBRlAAoJEOLF27JWwSg3RMEP/ixf0vUeoIRlKRUJ1UonvJvK e/eBtsz86DttJ8Ry/Yq3vw6+pbg5GPWT7rD50IjXEvu7IxipWre8TtnMEggcEh7I V/6J61G2BU5JKSHr8W+JoRVWocpnRv8QGapKGpqx1EGjE/jvsH1WopEf/H4ogeLL zcipZkwNK/LbmBvvj1kTiojGSE3IAoqhWAms4JwS7t0UYfO0rXhY2SaXoE2mG4ZG 9goSAMZNZHz5LyhngvRrxjnvOzNftkeU9lCKc8Az7njdCepcKMm4/sXXP4pijyz0 YYXUqd8n2Nj59wYWmVm4fcakLHQ2D4VWXnHdGd31GdHJ1zm3AUuw6n9pPy5Hjsv7 iMJda1jpn+ZXhR2PKmdiRCzKhawZ2zshK2RWRPCSwzL6DzSErLI3yg1aFo5D8VUu 8TO8VH3wYoAsHKlC8bFo1vp0Qa9hvjFBZKHb+IjDxB7Gf0f9JJWk++nTGNmYKTk/ PuMGGTT2aaBVDD7RIt2LjGGHJ2CAemqkZlbtdjbzFSeJGsn7RDlNqRWNocQZ/x9v a7A9B5A1N9pUncKFp+hpERfkekgeT3DE8GQ8Rs9iGlOqWi5sx+u+Dg/VvGTcbtOs qCnxThQcY3dqrnhe0a1sIIG8bP3ZFRDFlHUpbmcLKnfJqF8fOeUBT/S0m9cpTK34 S09/qv2LGKtp2GPOngwJ =OUzG -----END PGP SIGNATURE----- --Apple-Mail=_6D586FEA-B59F-438F-8035-12C765A73E28-- --===============5189499470447184158== 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 --===============5189499470447184158==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 09:34:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 09:34: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 1XReHn-0006nr-QB; Wed, 10 Sep 2014 09:33:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XReHm-0006nh-Ed for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 09:33:58 +0000 Received: from [193.109.254.147:7387] by server-3.bemta-14.messagelabs.com id 14/1A-23707-50B10145; Wed, 10 Sep 2014 09:33:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1410341636!14588818!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17015 invoked from network); 10 Sep 2014 09:33:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 10 Sep 2014 09:33:56 -0000 Received: (qmail 20426 invoked by uid 634); 10 Sep 2014 09:33:55 -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, 10 Sep 2014 10:33:54 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 10 Sep 2014 10:33:50 +0100 Message-Id: <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8862512714508985437==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8862512714508985437== Content-Type: multipart/alternative; boundary="Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8" --Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Ania, Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). Overall though, if you're interested in getting on with applications in = Mirage *right now*, you should avoid Core for now. Using Core_kernel is = pretty close though, so I'll take a look at that. -anil On 10 Sep 2014, at 10:05, Richard Mortier = wrote: > unfortunately, aiui, core can't presently be used to build for xen -- = as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >=20 > others on the list are better placed to comment on if/when Core code = will be usable with Xen :) >=20 > On 10 Sep 2014, at 09:43, Ania Skorupa wrote: >=20 >>=20 >> Hi, >>=20 >> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>=20 >> from errors, it looks that core is one of the libraries that results = in this error. in the code, I found that Core.Std is opened. Is that a = library that can not be used for xen? skimming through the code, I = didn't find explicit unix dependencies. >>=20 >>=20 >>=20 >> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>=20 >>=20 >> Hi, >>=20 >> I'd guess so, yes. Anything that depends on the underlying platform = (Unix) needs to be abstracted to work with mirage. >>=20 >> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>=20 >> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>=20 >> -- =20 >> Cheers, >>=20 >> R. >>=20 >>=20 >>=20 >> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>=20 >>> Hello guys, >>>=20 >>> When I compile my mirage application for xen, the following error = happens: >>>=20 >>> File "_none_", line 1: >>> Error: No implementations provided for the following modules: >>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>> Command exited with code 2. >>>=20 >>> Am I using libraries that can not be used to for xen unikernel? >>>=20 >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=20 >>=20 >=20 >=20 > --=20 > Cheers, >=20 > R. >=20 >=20 >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Ania,

Mort is correct -- we haven't completely = finishing porting Core to Mirage.  This requires breaking it down = into smaller Unix-free chunks, which the upstream maintainers (Jane = Street) have already started doing.  Core consists of several = sub-libraries, of which the Unix-free subset is Core_kernel. =  Core_kernel still requires a few minor C stubs (around Bigarray = handling) which should work with the trunk build of Mirage = (untested).

Overall though, if you're = interested in getting on with applications in Mirage *right now*, you = should avoid Core for now.  Using Core_kernel is pretty close = though, so I'll take a look at = that.

-anil

On 10 Sep = 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to = build for xen -- as i said, i think moves are afoot to fix this but it's = a non-trivial thing to do so i don't know what the timeline is (or even = if that's explicitly on the timeline). i don't know core well, but i = know at least one issue is that the threading library (Core.Async) is = alike to but not completely compatible with = Lwt.

others on the list are better placed to comment = on if/when Core code will be usable with Xen :)

On = 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> = wrote:


Hi,

thanks for your reply :) I am trying to build = a piece of ocaml program in mirage, which doesn't have a very large = codebase. 

from errors, it looks = that core is one of the libraries that results in this error. in the = code, I found that Core.Std is opened. Is that a library that can not be = used for xen? skimming through the code, I didn't find explicit unix = dependencies.



On Tuesday, September 9, 2014 6:32 PM, = Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything = that depends on the underlying platform (Unix) needs to be abstracted to = work with mirage.

Specifically, all those modules in = the error message have unix dependencies that aren't being satisfied, = though I believe work is ongoing to split js core up to have a kernel = part that will be more compatible with he mirage approach.

What are = you trying to do? It might be that there are alternative mirage = compatible libraries already available (though that might not help much = if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> = wrote:

Hello = guys,

When I = compile my mirage application for xen, the following error happens:

File "_none_", = line 1:
Error: No implementations provided = for the following modules:
         = UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix = referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
          = ; = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
          = ; = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),<= br class=3D"" = clear=3D"none">          = ; /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that = can not be used to for xen unikernel?


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




-- 
Cheers,

R.




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

= --Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8-- --===============8862512714508985437== 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 --===============8862512714508985437==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 09:34:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 09:34: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 1XReHn-0006nr-QB; Wed, 10 Sep 2014 09:33:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XReHm-0006nh-Ed for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 09:33:58 +0000 Received: from [193.109.254.147:7387] by server-3.bemta-14.messagelabs.com id 14/1A-23707-50B10145; Wed, 10 Sep 2014 09:33:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1410341636!14588818!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17015 invoked from network); 10 Sep 2014 09:33:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-27.messagelabs.com with SMTP; 10 Sep 2014 09:33:56 -0000 Received: (qmail 20426 invoked by uid 634); 10 Sep 2014 09:33:55 -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, 10 Sep 2014 10:33:54 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 10 Sep 2014 10:33:50 +0100 Message-Id: <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8862512714508985437==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8862512714508985437== Content-Type: multipart/alternative; boundary="Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8" --Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Ania, Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). Overall though, if you're interested in getting on with applications in = Mirage *right now*, you should avoid Core for now. Using Core_kernel is = pretty close though, so I'll take a look at that. -anil On 10 Sep 2014, at 10:05, Richard Mortier = wrote: > unfortunately, aiui, core can't presently be used to build for xen -- = as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >=20 > others on the list are better placed to comment on if/when Core code = will be usable with Xen :) >=20 > On 10 Sep 2014, at 09:43, Ania Skorupa wrote: >=20 >>=20 >> Hi, >>=20 >> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>=20 >> from errors, it looks that core is one of the libraries that results = in this error. in the code, I found that Core.Std is opened. Is that a = library that can not be used for xen? skimming through the code, I = didn't find explicit unix dependencies. >>=20 >>=20 >>=20 >> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>=20 >>=20 >> Hi, >>=20 >> I'd guess so, yes. Anything that depends on the underlying platform = (Unix) needs to be abstracted to work with mirage. >>=20 >> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>=20 >> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>=20 >> -- =20 >> Cheers, >>=20 >> R. >>=20 >>=20 >>=20 >> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>=20 >>> Hello guys, >>>=20 >>> When I compile my mirage application for xen, the following error = happens: >>>=20 >>> File "_none_", line 1: >>> Error: No implementations provided for the following modules: >>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>> Command exited with code 2. >>>=20 >>> Am I using libraries that can not be used to for xen unikernel? >>>=20 >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=20 >>=20 >=20 >=20 > --=20 > Cheers, >=20 > R. >=20 >=20 >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Ania,

Mort is correct -- we haven't completely = finishing porting Core to Mirage.  This requires breaking it down = into smaller Unix-free chunks, which the upstream maintainers (Jane = Street) have already started doing.  Core consists of several = sub-libraries, of which the Unix-free subset is Core_kernel. =  Core_kernel still requires a few minor C stubs (around Bigarray = handling) which should work with the trunk build of Mirage = (untested).

Overall though, if you're = interested in getting on with applications in Mirage *right now*, you = should avoid Core for now.  Using Core_kernel is pretty close = though, so I'll take a look at = that.

-anil

On 10 Sep = 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to = build for xen -- as i said, i think moves are afoot to fix this but it's = a non-trivial thing to do so i don't know what the timeline is (or even = if that's explicitly on the timeline). i don't know core well, but i = know at least one issue is that the threading library (Core.Async) is = alike to but not completely compatible with = Lwt.

others on the list are better placed to comment = on if/when Core code will be usable with Xen :)

On = 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> = wrote:


Hi,

thanks for your reply :) I am trying to build = a piece of ocaml program in mirage, which doesn't have a very large = codebase. 

from errors, it looks = that core is one of the libraries that results in this error. in the = code, I found that Core.Std is opened. Is that a library that can not be = used for xen? skimming through the code, I didn't find explicit unix = dependencies.



On Tuesday, September 9, 2014 6:32 PM, = Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything = that depends on the underlying platform (Unix) needs to be abstracted to = work with mirage.

Specifically, all those modules in = the error message have unix dependencies that aren't being satisfied, = though I believe work is ongoing to split js core up to have a kernel = part that will be more compatible with he mirage approach.

What are = you trying to do? It might be that there are alternative mirage = compatible libraries already available (though that might not help much = if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> = wrote:

Hello = guys,

When I = compile my mirage application for xen, the following error happens:

File "_none_", = line 1:
Error: No implementations provided = for the following modules:
         = UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix = referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
          = ; = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
          = ; = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),<= br class=3D"" = clear=3D"none">          = ; /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that = can not be used to for xen unikernel?


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




-- 
Cheers,

R.




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

= --Apple-Mail=_193E486B-B483-4E6F-B785-C7AB75CBD4D8-- --===============8862512714508985437== 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 --===============8862512714508985437==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 10:55:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 10:55: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 1XRfYp-0007my-Ij; Wed, 10 Sep 2014 10:55:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRfYo-0007mo-K0 for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 10:55:38 +0000 Received: from [193.109.254.147:11849] by server-15.bemta-14.messagelabs.com id 41/C8-30948-A2E20145; Wed, 10 Sep 2014 10:55:38 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1410346534!14653241!1 X-Originating-IP: [98.138.120.56] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27050 invoked from network); 10 Sep 2014 10:55:36 -0000 Received: from nm49.bullet.mail.ne1.yahoo.com (HELO nm49.bullet.mail.ne1.yahoo.com) (98.138.120.56) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2014 10:55:36 -0000 Received: from [127.0.0.1] by nm49.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 10:55:34 -0000 Received: from [98.138.100.112] by nm49.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 10:52:38 -0000 Received: from [98.139.215.143] by tm103.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 10:52:38 -0000 Received: from [98.139.212.241] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 10:52:37 -0000 Received: from [127.0.0.1] by omp1050.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 10:52:37 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 896054.11866.bm@omp1050.mail.bf1.yahoo.com Received: (qmail 10063 invoked by uid 60001); 10 Sep 2014 10:52:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410346356; bh=MnJAnXpUhxdtWunOxA1gNo3v/XEwJXJeoQFB3H9QKIk=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=uwdg3UBAyQRV1pCZyQEe/m31KLh1GHLzI8EMmfIGtiefz5IQCg3NULkmCkvk4AOoqEj6Ck5r8E+1vMWO+7+wmRBNzMv3kZ2i0YqY12i76NT+BmtSGEV0pO7Ml3XXeZ77zk/35C26N4QzAQos6Lg5sWumzybY+3a05XuLNt+NMTQ= X-YMail-OSG: IPaXWnUVM1mV2LrFsTQ4Fa.2iyww2WM91gYUA3M1cRYHBaE muxiTLQDJCUz9nh0kSW6KxGub8cIipnryegd6.T04Ivwq8.l5w_cjIdK2U37 oaUQZNfPipyHk82cGq6UkBtDNfGBfM8HMh9IFjrGbp2jwxJBdFuZ03wCQ4pr YE6DIgKg1Q2iKEHPOru3UBt0D6qVBKC3.Z27LGJZI5eQdAMlo2f5Q6vUOCKw MV30sxp.P94.WjKjFJDZWwIGiETD.DAZJzagJspvd1u2g3WYMZhCafPKsRj0 x1jB482NSQxuFY8.8eDAK1nVr4FMHR1SbC3om8y1skOEyK7tD7aDS5oWgyBy DJNKKCPQ61lF.FoS.owaP9FI1u46zyxLW3QwUGSSfVIDdImwZ8zQFNqpQhtu JHgYnaO01B_75Kvp.weLyCyVH2T55RSLnqtNL_ieOUX5hAR35TYc6FLwVcLZ c.Y.9fFuclhQ9SCCz8Zr5hj8gz3RnktQTeg8.1503Wf8O7iz5kIq2dLMtPny OqOZlpEtISscbeJB3Mgp_rbHv260Qbg-- Received: from [94.242.246.24] by web142401.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 03:52:36 PDT X-Rocket-MIMEInfo: 002.001, VGhhbmsgeW91IGZvciB0aGUgcmVwbGllcyA6LSkKCgoKT24gV2VkbmVzZGF5LCBTZXB0ZW1iZXIgMTAsIDIwMTQgOTozMyBBTSwgQW5pbCBNYWRoYXZhcGVkZHkgPGFuaWxAcmVjb2lsLm9yZz4gd3JvdGU6CiAKCgpIaSBBbmlhLAoKTW9ydCBpcyBjb3JyZWN0IC0tIHdlIGhhdmVuJ3QgY29tcGxldGVseSBmaW5pc2hpbmcgcG9ydGluZyBDb3JlIHRvIE1pcmFnZS4gIFRoaXMgcmVxdWlyZXMgYnJlYWtpbmcgaXQgZG93biBpbnRvIHNtYWxsZXIgVW5peC1mcmVlIGNodW5rcywgd2hpY2ggdGhlIHVwc3RyZWFtIG0BMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> Message-ID: <1410346356.56135.YahooMailNeo@web142401.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 03:52:36 -0700 From: Ania Skorupa To: Anil Madhavapeddy , Richard Mortier In-Reply-To: <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2784471568642669719==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2784471568642669719== Content-Type: multipart/alternative; boundary="1173125169-1833249549-1410346356=:56135" --1173125169-1833249549-1410346356=:56135 Content-Type: text/plain; charset=us-ascii Thank you for the replies :-) On Wednesday, September 10, 2014 9:33 AM, Anil Madhavapeddy wrote: Hi Ania, Mort is correct -- we haven't completely finishing porting Core to Mirage. This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing. Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel. Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested). Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now. Using Core_kernel is pretty close though, so I'll take a look at that. -anil On 10 Sep 2014, at 10:05, Richard Mortier wrote: unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt. > > >others on the list are better placed to comment on if/when Core code will be usable with Xen :) > > > >On 10 Sep 2014, at 09:43, Ania Skorupa wrote: > > >> >>Hi, >> >> >>thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. >> >> >> >>from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies. >> >> >> >> >> >>On Tuesday, September 9, 2014 6:32 PM, Richard Mortier wrote: >> >> >> >>Hi, >> >> >>I'd guess so, yes. Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage. >> >> >>Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach. >> >> >>What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :) >> >>-- >>Cheers, >> >> >>R. >> >> >> >> >> >>On 9 Sep 2014, at 19:13, "Ania Skorupa" wrote: >> >> >>Hello guys, >>> >>>When I compile my mirage application for xen, the following error happens: >>> >>>File "_none_", line 1: >>>Error: No implementations provided for the following modules: >>> UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core) >>> Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), >>> /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>> /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>Command exited with code 2. >>> >>>Am I using libraries that can not be used to for xen unikernel? >>> >>> >>> >>> >>_______________________________________________ >>>MirageOS-devel mailing list >>>MirageOS-devel@lists.xenproject.org >>>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> >> >> >> > > > >-- >Cheers, > >R. > > > > > >_______________________________________________ >MirageOS-devel mailing list >MirageOS-devel@lists.xenproject.org >http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --1173125169-1833249549-1410346356=:56135 Content-Type: text/html; charset=us-ascii
Thank you for the replies :-)


On Wednesday, September 10, 2014 9:33 AM, Anil Madhavapeddy <anil@recoil.org> wrote:


Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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





-- 
Cheers,

R.




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



--1173125169-1833249549-1410346356=:56135-- --===============2784471568642669719== 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 --===============2784471568642669719==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 10:55:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 10:55: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 1XRfYp-0007my-Ij; Wed, 10 Sep 2014 10:55:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRfYo-0007mo-K0 for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 10:55:38 +0000 Received: from [193.109.254.147:11849] by server-15.bemta-14.messagelabs.com id 41/C8-30948-A2E20145; Wed, 10 Sep 2014 10:55:38 +0000 X-Env-Sender: ania.skorupa@yahoo.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1410346534!14653241!1 X-Originating-IP: [98.138.120.56] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_6,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27050 invoked from network); 10 Sep 2014 10:55:36 -0000 Received: from nm49.bullet.mail.ne1.yahoo.com (HELO nm49.bullet.mail.ne1.yahoo.com) (98.138.120.56) by server-4.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2014 10:55:36 -0000 Received: from [127.0.0.1] by nm49.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 10:55:34 -0000 Received: from [98.138.100.112] by nm49.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 10:52:38 -0000 Received: from [98.139.215.143] by tm103.bullet.mail.ne1.yahoo.com with NNFMP; 10 Sep 2014 10:52:38 -0000 Received: from [98.139.212.241] by tm14.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 10:52:37 -0000 Received: from [127.0.0.1] by omp1050.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 10:52:37 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 896054.11866.bm@omp1050.mail.bf1.yahoo.com Received: (qmail 10063 invoked by uid 60001); 10 Sep 2014 10:52:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1410346356; bh=MnJAnXpUhxdtWunOxA1gNo3v/XEwJXJeoQFB3H9QKIk=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=uwdg3UBAyQRV1pCZyQEe/m31KLh1GHLzI8EMmfIGtiefz5IQCg3NULkmCkvk4AOoqEj6Ck5r8E+1vMWO+7+wmRBNzMv3kZ2i0YqY12i76NT+BmtSGEV0pO7Ml3XXeZ77zk/35C26N4QzAQos6Lg5sWumzybY+3a05XuLNt+NMTQ= X-YMail-OSG: IPaXWnUVM1mV2LrFsTQ4Fa.2iyww2WM91gYUA3M1cRYHBaE muxiTLQDJCUz9nh0kSW6KxGub8cIipnryegd6.T04Ivwq8.l5w_cjIdK2U37 oaUQZNfPipyHk82cGq6UkBtDNfGBfM8HMh9IFjrGbp2jwxJBdFuZ03wCQ4pr YE6DIgKg1Q2iKEHPOru3UBt0D6qVBKC3.Z27LGJZI5eQdAMlo2f5Q6vUOCKw MV30sxp.P94.WjKjFJDZWwIGiETD.DAZJzagJspvd1u2g3WYMZhCafPKsRj0 x1jB482NSQxuFY8.8eDAK1nVr4FMHR1SbC3om8y1skOEyK7tD7aDS5oWgyBy DJNKKCPQ61lF.FoS.owaP9FI1u46zyxLW3QwUGSSfVIDdImwZ8zQFNqpQhtu JHgYnaO01B_75Kvp.weLyCyVH2T55RSLnqtNL_ieOUX5hAR35TYc6FLwVcLZ c.Y.9fFuclhQ9SCCz8Zr5hj8gz3RnktQTeg8.1503Wf8O7iz5kIq2dLMtPny OqOZlpEtISscbeJB3Mgp_rbHv260Qbg-- Received: from [94.242.246.24] by web142401.mail.bf1.yahoo.com via HTTP; Wed, 10 Sep 2014 03:52:36 PDT X-Rocket-MIMEInfo: 002.001, VGhhbmsgeW91IGZvciB0aGUgcmVwbGllcyA6LSkKCgoKT24gV2VkbmVzZGF5LCBTZXB0ZW1iZXIgMTAsIDIwMTQgOTozMyBBTSwgQW5pbCBNYWRoYXZhcGVkZHkgPGFuaWxAcmVjb2lsLm9yZz4gd3JvdGU6CiAKCgpIaSBBbmlhLAoKTW9ydCBpcyBjb3JyZWN0IC0tIHdlIGhhdmVuJ3QgY29tcGxldGVseSBmaW5pc2hpbmcgcG9ydGluZyBDb3JlIHRvIE1pcmFnZS4gIFRoaXMgcmVxdWlyZXMgYnJlYWtpbmcgaXQgZG93biBpbnRvIHNtYWxsZXIgVW5peC1mcmVlIGNodW5rcywgd2hpY2ggdGhlIHVwc3RyZWFtIG0BMAEBAQE- X-Mailer: YahooMailWebService/0.8.203.696 References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> Message-ID: <1410346356.56135.YahooMailNeo@web142401.mail.bf1.yahoo.com> Date: Wed, 10 Sep 2014 03:52:36 -0700 From: Ania Skorupa To: Anil Madhavapeddy , Richard Mortier In-Reply-To: <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Ania Skorupa List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2784471568642669719==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2784471568642669719== Content-Type: multipart/alternative; boundary="1173125169-1833249549-1410346356=:56135" --1173125169-1833249549-1410346356=:56135 Content-Type: text/plain; charset=us-ascii Thank you for the replies :-) On Wednesday, September 10, 2014 9:33 AM, Anil Madhavapeddy wrote: Hi Ania, Mort is correct -- we haven't completely finishing porting Core to Mirage. This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing. Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel. Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested). Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now. Using Core_kernel is pretty close though, so I'll take a look at that. -anil On 10 Sep 2014, at 10:05, Richard Mortier wrote: unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt. > > >others on the list are better placed to comment on if/when Core code will be usable with Xen :) > > > >On 10 Sep 2014, at 09:43, Ania Skorupa wrote: > > >> >>Hi, >> >> >>thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. >> >> >> >>from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies. >> >> >> >> >> >>On Tuesday, September 9, 2014 6:32 PM, Richard Mortier wrote: >> >> >> >>Hi, >> >> >>I'd guess so, yes. Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage. >> >> >>Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach. >> >> >>What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :) >> >>-- >>Cheers, >> >> >>R. >> >> >> >> >> >>On 9 Sep 2014, at 19:13, "Ania Skorupa" wrote: >> >> >>Hello guys, >>> >>>When I compile my mirage application for xen, the following error happens: >>> >>>File "_none_", line 1: >>>Error: No implementations provided for the following modules: >>> UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core) >>> Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), >>> /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>> /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>Command exited with code 2. >>> >>>Am I using libraries that can not be used to for xen unikernel? >>> >>> >>> >>> >>_______________________________________________ >>>MirageOS-devel mailing list >>>MirageOS-devel@lists.xenproject.org >>>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >>> >> >> >> > > > >-- >Cheers, > >R. > > > > > >_______________________________________________ >MirageOS-devel mailing list >MirageOS-devel@lists.xenproject.org >http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --1173125169-1833249549-1410346356=:56135 Content-Type: text/html; charset=us-ascii
Thank you for the replies :-)


On Wednesday, September 10, 2014 9:33 AM, Anil Madhavapeddy <anil@recoil.org> wrote:


Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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





-- 
Cheers,

R.




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



--1173125169-1833249549-1410346356=:56135-- --===============2784471568642669719== 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 --===============2784471568642669719==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 12:20:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 12:20: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 1XRgsu-0005j4-UN; Wed, 10 Sep 2014 12:20:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRgst-0005iz-Og for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 12:20:27 +0000 Received: from [85.158.143.35:63690] by server-3.bemta-4.messagelabs.com id C9/01-06192-B0240145; Wed, 10 Sep 2014 12:20:27 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1410351626!12848380!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 531 invoked from network); 10 Sep 2014 12:20:26 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-21.messagelabs.com with SMTP; 10 Sep 2014 12:20:26 -0000 Received: (qmail 5242 invoked by uid 634); 10 Sep 2014 12:20:25 -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 no-dns-yet.demon.co.uk (HELO [192.168.14.219]) (62.49.66.12) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 10 Sep 2014 13:20:25 +0100 From: Anil Madhavapeddy Date: Wed, 10 Sep 2014 13:20:21 +0100 References: To: mirageos-devel@lists.xenproject.org Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Fwd: [opam-devel] OCaml/OPAM PPAs updated: now with armhf and OPAM 1.2.0 X-BeenThere: mirageos-devel@lists.xenproject.org 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 FYI -- armhf PPAs now available! Begin forwarded message: > From: Anil Madhavapeddy > Subject: [opam-devel] OCaml/OPAM PPAs updated: now with armhf and OPAM 1.2.0 > Date: 8 September 2014 21:23:23 BST > To: opam-devel > > Some updates to the binary packages used by all the Travis tests: > > - The Ubuntu launchpad folk kindly upgraded my account to support > ARM builds, and so the various PPA combinations now include armhf > binaries, which should greatly help save build times there. > See: https://launchpad.net/~avsm/ for all the combinations of PPAs. > > - Added PPAs for the OCaml 4.02 and OPAM 1.2.0 combinations, up to > the latest OPAM snapshot today. When's the OPAM 1.2.x branch > going to be created, Louis? I can call the packages 1.2.0 then. > > - Added binary packages for camlp4 as well, so that it remains a > system package. The (rather hacked up) Debian package for this > is in the experimental/master branch at: > https://github.com/avsm/camlp4 > > Enjoy! If there are no problems with these, I'll be blogging about > it for the opam.ocaml.org site when I get a chance so they are > seen more widely. > > -anil > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-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 Sep 10 12:20:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 12:20: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 1XRgsu-0005j4-UN; Wed, 10 Sep 2014 12:20:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRgst-0005iz-Og for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 12:20:27 +0000 Received: from [85.158.143.35:63690] by server-3.bemta-4.messagelabs.com id C9/01-06192-B0240145; Wed, 10 Sep 2014 12:20:27 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1410351626!12848380!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 531 invoked from network); 10 Sep 2014 12:20:26 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-21.messagelabs.com with SMTP; 10 Sep 2014 12:20:26 -0000 Received: (qmail 5242 invoked by uid 634); 10 Sep 2014 12:20:25 -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 no-dns-yet.demon.co.uk (HELO [192.168.14.219]) (62.49.66.12) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 10 Sep 2014 13:20:25 +0100 From: Anil Madhavapeddy Date: Wed, 10 Sep 2014 13:20:21 +0100 References: To: mirageos-devel@lists.xenproject.org Message-Id: Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Fwd: [opam-devel] OCaml/OPAM PPAs updated: now with armhf and OPAM 1.2.0 X-BeenThere: mirageos-devel@lists.xenproject.org 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 FYI -- armhf PPAs now available! Begin forwarded message: > From: Anil Madhavapeddy > Subject: [opam-devel] OCaml/OPAM PPAs updated: now with armhf and OPAM 1.2.0 > Date: 8 September 2014 21:23:23 BST > To: opam-devel > > Some updates to the binary packages used by all the Travis tests: > > - The Ubuntu launchpad folk kindly upgraded my account to support > ARM builds, and so the various PPA combinations now include armhf > binaries, which should greatly help save build times there. > See: https://launchpad.net/~avsm/ for all the combinations of PPAs. > > - Added PPAs for the OCaml 4.02 and OPAM 1.2.0 combinations, up to > the latest OPAM snapshot today. When's the OPAM 1.2.x branch > going to be created, Louis? I can call the packages 1.2.0 then. > > - Added binary packages for camlp4 as well, so that it remains a > system package. The (rather hacked up) Debian package for this > is in the experimental/master branch at: > https://github.com/avsm/camlp4 > > Enjoy! If there are no problems with these, I'll be blogging about > it for the opam.ocaml.org site when I get a chance so they are > seen more widely. > > -anil > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-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 Sep 10 14:56:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 14:56: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 1XRjJX-0005AM-B2; Wed, 10 Sep 2014 14:56:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRjJV-0005AG-Ci for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 14:56:05 +0000 Received: from [193.109.254.147:40739] by server-7.bemta-14.messagelabs.com id 9A/47-13362-48660145; Wed, 10 Sep 2014 14:56:04 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1410360963!14617068!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16399 invoked from network); 10 Sep 2014 14:56:03 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-27.messagelabs.com with SMTP; 10 Sep 2014 14:56:03 -0000 Received: (qmail 27602 invoked by uid 634); 10 Sep 2014 14:56:02 -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, 10 Sep 2014 15:56:01 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <54101FF4.40109@nottingham.ac.uk> Date: Wed, 10 Sep 2014 15:55:59 +0100 Message-Id: <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> To: Masoud Koleini , Yaron Minsky X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Spiros Eliopoulos , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0667993868915843655==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0667993868915843655== Content-Type: multipart/alternative; boundary="Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4" --Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 (Re-adding the devel list to CC) The s-expression library is actually independent of Unix, so that's = fine. It's easiest to fork Frenetic in the short term and shift it to = using Core_kernel instead of Core. There will be probably be an Async = scheduler, which is a lot more work to fix. This requires shifting the = Async portions to use Async_kernel instead, which Jane Street is working = on. CCing Yaron -- any sense of how far away Async_kernel is from a public = release? We can get started on an Async_xen port then as well. -anil On 10 Sep 2014, at 10:55, Masoud Koleini = wrote: > Oh, we will have the same problem! >=20 > Frenetic protocol library uses Core, mostly for s-expressions. So far, = I was testing it with unix config to figure out build and controller = communication problems. >=20 > Any idea of how we can make it work for xen? I think we have to modify = Frenetic library to compile on both unix and xen, but try to keep this = modification as light as possible until we have Core ported to Mirage. >=20 >=20 > On 10/09/14 10:33, Anil Madhavapeddy wrote: >> Hi Ania, >>=20 >> Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). >>=20 >> Overall though, if you're interested in getting on with applications = in Mirage *right now*, you should avoid Core for now. Using Core_kernel = is pretty close though, so I'll take a look at that. >>=20 >> -anil >>=20 >> On 10 Sep 2014, at 10:05, Richard Mortier = wrote: >>=20 >>> unfortunately, aiui, core can't presently be used to build for xen = -- as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >>>=20 >>> others on the list are better placed to comment on if/when Core code = will be usable with Xen :) >>>=20 >>> On 10 Sep 2014, at 09:43, Ania Skorupa = wrote: >>>=20 >>>>=20 >>>> Hi, >>>>=20 >>>> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>>>=20 >>>> from errors, it looks that core is one of the libraries that = results in this error. in the code, I found that Core.Std is opened. Is = that a library that can not be used for xen? skimming through the code, = I didn't find explicit unix dependencies. >>>>=20 >>>>=20 >>>>=20 >>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>>>=20 >>>>=20 >>>> Hi, >>>>=20 >>>> I'd guess so, yes. Anything that depends on the underlying = platform (Unix) needs to be abstracted to work with mirage. >>>>=20 >>>> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>>>=20 >>>> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>>>=20 >>>> -- =20 >>>> Cheers, >>>>=20 >>>> R. >>>>=20 >>>>=20 >>>>=20 >>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>>>=20 >>>>> Hello guys, >>>>>=20 >>>>> When I compile my mirage application for xen, the following error = happens: >>>>>=20 >>>>> File "_none_", line 1: >>>>> Error: No implementations provided for the following modules: >>>>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>> Command exited with code 2. >>>>>=20 >>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@lists.xenproject.org >>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>=20 >>>>=20 >>>=20 >>>=20 >>> --=20 >>> Cheers, >>>=20 >>> R. >>>=20 >>>=20 >>>=20 >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=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 --Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 (Re-adding the devel list to = CC)

The s-expression library is actually independent = of Unix, so that's fine.  It's easiest to fork Frenetic in the = short term and shift it to using Core_kernel instead of Core. =  There will be probably be an Async scheduler, which is a lot more = work to fix.  This requires shifting the Async portions to use = Async_kernel instead, which Jane Street is working = on.

CCing Yaron -- any sense of how far away = Async_kernel is from a public release?  We can get started on an = Async_xen port then as = well.

-anil

On 10 Sep = 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.= ac.uk> wrote:

=20 =20
Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into = smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll = take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your = reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it = looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying = to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello = guys,

When I compile my mirage application for xen, the following error = happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
=          UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core)
=          Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread),
= =            = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
=            = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),<= br class=3D"" clear=3D"none"> =            = /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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




= -- 
Cheers,

R.




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


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

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.



= --Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4-- --===============0667993868915843655== 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 --===============0667993868915843655==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 14:56:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 14:56: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 1XRjJX-0005AM-B2; Wed, 10 Sep 2014 14:56:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRjJV-0005AG-Ci for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 14:56:05 +0000 Received: from [193.109.254.147:40739] by server-7.bemta-14.messagelabs.com id 9A/47-13362-48660145; Wed, 10 Sep 2014 14:56:04 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1410360963!14617068!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16399 invoked from network); 10 Sep 2014 14:56:03 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-27.messagelabs.com with SMTP; 10 Sep 2014 14:56:03 -0000 Received: (qmail 27602 invoked by uid 634); 10 Sep 2014 14:56:02 -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, 10 Sep 2014 15:56:01 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <54101FF4.40109@nottingham.ac.uk> Date: Wed, 10 Sep 2014 15:55:59 +0100 Message-Id: <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> To: Masoud Koleini , Yaron Minsky X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Spiros Eliopoulos , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0667993868915843655==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0667993868915843655== Content-Type: multipart/alternative; boundary="Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4" --Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 (Re-adding the devel list to CC) The s-expression library is actually independent of Unix, so that's = fine. It's easiest to fork Frenetic in the short term and shift it to = using Core_kernel instead of Core. There will be probably be an Async = scheduler, which is a lot more work to fix. This requires shifting the = Async portions to use Async_kernel instead, which Jane Street is working = on. CCing Yaron -- any sense of how far away Async_kernel is from a public = release? We can get started on an Async_xen port then as well. -anil On 10 Sep 2014, at 10:55, Masoud Koleini = wrote: > Oh, we will have the same problem! >=20 > Frenetic protocol library uses Core, mostly for s-expressions. So far, = I was testing it with unix config to figure out build and controller = communication problems. >=20 > Any idea of how we can make it work for xen? I think we have to modify = Frenetic library to compile on both unix and xen, but try to keep this = modification as light as possible until we have Core ported to Mirage. >=20 >=20 > On 10/09/14 10:33, Anil Madhavapeddy wrote: >> Hi Ania, >>=20 >> Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). >>=20 >> Overall though, if you're interested in getting on with applications = in Mirage *right now*, you should avoid Core for now. Using Core_kernel = is pretty close though, so I'll take a look at that. >>=20 >> -anil >>=20 >> On 10 Sep 2014, at 10:05, Richard Mortier = wrote: >>=20 >>> unfortunately, aiui, core can't presently be used to build for xen = -- as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >>>=20 >>> others on the list are better placed to comment on if/when Core code = will be usable with Xen :) >>>=20 >>> On 10 Sep 2014, at 09:43, Ania Skorupa = wrote: >>>=20 >>>>=20 >>>> Hi, >>>>=20 >>>> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>>>=20 >>>> from errors, it looks that core is one of the libraries that = results in this error. in the code, I found that Core.Std is opened. Is = that a library that can not be used for xen? skimming through the code, = I didn't find explicit unix dependencies. >>>>=20 >>>>=20 >>>>=20 >>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>>>=20 >>>>=20 >>>> Hi, >>>>=20 >>>> I'd guess so, yes. Anything that depends on the underlying = platform (Unix) needs to be abstracted to work with mirage. >>>>=20 >>>> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>>>=20 >>>> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>>>=20 >>>> -- =20 >>>> Cheers, >>>>=20 >>>> R. >>>>=20 >>>>=20 >>>>=20 >>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>>>=20 >>>>> Hello guys, >>>>>=20 >>>>> When I compile my mirage application for xen, the following error = happens: >>>>>=20 >>>>> File "_none_", line 1: >>>>> Error: No implementations provided for the following modules: >>>>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>> Command exited with code 2. >>>>>=20 >>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@lists.xenproject.org >>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>=20 >>>>=20 >>>=20 >>>=20 >>> --=20 >>> Cheers, >>>=20 >>> R. >>>=20 >>>=20 >>>=20 >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=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 --Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 (Re-adding the devel list to = CC)

The s-expression library is actually independent = of Unix, so that's fine.  It's easiest to fork Frenetic in the = short term and shift it to using Core_kernel instead of Core. =  There will be probably be an Async scheduler, which is a lot more = work to fix.  This requires shifting the Async portions to use = Async_kernel instead, which Jane Street is working = on.

CCing Yaron -- any sense of how far away = Async_kernel is from a public release?  We can get started on an = Async_xen port then as = well.

-anil

On 10 Sep = 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.= ac.uk> wrote:

=20 =20
Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into = smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll = take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your = reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it = looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingha= m.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying = to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello = guys,

When I compile my mirage application for xen, the following error = happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
=          UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core)
=          Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread),
= =            = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
=            = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),<= br class=3D"" clear=3D"none"> =            = /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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




= -- 
Cheers,

R.




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


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

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.



= --Apple-Mail=_DBA8C4AB-A320-454B-A59B-231A74724CB4-- --===============0667993868915843655== 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 --===============0667993868915843655==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 15:06:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 15:06: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 1XRjTa-00066r-Fq; Wed, 10 Sep 2014 15:06:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRjTY-00066f-OH for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 15:06:28 +0000 Received: from [85.158.137.68:43577] by server-2.bemta-3.messagelabs.com id 7A/0E-09149-4F860145; Wed, 10 Sep 2014 15:06:28 +0000 X-Env-Sender: yminsky@janestreet.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1410361586!13733170!1 X-Originating-IP: [38.105.200.229] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMzguMTA1LjIwMC4yMjkgPT4gMjA3NjM=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30301 invoked from network); 10 Sep 2014 15:06:27 -0000 Received: from mxout3.mail.janestreet.com (HELO mxout3.mail.janestreet.com) (38.105.200.229) by server-13.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2014 15:06:27 -0000 Received: from tot-oib-smtp1 ([172.27.22.15] helo=tot-smtp) by mxout3.mail.janestreet.com with esmtps (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XRjTV-0001xH-Vv for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 11:06:26 -0400 Received: from [172.27.229.230] (helo=mxgoog1.mail.janestreet.com) by tot-smtp with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from ) id 1XRjTV-00028k-S2 for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 11:06:25 -0400 Received: from mail-lb0-f182.google.com ([209.85.217.182]) by mxgoog1.mail.janestreet.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1XRjTV-0006Ig-Hf for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 11:06:25 -0400 Received: by mail-lb0-f182.google.com with SMTP id v6so4995878lbi.13 for ; Wed, 10 Sep 2014 08:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zbrkIN67kde04xYlOSf2IEmSPMfGQr/wHx/8gzrhofY=; b=bFJdlakVMdSPujf8JxQkugNihipfTd17n33Myp2pvSTdBq2V3dvZaGTLKY9Fn1/3wE wdrkOMfY5zSqnlG9PLXCL5DgYYze8dEgqWXvf058PzV1N4/dVqfI3mKZgELKCsYhoWNN pZrq19dPV1ora1jJBdw4TnHFEcsyGef3MbOgs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=zbrkIN67kde04xYlOSf2IEmSPMfGQr/wHx/8gzrhofY=; b=Oe8/j9Agodd/o+3TbJajQmAynr5WOEU6bfxtyzHQBnIKecKNJw5JUOwTEwuN89CgvK DmUu5rg19n0cUGZFAJLXxR3cJPdO3GK69fu68oWGFytogtn53gQHea6MzaOYi3XIpa90 rURq+ivIJXiP62prejsLGtcWPqSyUpQXmrsyE8mkxn8YZPaIs/9G1by3aLQXr5u/qZl1 1/BfTgc5p9CjVm9Sdi2SkmMYt8g6HmxC6a7bkw1I3vk3KV+ucdGLb7Ny1e6Rrf345nMO fkTX0PRG4NfiZ7lP+YpR1dDW46daCT3+xMcx0OhlhNTsou1l7bw5VtyKKQZ5GhkiX3Lb Hk2A== X-Gm-Message-State: ALoCoQkJvtJ9BxgUrT35PpU1O4znLgdSCSdOqj+SqdUGl4aREg1iorDbX8nEMG0F0FRu2ZROJsrlNQ5htdOkuBI2DqalirJZEgwXLmRSDv3itMaKCceuOzbbb5qVTiiQIXCigfqspBUx5u0xp8ZJWkpFLYQCQp4ELw== X-Received: by 10.152.28.230 with SMTP id e6mr43052085lah.62.1410361584228; Wed, 10 Sep 2014 08:06:24 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.28.230 with SMTP id e6mr43052070lah.62.1410361584068; Wed, 10 Sep 2014 08:06:24 -0700 (PDT) Received: by 10.112.56.136 with HTTP; Wed, 10 Sep 2014 08:06:23 -0700 (PDT) In-Reply-To: <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> Date: Wed, 10 Sep 2014 11:06:23 -0400 Message-ID: From: Yaron Minsky To: Anil Madhavapeddy Cc: Spiros Eliopoulos , Stephen Weeks , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Sep 10, 2014 at 10:55 AM, Anil Madhavapeddy wrote: > (Re-adding the devel list to CC) > > The s-expression library is actually independent of Unix, so that's fine. > It's easiest to fork Frenetic in the short term and shift it to using > Core_kernel instead of Core. There will be probably be an Async scheduler, > which is a lot more work to fix. This requires shifting the Async portions > to use Async_kernel instead, which Jane Street is working on. > > CCing Yaron -- any sense of how far away Async_kernel is from a public > release? We can get started on an Async_xen port then as well. CC'ing Sweeks. I think the concrete work is just getting started now. Sweeks, can you come up with a rough estimate? > -anil > > On 10 Sep 2014, at 10:55, Masoud Koleini > wrote: > > Oh, we will have the same problem! > > Frenetic protocol library uses Core, mostly for s-expressions. So far, I was > testing it with unix config to figure out build and controller communication > problems. > > Any idea of how we can make it work for xen? I think we have to modify > Frenetic library to compile on both unix and xen, but try to keep this > modification as light as possible until we have Core ported to Mirage. > > > On 10/09/14 10:33, Anil Madhavapeddy wrote: > > Hi Ania, > > Mort is correct -- we haven't completely finishing porting Core to Mirage. > This requires breaking it down into smaller Unix-free chunks, which the > upstream maintainers (Jane Street) have already started doing. Core > consists of several sub-libraries, of which the Unix-free subset is > Core_kernel. Core_kernel still requires a few minor C stubs (around > Bigarray handling) which should work with the trunk build of Mirage > (untested). > > Overall though, if you're interested in getting on with applications in > Mirage *right now*, you should avoid Core for now. Using Core_kernel is > pretty close though, so I'll take a look at that. > > -anil > > On 10 Sep 2014, at 10:05, Richard Mortier > wrote: > > unfortunately, aiui, core can't presently be used to build for xen -- as i > said, i think moves are afoot to fix this but it's a non-trivial thing to do > so i don't know what the timeline is (or even if that's explicitly on the > timeline). i don't know core well, but i know at least one issue is that the > threading library (Core.Async) is alike to but not completely compatible > with Lwt. > > others on the list are better placed to comment on if/when Core code will be > usable with Xen :) > > On 10 Sep 2014, at 09:43, Ania Skorupa wrote: > > > Hi, > > thanks for your reply :) I am trying to build a piece of ocaml program in > mirage, which doesn't have a very large codebase. > > from errors, it looks that core is one of the libraries that results in this > error. in the code, I found that Core.Std is opened. Is that a library that > can not be used for xen? skimming through the code, I didn't find explicit > unix dependencies. > > > > On Tuesday, September 9, 2014 6:32 PM, Richard Mortier > wrote: > > > Hi, > > I'd guess so, yes. Anything that depends on the underlying platform (Unix) > needs to be abstracted to work with mirage. > > Specifically, all those modules in the error message have unix dependencies > that aren't being satisfied, though I believe work is ongoing to split js > core up to have a kernel part that will be more compatible with he mirage > approach. > > What are you trying to do? It might be that there are alternative mirage > compatible libraries already available (though that might not help much if > you're looking at porting a large codebase of course :) > > -- > Cheers, > > R. > > > > On 9 Sep 2014, at 19:13, "Ania Skorupa" wrote: > > Hello guys, > > When I compile my mirage application for xen, the following error happens: > > File "_none_", line 1: > Error: No implementations provided for the following modules: > UnixLabels referenced from > /home/user/.opam/system/lib/core/core.cmxa(Core) > Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), > > /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), > > /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), > /home/user/.opam/system/lib/core/core.cmxa(Core) > Command exited with code 2. > > Am I using libraries that can not be used to for xen unikernel? > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > -- > Cheers, > > R. > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message in > error, please send it back to me, and immediately delete it. Please do not > use, copy or disclose the information contained in this message or in any > attachment. Any views or opinions expressed by the author of this email do > not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer system, > you are advised to perform your own checks. Email communications with the > University of Nottingham may be monitored as permitted by UK legislation. > > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Sep 10 15:06:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 10 Sep 2014 15:06: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 1XRjTa-00066r-Fq; Wed, 10 Sep 2014 15:06:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRjTY-00066f-OH for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 15:06:28 +0000 Received: from [85.158.137.68:43577] by server-2.bemta-3.messagelabs.com id 7A/0E-09149-4F860145; Wed, 10 Sep 2014 15:06:28 +0000 X-Env-Sender: yminsky@janestreet.com X-Msg-Ref: server-13.tower-31.messagelabs.com!1410361586!13733170!1 X-Originating-IP: [38.105.200.229] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMzguMTA1LjIwMC4yMjkgPT4gMjA3NjM=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30301 invoked from network); 10 Sep 2014 15:06:27 -0000 Received: from mxout3.mail.janestreet.com (HELO mxout3.mail.janestreet.com) (38.105.200.229) by server-13.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Sep 2014 15:06:27 -0000 Received: from tot-oib-smtp1 ([172.27.22.15] helo=tot-smtp) by mxout3.mail.janestreet.com with esmtps (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XRjTV-0001xH-Vv for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 11:06:26 -0400 Received: from [172.27.229.230] (helo=mxgoog1.mail.janestreet.com) by tot-smtp with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from ) id 1XRjTV-00028k-S2 for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 11:06:25 -0400 Received: from mail-lb0-f182.google.com ([209.85.217.182]) by mxgoog1.mail.janestreet.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1XRjTV-0006Ig-Hf for mirageos-devel@lists.xenproject.org; Wed, 10 Sep 2014 11:06:25 -0400 Received: by mail-lb0-f182.google.com with SMTP id v6so4995878lbi.13 for ; Wed, 10 Sep 2014 08:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zbrkIN67kde04xYlOSf2IEmSPMfGQr/wHx/8gzrhofY=; b=bFJdlakVMdSPujf8JxQkugNihipfTd17n33Myp2pvSTdBq2V3dvZaGTLKY9Fn1/3wE wdrkOMfY5zSqnlG9PLXCL5DgYYze8dEgqWXvf058PzV1N4/dVqfI3mKZgELKCsYhoWNN pZrq19dPV1ora1jJBdw4TnHFEcsyGef3MbOgs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=zbrkIN67kde04xYlOSf2IEmSPMfGQr/wHx/8gzrhofY=; b=Oe8/j9Agodd/o+3TbJajQmAynr5WOEU6bfxtyzHQBnIKecKNJw5JUOwTEwuN89CgvK DmUu5rg19n0cUGZFAJLXxR3cJPdO3GK69fu68oWGFytogtn53gQHea6MzaOYi3XIpa90 rURq+ivIJXiP62prejsLGtcWPqSyUpQXmrsyE8mkxn8YZPaIs/9G1by3aLQXr5u/qZl1 1/BfTgc5p9CjVm9Sdi2SkmMYt8g6HmxC6a7bkw1I3vk3KV+ucdGLb7Ny1e6Rrf345nMO fkTX0PRG4NfiZ7lP+YpR1dDW46daCT3+xMcx0OhlhNTsou1l7bw5VtyKKQZ5GhkiX3Lb Hk2A== X-Gm-Message-State: ALoCoQkJvtJ9BxgUrT35PpU1O4znLgdSCSdOqj+SqdUGl4aREg1iorDbX8nEMG0F0FRu2ZROJsrlNQ5htdOkuBI2DqalirJZEgwXLmRSDv3itMaKCceuOzbbb5qVTiiQIXCigfqspBUx5u0xp8ZJWkpFLYQCQp4ELw== X-Received: by 10.152.28.230 with SMTP id e6mr43052085lah.62.1410361584228; Wed, 10 Sep 2014 08:06:24 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.28.230 with SMTP id e6mr43052070lah.62.1410361584068; Wed, 10 Sep 2014 08:06:24 -0700 (PDT) Received: by 10.112.56.136 with HTTP; Wed, 10 Sep 2014 08:06:23 -0700 (PDT) In-Reply-To: <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> Date: Wed, 10 Sep 2014 11:06:23 -0400 Message-ID: From: Yaron Minsky To: Anil Madhavapeddy Cc: Spiros Eliopoulos , Stephen Weeks , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Wed, Sep 10, 2014 at 10:55 AM, Anil Madhavapeddy wrote: > (Re-adding the devel list to CC) > > The s-expression library is actually independent of Unix, so that's fine. > It's easiest to fork Frenetic in the short term and shift it to using > Core_kernel instead of Core. There will be probably be an Async scheduler, > which is a lot more work to fix. This requires shifting the Async portions > to use Async_kernel instead, which Jane Street is working on. > > CCing Yaron -- any sense of how far away Async_kernel is from a public > release? We can get started on an Async_xen port then as well. CC'ing Sweeks. I think the concrete work is just getting started now. Sweeks, can you come up with a rough estimate? > -anil > > On 10 Sep 2014, at 10:55, Masoud Koleini > wrote: > > Oh, we will have the same problem! > > Frenetic protocol library uses Core, mostly for s-expressions. So far, I was > testing it with unix config to figure out build and controller communication > problems. > > Any idea of how we can make it work for xen? I think we have to modify > Frenetic library to compile on both unix and xen, but try to keep this > modification as light as possible until we have Core ported to Mirage. > > > On 10/09/14 10:33, Anil Madhavapeddy wrote: > > Hi Ania, > > Mort is correct -- we haven't completely finishing porting Core to Mirage. > This requires breaking it down into smaller Unix-free chunks, which the > upstream maintainers (Jane Street) have already started doing. Core > consists of several sub-libraries, of which the Unix-free subset is > Core_kernel. Core_kernel still requires a few minor C stubs (around > Bigarray handling) which should work with the trunk build of Mirage > (untested). > > Overall though, if you're interested in getting on with applications in > Mirage *right now*, you should avoid Core for now. Using Core_kernel is > pretty close though, so I'll take a look at that. > > -anil > > On 10 Sep 2014, at 10:05, Richard Mortier > wrote: > > unfortunately, aiui, core can't presently be used to build for xen -- as i > said, i think moves are afoot to fix this but it's a non-trivial thing to do > so i don't know what the timeline is (or even if that's explicitly on the > timeline). i don't know core well, but i know at least one issue is that the > threading library (Core.Async) is alike to but not completely compatible > with Lwt. > > others on the list are better placed to comment on if/when Core code will be > usable with Xen :) > > On 10 Sep 2014, at 09:43, Ania Skorupa wrote: > > > Hi, > > thanks for your reply :) I am trying to build a piece of ocaml program in > mirage, which doesn't have a very large codebase. > > from errors, it looks that core is one of the libraries that results in this > error. in the code, I found that Core.Std is opened. Is that a library that > can not be used for xen? skimming through the code, I didn't find explicit > unix dependencies. > > > > On Tuesday, September 9, 2014 6:32 PM, Richard Mortier > wrote: > > > Hi, > > I'd guess so, yes. Anything that depends on the underlying platform (Unix) > needs to be abstracted to work with mirage. > > Specifically, all those modules in the error message have unix dependencies > that aren't being satisfied, though I believe work is ongoing to split js > core up to have a kernel part that will be more compatible with he mirage > approach. > > What are you trying to do? It might be that there are alternative mirage > compatible libraries already available (though that might not help much if > you're looking at porting a large codebase of course :) > > -- > Cheers, > > R. > > > > On 9 Sep 2014, at 19:13, "Ania Skorupa" wrote: > > Hello guys, > > When I compile my mirage application for xen, the following error happens: > > File "_none_", line 1: > Error: No implementations provided for the following modules: > UnixLabels referenced from > /home/user/.opam/system/lib/core/core.cmxa(Core) > Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), > > /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), > > /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), > /home/user/.opam/system/lib/core/core.cmxa(Core) > Command exited with code 2. > > Am I using libraries that can not be used to for xen unikernel? > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > > -- > Cheers, > > R. > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message in > error, please send it back to me, and immediately delete it. Please do not > use, copy or disclose the information contained in this message or in any > attachment. Any views or opinions expressed by the author of this email do > not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer system, > you are advised to perform your own checks. Email communications with the > University of Nottingham may be monitored as permitted by UK legislation. > > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 01:54:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 01:54: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 1XRtat-0000Yw-DB; Thu, 11 Sep 2014 01:54:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRtar-0000Yr-Ey for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 01:54:41 +0000 Received: from [85.158.137.68:19329] by server-11.bemta-3.messagelabs.com id C7/4B-01568-0E001145; Thu, 11 Sep 2014 01:54:40 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1410400480!10052790!1 X-Originating-IP: [209.85.212.174] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3529 invoked from network); 11 Sep 2014 01:54:40 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 01:54:40 -0000 Received: by mail-wi0-f174.google.com with SMTP id n3so124460wiv.13 for ; Wed, 10 Sep 2014 18:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1hi4pjdn0PNOrCRMPZQ3W3Z8joLRsx6gF19njdbj310=; b=BJgsYCcqnTU9IiIfs8w64gPLKgvO6YOftKVDEtqoGmKz1drjpWkT5O/DTiSPAA0Hjm E+yWuTwc7WeW6ujOiB4Sbgi0GnUDOjKZdG7kZJLMjevDp5C1zzji0AmtBlCkqPN6drWa ow2iW1J0v1LlH3hdOc2tprJWKMK69z/OUVUiyvJ1sDYkqCXqfW7Il4+9spmDuGy+ste0 Ozj1s35MFyVnQFxS4gJmzELSmg7iTm1IPPb9B0DdhMVW4YfU7t2isiP8zVHJfNrpivGY aBqtH4tz5skWSuHhBzSaLkVKPDbxHHHOGZ/DCliYUf2Z3kPppL9Owf1qSFb09OsqBpLV UV8Q== MIME-Version: 1.0 X-Received: by 10.180.208.51 with SMTP id mb19mr3284786wic.63.1410400479742; Wed, 10 Sep 2014 18:54:39 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Wed, 10 Sep 2014 18:54:39 -0700 (PDT) Date: Wed, 10 Sep 2014 22:54:39 -0300 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0183267104731288967==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0183267104731288967== Content-Type: multipart/alternative; boundary=001a11c38860960f910502c073be --001a11c38860960f910502c073be Content-Type: text/plain; charset=UTF-8 I have a somewhat silly question. Does Xen have access to the on-board GPU and can Mirage access the Graphics Processing Unit to use it as a calculation engine? I am not looking to mine bitcoins but if it is there it might be useful for calculation intensive functions since I will not be using it for openGL graphics. --Stephen --001a11c38860960f910502c073be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have a somewhat silly question. =C2=A0Does Xen have acce= ss to the on-board GPU and can Mirage access the Graphics Processing Unit t= o use it as a calculation engine?

I am not looking to mi= ne bitcoins but if it is there it might be useful for calculation intensive= functions since I will not be using it for openGL graphics.

=
--Stephen
--001a11c38860960f910502c073be-- --===============0183267104731288967== 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 --===============0183267104731288967==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 01:54:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 01:54: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 1XRtat-0000Yw-DB; Thu, 11 Sep 2014 01:54:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRtar-0000Yr-Ey for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 01:54:41 +0000 Received: from [85.158.137.68:19329] by server-11.bemta-3.messagelabs.com id C7/4B-01568-0E001145; Thu, 11 Sep 2014 01:54:40 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1410400480!10052790!1 X-Originating-IP: [209.85.212.174] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3529 invoked from network); 11 Sep 2014 01:54:40 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 01:54:40 -0000 Received: by mail-wi0-f174.google.com with SMTP id n3so124460wiv.13 for ; Wed, 10 Sep 2014 18:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1hi4pjdn0PNOrCRMPZQ3W3Z8joLRsx6gF19njdbj310=; b=BJgsYCcqnTU9IiIfs8w64gPLKgvO6YOftKVDEtqoGmKz1drjpWkT5O/DTiSPAA0Hjm E+yWuTwc7WeW6ujOiB4Sbgi0GnUDOjKZdG7kZJLMjevDp5C1zzji0AmtBlCkqPN6drWa ow2iW1J0v1LlH3hdOc2tprJWKMK69z/OUVUiyvJ1sDYkqCXqfW7Il4+9spmDuGy+ste0 Ozj1s35MFyVnQFxS4gJmzELSmg7iTm1IPPb9B0DdhMVW4YfU7t2isiP8zVHJfNrpivGY aBqtH4tz5skWSuHhBzSaLkVKPDbxHHHOGZ/DCliYUf2Z3kPppL9Owf1qSFb09OsqBpLV UV8Q== MIME-Version: 1.0 X-Received: by 10.180.208.51 with SMTP id mb19mr3284786wic.63.1410400479742; Wed, 10 Sep 2014 18:54:39 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Wed, 10 Sep 2014 18:54:39 -0700 (PDT) Date: Wed, 10 Sep 2014 22:54:39 -0300 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0183267104731288967==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0183267104731288967== Content-Type: multipart/alternative; boundary=001a11c38860960f910502c073be --001a11c38860960f910502c073be Content-Type: text/plain; charset=UTF-8 I have a somewhat silly question. Does Xen have access to the on-board GPU and can Mirage access the Graphics Processing Unit to use it as a calculation engine? I am not looking to mine bitcoins but if it is there it might be useful for calculation intensive functions since I will not be using it for openGL graphics. --Stephen --001a11c38860960f910502c073be Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have a somewhat silly question. =C2=A0Does Xen have acce= ss to the on-board GPU and can Mirage access the Graphics Processing Unit t= o use it as a calculation engine?

I am not looking to mi= ne bitcoins but if it is there it might be useful for calculation intensive= functions since I will not be using it for openGL graphics.

=
--Stephen
--001a11c38860960f910502c073be-- --===============0183267104731288967== 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 --===============0183267104731288967==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 08:18:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 08:18: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 1XRzaY-0000E7-L4; Thu, 11 Sep 2014 08:18:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRzaX-0000E2-Np for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 08:18:45 +0000 Received: from [85.158.143.35:22391] by server-2.bemta-4.messagelabs.com id CB/23-04525-5EA51145; Thu, 11 Sep 2014 08:18:45 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1410423524!13010690!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2916 invoked from network); 11 Sep 2014 08:18:44 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 08:18:44 -0000 Received: by mail-wg0-f48.google.com with SMTP id m15so5571251wgh.31 for ; Thu, 11 Sep 2014 01:18:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OIkQoRw/5Uv0cUhIUNAV232nFUIjVL8t7fB8dVIlgLs=; b=ixNrSorCmjkq6RQy4hjOSGzVqeGMUs0XRXLbYb8mxSmjbz7N781607a3NfbBUoPJri 0yqmRPcll537kpn0CxKqx4R/QaJP69exy8OFh53yBYD4PcvFcg3JFF1yqo6OvkTfH5sW I29q66Q7BJUZn4oKQF2mLHHBDCwbmR7rBMfMs3arZfQmjemNc/t2pDDc8aOGojAI1xJ5 6+1hafwzFjQy/n+tlC93AIt09CoHorvcIlqGuh/Jrav1N0Bku45lbDiBzKu4+AB+Vh2o ntDsZemZkfMqo2Wl5QjLk7Hngo3aWTaSx73JncnbeSIAbVMbZj1TURUE7RkdYqOx1nCo YANQ== X-Received: by 10.194.94.73 with SMTP id da9mr33935117wjb.67.1410423524343; Thu, 11 Sep 2014 01:18:44 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ju1sm362451wjc.1.2014.09.11.01.18.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 01:18:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 11 Sep 2014 09:18:44 +0100 Message-Id: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org 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 have a somewhat silly question. Does Xen have access to the on-board GPU and can Mirage access the Graphics Processing Unit to use it as a calculation engine? > > I am not looking to mine bitcoins but if it is there it might be useful for calculation intensive functions since I will not be using it for openGL graphics. Xen domu can be configured to have direct GPU passthrough and we have SPOC to compile OCaml code to GPU kernels, so I guess the two things can be connected somehow. I'm not sure anyone already done this and how feasible it is, but that could be an interesting try! Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 08:18:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 08:18: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 1XRzaY-0000E7-L4; Thu, 11 Sep 2014 08:18:46 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRzaX-0000E2-Np for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 08:18:45 +0000 Received: from [85.158.143.35:22391] by server-2.bemta-4.messagelabs.com id CB/23-04525-5EA51145; Thu, 11 Sep 2014 08:18:45 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1410423524!13010690!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2916 invoked from network); 11 Sep 2014 08:18:44 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 08:18:44 -0000 Received: by mail-wg0-f48.google.com with SMTP id m15so5571251wgh.31 for ; Thu, 11 Sep 2014 01:18:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OIkQoRw/5Uv0cUhIUNAV232nFUIjVL8t7fB8dVIlgLs=; b=ixNrSorCmjkq6RQy4hjOSGzVqeGMUs0XRXLbYb8mxSmjbz7N781607a3NfbBUoPJri 0yqmRPcll537kpn0CxKqx4R/QaJP69exy8OFh53yBYD4PcvFcg3JFF1yqo6OvkTfH5sW I29q66Q7BJUZn4oKQF2mLHHBDCwbmR7rBMfMs3arZfQmjemNc/t2pDDc8aOGojAI1xJ5 6+1hafwzFjQy/n+tlC93AIt09CoHorvcIlqGuh/Jrav1N0Bku45lbDiBzKu4+AB+Vh2o ntDsZemZkfMqo2Wl5QjLk7Hngo3aWTaSx73JncnbeSIAbVMbZj1TURUE7RkdYqOx1nCo YANQ== X-Received: by 10.194.94.73 with SMTP id da9mr33935117wjb.67.1410423524343; Thu, 11 Sep 2014 01:18:44 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ju1sm362451wjc.1.2014.09.11.01.18.43 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 01:18:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 11 Sep 2014 09:18:44 +0100 Message-Id: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org 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 have a somewhat silly question. Does Xen have access to the on-board GPU and can Mirage access the Graphics Processing Unit to use it as a calculation engine? > > I am not looking to mine bitcoins but if it is there it might be useful for calculation intensive functions since I will not be using it for openGL graphics. Xen domu can be configured to have direct GPU passthrough and we have SPOC to compile OCaml code to GPU kernels, so I guess the two things can be connected somehow. I'm not sure anyone already done this and how feasible it is, but that could be an interesting try! Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 08:42:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 08:42:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRzxO-0001JR-MK; Thu, 11 Sep 2014 08:42:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRzxO-0001JM-7z for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 08:42:22 +0000 Received: from [85.158.139.211:24886] by server-11.bemta-5.messagelabs.com id 7F/2B-11011-D6061145; Thu, 11 Sep 2014 08:42:21 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-9.tower-206.messagelabs.com!1410424939!13788854!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31204 invoked from network); 11 Sep 2014 08:42:20 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-9.tower-206.messagelabs.com with SMTP; 11 Sep 2014 08:42:20 -0000 Received: from [192.168.0.16] (bbcs-167-211.cust.wingo.ch [178.238.167.211]) by smtp.webfaction.com (Postfix) with ESMTP id 6C64C228EA5F; Thu, 11 Sep 2014 08:42:18 +0000 (UTC) Date: Thu, 11 Sep 2014 10:42:17 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Gazagnaire Message-ID: In-Reply-To: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBqZXVkaSwgMTEgc2VwdGVtYnJlIDIwMTQgw6AgMTA6MTgsIFRob21hcyBHYXphZ25haXJl IGEgw6ljcml0IDoKCj4gWGVuIGRvbXUgY2FuIGJlIGNvbmZpZ3VyZWQgdG8gaGF2ZSBkaXJlY3Qg R1BVIHBhc3N0aHJvdWdoIGFuZCAgCgpBcmUgeW91IHJlZmVycmluZyB0byB4ZW4gcGNpIHBhc3N0 aHJvdWdoID8gIAoKSWYgdGhhdCdzIHRoZSBjYXNlIHdobyBwcm92aWRlcyB0aGUgZHJpdmVyID8g YW5kIHRoZSBPcGVuQ0wgb3IgQ1VEQSBsaWJyYXJ5IChzcG9jIG5lZWRzIHRoYXQpID8gT3IgdGhl IE9wZW5HTCBsaWJyYXJ5ID8KCkJlc3QsCgpEYW5pZWwKCgoKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1p cmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0 Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 08:42:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 08:42:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRzxO-0001JR-MK; Thu, 11 Sep 2014 08:42:22 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XRzxO-0001JM-7z for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 08:42:22 +0000 Received: from [85.158.139.211:24886] by server-11.bemta-5.messagelabs.com id 7F/2B-11011-D6061145; Thu, 11 Sep 2014 08:42:21 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-9.tower-206.messagelabs.com!1410424939!13788854!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31204 invoked from network); 11 Sep 2014 08:42:20 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-9.tower-206.messagelabs.com with SMTP; 11 Sep 2014 08:42:20 -0000 Received: from [192.168.0.16] (bbcs-167-211.cust.wingo.ch [178.238.167.211]) by smtp.webfaction.com (Postfix) with ESMTP id 6C64C228EA5F; Thu, 11 Sep 2014 08:42:18 +0000 (UTC) Date: Thu, 11 Sep 2014 10:42:17 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Thomas Gazagnaire Message-ID: In-Reply-To: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org CgpMZSBqZXVkaSwgMTEgc2VwdGVtYnJlIDIwMTQgw6AgMTA6MTgsIFRob21hcyBHYXphZ25haXJl IGEgw6ljcml0IDoKCj4gWGVuIGRvbXUgY2FuIGJlIGNvbmZpZ3VyZWQgdG8gaGF2ZSBkaXJlY3Qg R1BVIHBhc3N0aHJvdWdoIGFuZCAgCgpBcmUgeW91IHJlZmVycmluZyB0byB4ZW4gcGNpIHBhc3N0 aHJvdWdoID8gIAoKSWYgdGhhdCdzIHRoZSBjYXNlIHdobyBwcm92aWRlcyB0aGUgZHJpdmVyID8g YW5kIHRoZSBPcGVuQ0wgb3IgQ1VEQSBsaWJyYXJ5IChzcG9jIG5lZWRzIHRoYXQpID8gT3IgdGhl IE9wZW5HTCBsaWJyYXJ5ID8KCkJlc3QsCgpEYW5pZWwKCgoKX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX18KTWlyYWdlT1MtZGV2ZWwgbWFpbGluZyBsaXN0Ck1p cmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0 Lm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWwK From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 13:07:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 13:07: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 1XS465-0004bp-Ee; Thu, 11 Sep 2014 13:07:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS464-0004bi-1E for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 13:07:36 +0000 Received: from [85.158.137.68:36144] by server-10.bemta-3.messagelabs.com id 3D/61-01456-79E91145; Thu, 11 Sep 2014 13:07:35 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1410440854!13862354!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25162 invoked from network); 11 Sep 2014 13:07:34 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 13:07:34 -0000 Received: by mail-wg0-f51.google.com with SMTP id k14so5170819wgh.10 for ; Thu, 11 Sep 2014 06:07:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zamSY8j0nWJaJiyeiuRTgFvbRAHLdgT0s1dYr4h2Eoo=; b=dj8pIT6p/U36n6lH4JinXJUACYOGLVtarWh/1kwIXy5mdRFnXBCF9qLwd6vusOhdJt +wCOVvpBQUxdLN02evZbzlsaIcJy+/u2usIuO7Y+1geBwupq7mzHrTW7YXOEMxMZv0Jy bhdEtwm1dSp4MFm7fQGy8IzaJ0RIfgzHDQ1Gvz1rvl25PZH2f8dYpsiFubr5Lq2QTCD0 pOBSGdqHZgZm7zzXaKDYZnSczLs+piPYtKR0iRo36raS2C9HErJspo1vfEr7UALqC5ye 3xfZA1CtZaQN6q2zATB4fiA4DaDw6wEmN7Z+AX9OZgzRXwGx99G88/LsYJEfilfWA+Iw DSVg== X-Received: by 10.180.93.130 with SMTP id cu2mr2152531wib.15.1410440851469; Thu, 11 Sep 2014 06:07:31 -0700 (PDT) Received: from ?IPv6:2001:630:212:248:39aa:84ff:d58d:a2c1? ([2001:630:212:248:39aa:84ff:d58d:a2c1]) by mx.google.com with ESMTPSA id a5sm1183607wje.17.2014.09.11.06.07.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 06:07:30 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 11 Sep 2014 14:07:27 +0100 Message-Id: <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> To: =?iso-8859-1?Q?Daniel_B=FCnzli?= X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org 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 >> Xen domu can be configured to have direct GPU passthrough and > > Are you referring to xen pci passthrough ? No GPU passthrough (that's a new feature of Xen apparently). Note: I know nothing about that, just read it on some blogs few months ago. > If that's the case who provides the driver ? and the OpenCL or CUDA library (spoc needs that) ? Or the OpenGL library ? For normal GPU, I think you will have to write your own drivers (or manage to link them with mini-OS where you don't have the libc). But I'm don't know how this work exactly. But hopefully, vGPU will provide more portable front-end drivers that we can use in mini-os, but I have no idea how far we are from that. Dave or Jon (or someone else at Citrix), any input? Best, Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 13:07:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 13:07: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 1XS465-0004bp-Ee; Thu, 11 Sep 2014 13:07:37 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS464-0004bi-1E for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 13:07:36 +0000 Received: from [85.158.137.68:36144] by server-10.bemta-3.messagelabs.com id 3D/61-01456-79E91145; Thu, 11 Sep 2014 13:07:35 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-31.messagelabs.com!1410440854!13862354!1 X-Originating-IP: [74.125.82.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25162 invoked from network); 11 Sep 2014 13:07:34 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-12.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 13:07:34 -0000 Received: by mail-wg0-f51.google.com with SMTP id k14so5170819wgh.10 for ; Thu, 11 Sep 2014 06:07:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zamSY8j0nWJaJiyeiuRTgFvbRAHLdgT0s1dYr4h2Eoo=; b=dj8pIT6p/U36n6lH4JinXJUACYOGLVtarWh/1kwIXy5mdRFnXBCF9qLwd6vusOhdJt +wCOVvpBQUxdLN02evZbzlsaIcJy+/u2usIuO7Y+1geBwupq7mzHrTW7YXOEMxMZv0Jy bhdEtwm1dSp4MFm7fQGy8IzaJ0RIfgzHDQ1Gvz1rvl25PZH2f8dYpsiFubr5Lq2QTCD0 pOBSGdqHZgZm7zzXaKDYZnSczLs+piPYtKR0iRo36raS2C9HErJspo1vfEr7UALqC5ye 3xfZA1CtZaQN6q2zATB4fiA4DaDw6wEmN7Z+AX9OZgzRXwGx99G88/LsYJEfilfWA+Iw DSVg== X-Received: by 10.180.93.130 with SMTP id cu2mr2152531wib.15.1410440851469; Thu, 11 Sep 2014 06:07:31 -0700 (PDT) Received: from ?IPv6:2001:630:212:248:39aa:84ff:d58d:a2c1? ([2001:630:212:248:39aa:84ff:d58d:a2c1]) by mx.google.com with ESMTPSA id a5sm1183607wje.17.2014.09.11.06.07.30 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 06:07:30 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 11 Sep 2014 14:07:27 +0100 Message-Id: <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> To: =?iso-8859-1?Q?Daniel_B=FCnzli?= X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org 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 >> Xen domu can be configured to have direct GPU passthrough and > > Are you referring to xen pci passthrough ? No GPU passthrough (that's a new feature of Xen apparently). Note: I know nothing about that, just read it on some blogs few months ago. > If that's the case who provides the driver ? and the OpenCL or CUDA library (spoc needs that) ? Or the OpenGL library ? For normal GPU, I think you will have to write your own drivers (or manage to link them with mini-OS where you don't have the libc). But I'm don't know how this work exactly. But hopefully, vGPU will provide more portable front-end drivers that we can use in mini-os, but I have no idea how far we are from that. Dave or Jon (or someone else at Citrix), any input? Best, Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 13:32:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 13:32: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 1XS4U5-0000ra-4I; Thu, 11 Sep 2014 13:32:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS4U4-0000rO-Os for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 13:32:24 +0000 Received: from [85.158.137.68:13079] by server-12.bemta-3.messagelabs.com id 5C/0C-01574-864A1145; Thu, 11 Sep 2014 13:32:24 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1410442343!13807585!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20139 invoked from network); 11 Sep 2014 13:32:23 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 13:32:23 -0000 X-IronPort-AV: E=Sophos;i="5.04,505,1406592000"; d="scan'208";a="24678802" From: Dave Scott To: Thomas Gazagnaire Thread-Topic: [MirageOS-devel] Xen access to the GPU Thread-Index: AQHPzWNoeRGIwp3fzkCvBvUg7EEoRpv7dbMAgAAGlICAAEoWgIAABvOA Date: Thu, 11 Sep 2014 13:32:21 +0000 Message-ID: References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> In-Reply-To: <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <05984DF4CD730D4A892156DAE783653F@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 11 Sep 2014, at 14:07, Thomas Gazagnaire wrote: >>> Xen domu can be configured to have direct GPU passthrough and = >> = >> Are you referring to xen pci passthrough ? = > = > No GPU passthrough (that's a new feature of Xen apparently). Note: I know= nothing about that, just read it on some blogs few months ago. > = >> If that's the case who provides the driver ? and the OpenCL or CUDA libr= ary (spoc needs that) ? Or the OpenGL library ? > = > For normal GPU, I think you will have to write your own drivers (or manag= e to link them with mini-OS where you don't have the libc). But I'm don't k= now how this work exactly. > = > But hopefully, vGPU will provide more portable front-end drivers that we = can use in mini-os, but I have no idea how far we are from that. Dave or Jo= n (or someone else at Citrix), any input? There=92s no simple frontend/backend graphics protocol (unfortunately) so w= hen people talk about vGPU they=92re still talking about passing-through so= mething a bit like a custom PCI virtual function. You=92ll still need compl= ex drivers to map OpenGL onto the hardware, typically written by the hardwa= re vendor for Windows (and hopefully Linux, often as a =91binary blob=92) I guess your options are: - focus on hardware which has open-source 3D drivers[1], and port to a mo= re Mirage-y environment=85 perhaps the rPi would be a good target?[2] - take a Linux binary blob from a vendor and see what symbols it needs an= d attempt to build a wrapper (a bit like =91ndiswrapper=92[3]?) Cheers, Dave [1] http://en.wikipedia.org/wiki/Free_and_open-source_graphics_device_driver [2] http://www.raspberrypi.org/a-birthday-present-from-broadcom/ [3] http://en.wikipedia.org/wiki/NDISwrapper _______________________________________________ MirageOS-devel 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 Sep 11 13:32:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 13:32: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 1XS4U5-0000ra-4I; Thu, 11 Sep 2014 13:32:25 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS4U4-0000rO-Os for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 13:32:24 +0000 Received: from [85.158.137.68:13079] by server-12.bemta-3.messagelabs.com id 5C/0C-01574-864A1145; Thu, 11 Sep 2014 13:32:24 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1410442343!13807585!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20139 invoked from network); 11 Sep 2014 13:32:23 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-15.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 13:32:23 -0000 X-IronPort-AV: E=Sophos;i="5.04,505,1406592000"; d="scan'208";a="24678802" From: Dave Scott To: Thomas Gazagnaire Thread-Topic: [MirageOS-devel] Xen access to the GPU Thread-Index: AQHPzWNoeRGIwp3fzkCvBvUg7EEoRpv7dbMAgAAGlICAAEoWgIAABvOA Date: Thu, 11 Sep 2014 13:32:21 +0000 Message-ID: References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> In-Reply-To: <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <05984DF4CD730D4A892156DAE783653F@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 11 Sep 2014, at 14:07, Thomas Gazagnaire wrote: >>> Xen domu can be configured to have direct GPU passthrough and = >> = >> Are you referring to xen pci passthrough ? = > = > No GPU passthrough (that's a new feature of Xen apparently). Note: I know= nothing about that, just read it on some blogs few months ago. > = >> If that's the case who provides the driver ? and the OpenCL or CUDA libr= ary (spoc needs that) ? Or the OpenGL library ? > = > For normal GPU, I think you will have to write your own drivers (or manag= e to link them with mini-OS where you don't have the libc). But I'm don't k= now how this work exactly. > = > But hopefully, vGPU will provide more portable front-end drivers that we = can use in mini-os, but I have no idea how far we are from that. Dave or Jo= n (or someone else at Citrix), any input? There=92s no simple frontend/backend graphics protocol (unfortunately) so w= hen people talk about vGPU they=92re still talking about passing-through so= mething a bit like a custom PCI virtual function. You=92ll still need compl= ex drivers to map OpenGL onto the hardware, typically written by the hardwa= re vendor for Windows (and hopefully Linux, often as a =91binary blob=92) I guess your options are: - focus on hardware which has open-source 3D drivers[1], and port to a mo= re Mirage-y environment=85 perhaps the rPi would be a good target?[2] - take a Linux binary blob from a vendor and see what symbols it needs an= d attempt to build a wrapper (a bit like =91ndiswrapper=92[3]?) Cheers, Dave [1] http://en.wikipedia.org/wiki/Free_and_open-source_graphics_device_driver [2] http://www.raspberrypi.org/a-birthday-present-from-broadcom/ [3] http://en.wikipedia.org/wiki/NDISwrapper _______________________________________________ MirageOS-devel 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 Sep 11 13:59:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 13:59: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 1XS4tw-0002VQ-EU; Thu, 11 Sep 2014 13:59:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS4tv-0002VI-N8 for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 13:59:07 +0000 Received: from [193.109.254.147:3605] by server-14.bemta-14.messagelabs.com id 35/32-18345-BAAA1145; Thu, 11 Sep 2014 13:59:07 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-2.tower-27.messagelabs.com!1410443946!14934706!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20973 invoked from network); 11 Sep 2014 13:59:06 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-2.tower-27.messagelabs.com with SMTP; 11 Sep 2014 13:59:06 -0000 Received: from [192.168.0.16] (bbcs-167-211.cust.wingo.ch [178.238.167.211]) by smtp.webfaction.com (Postfix) with ESMTP id 97F1F59A42F1; Thu, 11 Sep 2014 13:59:03 +0000 (UTC) Date: Thu, 11 Sep 2014 15:59:02 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Dave Scott Message-ID: <0AD6DE2441B74925A3019AE31BFF28FA@erratique.ch> In-Reply-To: References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: Thomas Gazagnaire , "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgamV1ZGksIDExIHNlcHRlbWJyZSAyMDE0IMOgIDE1OjMyLCBEYXZlIFNjb3R0IGEgw6ljcml0 IDoKPiAtIGZvY3VzIG9uIGhhcmR3YXJlIHdoaWNoIGhhcyBvcGVuLXNvdXJjZSAzRCBkcml2ZXJz WzFdLCBhbmQgcG9ydCB0byBhIG1vcmUgTWlyYWdlLXkgZW52aXJvbm1lbnTigKYgcGVyaGFwcyB0 aGUgclBpIHdvdWxkIGJlIGEgZ29vZCB0YXJnZXQ/WzJdCgpBY3R1YWxseSBJIHdhbnRlZCB0byBo YXZlIGEgbG9vayBhdCB0aGF0IGF0IGEgY2VydGFpbiBwb2ludCwgYnV0Li4uIHRpbWUuLi4gQXBw YXJlbnRseSB0aGUgb3BlbiBzb3VyY2UgZHJpdmVyIFsxXSBpcyBzaW1wbHkgYSBtZXNzYWdlIHBh c3Npbmcgc2hpbSB0aGF0IHRhbGtzIHRvIHRoZSBSVE9TIHRoYXQgcnVucyBvbiB0aGUgYnJvYWRj b20gZ3B1LiAgCgpTbyBpbiBteSBuYWl2ZSB2aWV3IGlmIEkgY291bGQganVzdCBsaW5rIHRoZXNl IHRoaW5ncyBpbiB3aXRoIHRoZSBtaXJhZ2Uga2VybmVsIGFuZCBhY2Nlc3MgdGhlIGV4cG9zZWQg R0xFUyBhcGkgdXNpbmcgdGdscyBbMl0gdGhhdCBjb3VsZCBhY3R1YWxseSBkbyBpdC4gIAoKQnR3 LCB3aGF0J3MgdGhlIHN0YXR1cyBvZiBtaXJhZ2Ugb24gdGhlIHJQSSA/ICAKCkRhbmllbAoKUC5T LiBBdCBhIGNlcnRhaW4gcG9pbnQgSSBsb29rZWQgYXQgdHJ5aW5nIHRvIGRvIHRoYXQgdXNpbmcg R29zd2luIFsxXSBleG8ta2VybmVsLiBCdXQgSSBzdG9wcGVkIHRyeWluZyB0byBnZXQgYSB3b3Jr aW5nIGFybSBjcm9zcyBjb21waWxlci4gV291bGQgYmUgbmljZSB0byBiZSBhYmxlIHRvIGJ1bmRs ZSBjcm9zcy1jb21waWxlcnMgaW4gb3BhbSBzd2l0Y2hlcy4KCgpbMV0gaHR0cHM6Ly9naXRodWIu Y29tL3Jhc3BiZXJyeXBpL3VzZXJsYW5kClsyXSBodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJl L3RnbHMKWzNdIGh0dHBzOi8vZ2l0aHViLmNvbS9tcnZuL29jYW1sLXJwaQoKCgpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWls aW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3Rz LnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 13:59:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 13:59: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 1XS4tw-0002VQ-EU; Thu, 11 Sep 2014 13:59:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS4tv-0002VI-N8 for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 13:59:07 +0000 Received: from [193.109.254.147:3605] by server-14.bemta-14.messagelabs.com id 35/32-18345-BAAA1145; Thu, 11 Sep 2014 13:59:07 +0000 X-Env-Sender: daniel.buenzli@erratique.ch X-Msg-Ref: server-2.tower-27.messagelabs.com!1410443946!14934706!1 X-Originating-IP: [74.55.86.74] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNzQuNTUuODYuNzQgPT4gMzA4NTYz\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20973 invoked from network); 11 Sep 2014 13:59:06 -0000 Received: from mail6.webfaction.com (HELO smtp.webfaction.com) (74.55.86.74) by server-2.tower-27.messagelabs.com with SMTP; 11 Sep 2014 13:59:06 -0000 Received: from [192.168.0.16] (bbcs-167-211.cust.wingo.ch [178.238.167.211]) by smtp.webfaction.com (Postfix) with ESMTP id 97F1F59A42F1; Thu, 11 Sep 2014 13:59:03 +0000 (UTC) Date: Thu, 11 Sep 2014 15:59:02 +0200 From: =?utf-8?Q?Daniel_B=C3=BCnzli?= To: Dave Scott Message-ID: <0AD6DE2441B74925A3019AE31BFF28FA@erratique.ch> In-Reply-To: References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> X-Mailer: sparrow 1.6.4 (build 1178) MIME-Version: 1.0 Content-Disposition: inline Cc: Thomas Gazagnaire , "=?utf-8?Q?mirageos-devel=40lists.xenproject.org?=" Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org TGUgamV1ZGksIDExIHNlcHRlbWJyZSAyMDE0IMOgIDE1OjMyLCBEYXZlIFNjb3R0IGEgw6ljcml0 IDoKPiAtIGZvY3VzIG9uIGhhcmR3YXJlIHdoaWNoIGhhcyBvcGVuLXNvdXJjZSAzRCBkcml2ZXJz WzFdLCBhbmQgcG9ydCB0byBhIG1vcmUgTWlyYWdlLXkgZW52aXJvbm1lbnTigKYgcGVyaGFwcyB0 aGUgclBpIHdvdWxkIGJlIGEgZ29vZCB0YXJnZXQ/WzJdCgpBY3R1YWxseSBJIHdhbnRlZCB0byBo YXZlIGEgbG9vayBhdCB0aGF0IGF0IGEgY2VydGFpbiBwb2ludCwgYnV0Li4uIHRpbWUuLi4gQXBw YXJlbnRseSB0aGUgb3BlbiBzb3VyY2UgZHJpdmVyIFsxXSBpcyBzaW1wbHkgYSBtZXNzYWdlIHBh c3Npbmcgc2hpbSB0aGF0IHRhbGtzIHRvIHRoZSBSVE9TIHRoYXQgcnVucyBvbiB0aGUgYnJvYWRj b20gZ3B1LiAgCgpTbyBpbiBteSBuYWl2ZSB2aWV3IGlmIEkgY291bGQganVzdCBsaW5rIHRoZXNl IHRoaW5ncyBpbiB3aXRoIHRoZSBtaXJhZ2Uga2VybmVsIGFuZCBhY2Nlc3MgdGhlIGV4cG9zZWQg R0xFUyBhcGkgdXNpbmcgdGdscyBbMl0gdGhhdCBjb3VsZCBhY3R1YWxseSBkbyBpdC4gIAoKQnR3 LCB3aGF0J3MgdGhlIHN0YXR1cyBvZiBtaXJhZ2Ugb24gdGhlIHJQSSA/ICAKCkRhbmllbAoKUC5T LiBBdCBhIGNlcnRhaW4gcG9pbnQgSSBsb29rZWQgYXQgdHJ5aW5nIHRvIGRvIHRoYXQgdXNpbmcg R29zd2luIFsxXSBleG8ta2VybmVsLiBCdXQgSSBzdG9wcGVkIHRyeWluZyB0byBnZXQgYSB3b3Jr aW5nIGFybSBjcm9zcyBjb21waWxlci4gV291bGQgYmUgbmljZSB0byBiZSBhYmxlIHRvIGJ1bmRs ZSBjcm9zcy1jb21waWxlcnMgaW4gb3BhbSBzd2l0Y2hlcy4KCgpbMV0gaHR0cHM6Ly9naXRodWIu Y29tL3Jhc3BiZXJyeXBpL3VzZXJsYW5kClsyXSBodHRwOi8vZXJyYXRpcXVlLmNoL3NvZnR3YXJl L3RnbHMKWzNdIGh0dHBzOi8vZ2l0aHViLmNvbS9tcnZuL29jYW1sLXJwaQoKCgpfX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWls aW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3Rz LnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 14:26:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 14:26: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 1XS5K4-0005Jk-B2; Thu, 11 Sep 2014 14:26:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS5K3-0005JY-Ea for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 14:26:07 +0000 Received: from [85.158.143.35:4568] by server-2.bemta-4.messagelabs.com id 5C/90-04525-EF0B1145; Thu, 11 Sep 2014 14:26:06 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1410445565!13126650!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8425 invoked from network); 11 Sep 2014 14:26:06 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 14:26:06 -0000 X-IronPort-AV: E=Sophos;i="5.04,506,1406592000"; d="scan'208";a="24681049" From: Dave Scott To: =?Windows-1252?Q?Daniel_B=FCnzli?= Thread-Topic: [MirageOS-devel] Xen access to the GPU Thread-Index: AQHPzWNoeRGIwp3fzkCvBvUg7EEoRpv7dbMAgAAGlICAAEoWgIAABvOAgAAHdwCAAAeLAA== Date: Thu, 11 Sep 2014 14:26:04 +0000 Message-ID: <6A722A6E-FA2F-4FD4-94AB-B9F14A095E18@citrix.com> References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> <0AD6DE2441B74925A3019AE31BFF28FA@erratique.ch> In-Reply-To: <0AD6DE2441B74925A3019AE31BFF28FA@erratique.ch> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 Sep 2014, at 14:59, Daniel B=FCnzli wro= te: > Le jeudi, 11 septembre 2014 =E0 15:32, Dave Scott a =E9crit : >> - focus on hardware which has open-source 3D drivers[1], and port to a m= ore Mirage-y environment=85 perhaps the rPi would be a good target?[2] > = > Actually I wanted to have a look at that at a certain point, but... time.= .. Apparently the open source driver [1] is simply a message passing shim t= hat talks to the RTOS that runs on the broadcom gpu. = > = > So in my naive view if I could just link these things in with the mirage = kernel and access the exposed GLES api using tgls [2] that could actually d= o it. = That does sound plausible to me! > Btw, what's the status of mirage on the rPI ? I think Anil suggested using FreeBSD as a bootloader/host for Mirage on the= rPi (and other devices which don=92t support Xen). G=E1bor P=E1li created = a Mirage FreeBSD kernel module port[1] which takes care of boot and basic h= ardware initialisation (such as turning on the USB network stack). He demoe= d a Mirage web server running within the kernel. I don=92t know the current= state of the project, but I=92d love to see it as a first-class method of = running Mirage applications. Even on hosts which can run Xen, it would be u= seful to be able to pass-through a PCI network or storage device, use the F= reeBSD driver to access it, but then write higher-level protocol code in OC= aml. Cheers, Dave [1] https://wiki.freebsd.org/201210DevSummit?action=3DAttachFile&do=3Dget&t= arget=3Dmirage-kfreebsd.pdf > = > Daniel > = > P.S. At a certain point I looked at trying to do that using Goswin [1] ex= o-kernel. But I stopped trying to get a working arm cross compiler. Would b= e nice to be able to bundle cross-compilers in opam switches. > = > = > [1] https://github.com/raspberrypi/userland > [2] http://erratique.ch/software/tgls > [3] https://github.com/mrvn/ocaml-rpi > = > = > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 14:26:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 14:26: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 1XS5K4-0005Jk-B2; Thu, 11 Sep 2014 14:26:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS5K3-0005JY-Ea for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 14:26:07 +0000 Received: from [85.158.143.35:4568] by server-2.bemta-4.messagelabs.com id 5C/90-04525-EF0B1145; Thu, 11 Sep 2014 14:26:06 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1410445565!13126650!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8425 invoked from network); 11 Sep 2014 14:26:06 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 14:26:06 -0000 X-IronPort-AV: E=Sophos;i="5.04,506,1406592000"; d="scan'208";a="24681049" From: Dave Scott To: =?Windows-1252?Q?Daniel_B=FCnzli?= Thread-Topic: [MirageOS-devel] Xen access to the GPU Thread-Index: AQHPzWNoeRGIwp3fzkCvBvUg7EEoRpv7dbMAgAAGlICAAEoWgIAABvOAgAAHdwCAAAeLAA== Date: Thu, 11 Sep 2014 14:26:04 +0000 Message-ID: <6A722A6E-FA2F-4FD4-94AB-B9F14A095E18@citrix.com> References: <7A7B1079-051B-4201-8717-5320DD3AA369@gazagnaire.org> <671267FD-FB16-4B66-B8E9-7CD57D5919A7@gazagnaire.org> <0AD6DE2441B74925A3019AE31BFF28FA@erratique.ch> In-Reply-To: <0AD6DE2441B74925A3019AE31BFF28FA@erratique.ch> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: MIME-Version: 1.0 X-DLP: AMS1 Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen access to the GPU X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 Sep 2014, at 14:59, Daniel B=FCnzli wro= te: > Le jeudi, 11 septembre 2014 =E0 15:32, Dave Scott a =E9crit : >> - focus on hardware which has open-source 3D drivers[1], and port to a m= ore Mirage-y environment=85 perhaps the rPi would be a good target?[2] > = > Actually I wanted to have a look at that at a certain point, but... time.= .. Apparently the open source driver [1] is simply a message passing shim t= hat talks to the RTOS that runs on the broadcom gpu. = > = > So in my naive view if I could just link these things in with the mirage = kernel and access the exposed GLES api using tgls [2] that could actually d= o it. = That does sound plausible to me! > Btw, what's the status of mirage on the rPI ? I think Anil suggested using FreeBSD as a bootloader/host for Mirage on the= rPi (and other devices which don=92t support Xen). G=E1bor P=E1li created = a Mirage FreeBSD kernel module port[1] which takes care of boot and basic h= ardware initialisation (such as turning on the USB network stack). He demoe= d a Mirage web server running within the kernel. I don=92t know the current= state of the project, but I=92d love to see it as a first-class method of = running Mirage applications. Even on hosts which can run Xen, it would be u= seful to be able to pass-through a PCI network or storage device, use the F= reeBSD driver to access it, but then write higher-level protocol code in OC= aml. Cheers, Dave [1] https://wiki.freebsd.org/201210DevSummit?action=3DAttachFile&do=3Dget&t= arget=3Dmirage-kfreebsd.pdf > = > Daniel > = > P.S. At a certain point I looked at trying to do that using Goswin [1] ex= o-kernel. But I stopped trying to get a working arm cross compiler. Would b= e nice to be able to bundle cross-compilers in opam switches. > = > = > [1] https://github.com/raspberrypi/userland > [2] http://erratique.ch/software/tgls > [3] https://github.com/mrvn/ocaml-rpi > = > = > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 15:41:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 15:41: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 1XS6V9-0002zx-IM; Thu, 11 Sep 2014 15:41:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS6V7-0002zm-IH for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 15:41:37 +0000 Received: from [85.158.143.35:50069] by server-3.bemta-4.messagelabs.com id 8B/0E-06192-0B2C1145; Thu, 11 Sep 2014 15:41:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1410450096!12406526!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4393 invoked from network); 11 Sep 2014 15:41:36 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 15:41:36 -0000 Received: by mail-wi0-f169.google.com with SMTP id cc10so1381190wib.4 for ; Thu, 11 Sep 2014 08:41:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rEbLHLBayFBDvFX3WeYaPKgXQ3MNrObHHVFPsuIsznQ=; b=oeZSD6HkwWfmsQA29Jd+nBdbk+YYTbXPxhizfZEFct9vzsy8ghL32pnyyWk6O1n+cO f2NautOXekXtoTBBoAg2cK+Wlgfqd4kcFXVxtFtYlLmSoUvqgB2eCgudkQucO74SjM4k p1epZbZvk34XbrhPkLd58eGtDZmgDlR9D+24LMqaNtLMexlGUd5YipOTc4XkcwSwenEv F0GToeix5TRu+9kgd0noQL1qPZsze7lR1NwK2LYDJsZxQ2nyWXGTLrNt+f7NVFO7LDs2 W1Zqi1zaTWAUiXO28EZqhhNKQZu79DXqpsh6Ub5IBBaoKv2y0pDXvj5XcRkJJnehUjrX J0eQ== X-Received: by 10.194.84.175 with SMTP id a15mr2819882wjz.12.1410450094301; Thu, 11 Sep 2014 08:41:34 -0700 (PDT) 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 y5sm1583878wje.32.2014.09.11.08.41.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 08:41:33 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <540F3340.2060400@galois.com> Date: Thu, 11 Sep 2014 16:41:31 +0100 Message-Id: <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> References: <540E2C77.6050007@galois.com> <540F3340.2060400@galois.com> To: James Bielman X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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 > Our case is a little unusual in that we want to expose the security label of > > /local/domain/1/name > > as a virtual path: > > /label/local/domain/1/name Is a virtual path a kind of symlink? You don't want to persist it for performance reason? Just trying to understand the use-cases for maybe implementing this natively in Irmin :-) Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 15:41:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 15:41: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 1XS6V9-0002zx-IM; Thu, 11 Sep 2014 15:41:39 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS6V7-0002zm-IH for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 15:41:37 +0000 Received: from [85.158.143.35:50069] by server-3.bemta-4.messagelabs.com id 8B/0E-06192-0B2C1145; Thu, 11 Sep 2014 15:41:36 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1410450096!12406526!1 X-Originating-IP: [209.85.212.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4393 invoked from network); 11 Sep 2014 15:41:36 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 15:41:36 -0000 Received: by mail-wi0-f169.google.com with SMTP id cc10so1381190wib.4 for ; Thu, 11 Sep 2014 08:41:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rEbLHLBayFBDvFX3WeYaPKgXQ3MNrObHHVFPsuIsznQ=; b=oeZSD6HkwWfmsQA29Jd+nBdbk+YYTbXPxhizfZEFct9vzsy8ghL32pnyyWk6O1n+cO f2NautOXekXtoTBBoAg2cK+Wlgfqd4kcFXVxtFtYlLmSoUvqgB2eCgudkQucO74SjM4k p1epZbZvk34XbrhPkLd58eGtDZmgDlR9D+24LMqaNtLMexlGUd5YipOTc4XkcwSwenEv F0GToeix5TRu+9kgd0noQL1qPZsze7lR1NwK2LYDJsZxQ2nyWXGTLrNt+f7NVFO7LDs2 W1Zqi1zaTWAUiXO28EZqhhNKQZu79DXqpsh6Ub5IBBaoKv2y0pDXvj5XcRkJJnehUjrX J0eQ== X-Received: by 10.194.84.175 with SMTP id a15mr2819882wjz.12.1410450094301; Thu, 11 Sep 2014 08:41:34 -0700 (PDT) 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 y5sm1583878wje.32.2014.09.11.08.41.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 08:41:33 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <540F3340.2060400@galois.com> Date: Thu, 11 Sep 2014 16:41:31 +0100 Message-Id: <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> References: <540E2C77.6050007@galois.com> <540F3340.2060400@galois.com> To: James Bielman X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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 > Our case is a little unusual in that we want to expose the security label of > > /local/domain/1/name > > as a virtual path: > > /label/local/domain/1/name Is a virtual path a kind of symlink? You don't want to persist it for performance reason? Just trying to understand the use-cases for maybe implementing this natively in Irmin :-) Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 16:21:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 16:21: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 1XS77v-0006G2-6d; Thu, 11 Sep 2014 16:21:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS77t-0006Fg-Rw for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 16:21:41 +0000 Received: from [85.158.137.68:3885] by server-13.bemta-3.messagelabs.com id 81/5B-01569-51CC1145; Thu, 11 Sep 2014 16:21:41 +0000 X-Env-Sender: jamesjb@galois.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1410452499!13938000!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30917 invoked from network); 11 Sep 2014 16:21:40 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-16.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Sep 2014 16:21:40 -0000 Received: from hurricane.galois.com (hurricane.galois.com [IPv6:2001:4870:e08e:200:5054:ff:fefa:ce41]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id s8BGLVgg031374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 11 Sep 2014 09:21:35 -0700 Received: from [IPv6:2001:4870:e08e:201:e936:26de:188:c929] ([IPv6:2001:4870:e08e:201:e936:26de:188:c929]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id s8BGLV2p009809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 11 Sep 2014 09:21:31 -0700 Message-ID: <5411CC0B.1060603@galois.com> Date: Thu, 11 Sep 2014 09:21:31 -0700 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Thomas Gazagnaire References: <540E2C77.6050007@galois.com> <540F3340.2060400@galois.com> <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> In-Reply-To: <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> X-Spam-Status: No, score=-3.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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 09/11/2014 08:41 AM, Thomas Gazagnaire wrote: >> Our case is a little unusual in that we want to expose the security label of >> >> /local/domain/1/name >> >> as a virtual path: >> >> /label/local/domain/1/name > Is a virtual path a kind of symlink? You don't want to persist it for performance reason? > > Just trying to understand the use-cases for maybe implementing this natively in Irmin :-) > Hi Thomas, If you think of XenStore like a filesystem, it's more like accessing an extended attribute of a node rather than a symlink. In addition to the value stored at "/local/domain/1/name" we also need a way to read and write its security label. Using a virtual file system like "/label" lets us do this without needing to modify the XenStore protocol. One could imagine extensions to the XenStore protocol to make this more explicit, but we're currently using this "/label" solution so protocol changes aren't required. I do think this data should be persisted---my concern is that persisting security labels could raise consistency issues that don't come up when everything is in-memory (because nodes might be created while our security module is disabled or a different policy is loaded, leading to them having missing or inconsistent labels). I suppose this situation is not that different from a policy reload though, so perhaps this is a non-issue. I just need to think about it a bit more. Personally, I don't think any Irmin changes are necessary---my plan is to add either a "label" field or a map of "extended attributes" to XenStore's "node" type and it will be stored like all the other data associated with the node. Then I want a translation within XenStore that routes "/label/X" to "X.label" rather than the usual "X.value". Thanks, James _______________________________________________ MirageOS-devel 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 Sep 11 16:21:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 16:21: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 1XS77v-0006G2-6d; Thu, 11 Sep 2014 16:21:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS77t-0006Fg-Rw for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 16:21:41 +0000 Received: from [85.158.137.68:3885] by server-13.bemta-3.messagelabs.com id 81/5B-01569-51CC1145; Thu, 11 Sep 2014 16:21:41 +0000 X-Env-Sender: jamesjb@galois.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1410452499!13938000!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30917 invoked from network); 11 Sep 2014 16:21:40 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-16.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Sep 2014 16:21:40 -0000 Received: from hurricane.galois.com (hurricane.galois.com [IPv6:2001:4870:e08e:200:5054:ff:fefa:ce41]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id s8BGLVgg031374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 11 Sep 2014 09:21:35 -0700 Received: from [IPv6:2001:4870:e08e:201:e936:26de:188:c929] ([IPv6:2001:4870:e08e:201:e936:26de:188:c929]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id s8BGLV2p009809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 11 Sep 2014 09:21:31 -0700 Message-ID: <5411CC0B.1060603@galois.com> Date: Thu, 11 Sep 2014 09:21:31 -0700 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Thomas Gazagnaire References: <540E2C77.6050007@galois.com> <540F3340.2060400@galois.com> <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> In-Reply-To: <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> X-Spam-Status: No, score=-3.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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 09/11/2014 08:41 AM, Thomas Gazagnaire wrote: >> Our case is a little unusual in that we want to expose the security label of >> >> /local/domain/1/name >> >> as a virtual path: >> >> /label/local/domain/1/name > Is a virtual path a kind of symlink? You don't want to persist it for performance reason? > > Just trying to understand the use-cases for maybe implementing this natively in Irmin :-) > Hi Thomas, If you think of XenStore like a filesystem, it's more like accessing an extended attribute of a node rather than a symlink. In addition to the value stored at "/local/domain/1/name" we also need a way to read and write its security label. Using a virtual file system like "/label" lets us do this without needing to modify the XenStore protocol. One could imagine extensions to the XenStore protocol to make this more explicit, but we're currently using this "/label" solution so protocol changes aren't required. I do think this data should be persisted---my concern is that persisting security labels could raise consistency issues that don't come up when everything is in-memory (because nodes might be created while our security module is disabled or a different policy is loaded, leading to them having missing or inconsistent labels). I suppose this situation is not that different from a policy reload though, so perhaps this is a non-issue. I just need to think about it a bit more. Personally, I don't think any Irmin changes are necessary---my plan is to add either a "label" field or a map of "extended attributes" to XenStore's "node" type and it will be stored like all the other data associated with the node. Then I want a translation within XenStore that routes "/label/X" to "X.label" rather than the usual "X.value". Thanks, James _______________________________________________ MirageOS-devel 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 Sep 11 17:39:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 17:39: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 1XS8LJ-0002L9-5g; Thu, 11 Sep 2014 17:39:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS8LI-0002L4-8t for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 17:39:36 +0000 Received: from [85.158.143.35:64371] by server-1.bemta-4.messagelabs.com id F7/F9-05872-75ED1145; Thu, 11 Sep 2014 17:39:35 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1410457174!8795384!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9824 invoked from network); 11 Sep 2014 17:39:35 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 17:39:35 -0000 Received: by mail-la0-f54.google.com with SMTP id ge10so2858059lab.27 for ; Thu, 11 Sep 2014 10:39:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fpiRSKTCF1aD3qJesl33m3DDsPISgzTLgIQKIB4YNU8=; b=Jq0YSXhWoERTcBYdSHl63EX09N0m+m+iqcLzun0u2vMP8dyjEUvKs8MqLEuV2f/OfZ 5xjA9Vm/9hEB7Pkr8J8nrn59jwdOjqp6+Fvl/88I0j+MhnFRuLPXQhPpEod1WPN2CzHK O26axKTLAAUI8dJKooJ0ENCuF4TCScinfgKG2PMAcpxjrsqErGNSlZqNT+kjw1kOdCjW U8JzbOcUKMr/PUNJOnU0GQIRxd4KDOV/trCvaxDmt+RUNYs+A0jJzxzQleqQzEYoHwCt DbqoJtD/s5g8OVt9tQ0WjAPhYweDGAt1ltf5MwBwX7LVNXZ2hvff+8dB+xaol2jJT79o 6C3A== MIME-Version: 1.0 X-Received: by 10.152.43.50 with SMTP id t18mr2932503lal.25.1410457173859; Thu, 11 Sep 2014 10:39:33 -0700 (PDT) Received: by 10.112.140.73 with HTTP; Thu, 11 Sep 2014 10:39:33 -0700 (PDT) In-Reply-To: <5411CC0B.1060603@galois.com> References: <540E2C77.6050007@galois.com> <540F3340.2060400@galois.com> <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> <5411CC0B.1060603@galois.com> Date: Thu, 11 Sep 2014 18:39:33 +0100 X-Google-Sender-Auth: t3XTmvphrYuKcPl4ep2Qur7T2qo Message-ID: From: David Sheets To: James Bielman Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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 Thu, Sep 11, 2014 at 5:21 PM, James Bielman wrote: > > On 09/11/2014 08:41 AM, Thomas Gazagnaire wrote: >>> Our case is a little unusual in that we want to expose the security label of >>> >>> /local/domain/1/name >>> >>> as a virtual path: >>> >>> /label/local/domain/1/name >> Is a virtual path a kind of symlink? You don't want to persist it for performance reason? >> >> Just trying to understand the use-cases for maybe implementing this natively in Irmin :-) >> > > Hi Thomas, > > If you think of XenStore like a filesystem, it's more like accessing an > extended attribute of a node rather than a symlink. In addition to the > value stored at "/local/domain/1/name" we also need a way to read and > write its security label. > > Using a virtual file system like "/label" lets us do this without > needing to modify the XenStore protocol. One could imagine extensions > to the XenStore protocol to make this more explicit, but we're currently > using this "/label" solution so protocol changes aren't required. > > I do think this data should be persisted---my concern is that persisting > security labels could raise consistency issues that don't come up when > everything is in-memory (because nodes might be created while our > security module is disabled or a different policy is loaded, leading to > them having missing or inconsistent labels). I suppose this situation > is not that different from a policy reload though, so perhaps this is a > non-issue. I just need to think about it a bit more. > > Personally, I don't think any Irmin changes are necessary---my plan is > to add either a "label" field or a map of "extended attributes" to > XenStore's "node" type and it will be stored like all the other data > associated with the node. Then I want a translation within XenStore > that routes "/label/X" to "X.label" rather than the usual "X.value". Hi James, I would like to humbly suggest that you name your virtual root "/label#/" rather than "/label/" for the following reasons: 1. By appending "#", you can now also have a sibling to "/label#/" called "/label" which, when read, can describe the nature of the virtual file system. 2. Receivers of a path like "/label#/X" can know that something funny is going on when they dereference the path by simply looking at the structure of the path to determine where they can find what strangeness awaits them. 3. No extra semantics or work needs to be done immediately to enable these future use cases, simply changing the name of the virtual root is sufficient. 4. The structure of the descriptive node can contain further parameters so that the view into the virtual tree is explicit and configurable. For instance, policy specifics could be included which would help with later reconciliation. Thanks for your consideration, David > Thanks, > James > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 17:39:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 17:39: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 1XS8LJ-0002L9-5g; Thu, 11 Sep 2014 17:39:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XS8LI-0002L4-8t for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 17:39:36 +0000 Received: from [85.158.143.35:64371] by server-1.bemta-4.messagelabs.com id F7/F9-05872-75ED1145; Thu, 11 Sep 2014 17:39:35 +0000 X-Env-Sender: kosmo.zb@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1410457174!8795384!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9824 invoked from network); 11 Sep 2014 17:39:35 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 17:39:35 -0000 Received: by mail-la0-f54.google.com with SMTP id ge10so2858059lab.27 for ; Thu, 11 Sep 2014 10:39:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fpiRSKTCF1aD3qJesl33m3DDsPISgzTLgIQKIB4YNU8=; b=Jq0YSXhWoERTcBYdSHl63EX09N0m+m+iqcLzun0u2vMP8dyjEUvKs8MqLEuV2f/OfZ 5xjA9Vm/9hEB7Pkr8J8nrn59jwdOjqp6+Fvl/88I0j+MhnFRuLPXQhPpEod1WPN2CzHK O26axKTLAAUI8dJKooJ0ENCuF4TCScinfgKG2PMAcpxjrsqErGNSlZqNT+kjw1kOdCjW U8JzbOcUKMr/PUNJOnU0GQIRxd4KDOV/trCvaxDmt+RUNYs+A0jJzxzQleqQzEYoHwCt DbqoJtD/s5g8OVt9tQ0WjAPhYweDGAt1ltf5MwBwX7LVNXZ2hvff+8dB+xaol2jJT79o 6C3A== MIME-Version: 1.0 X-Received: by 10.152.43.50 with SMTP id t18mr2932503lal.25.1410457173859; Thu, 11 Sep 2014 10:39:33 -0700 (PDT) Received: by 10.112.140.73 with HTTP; Thu, 11 Sep 2014 10:39:33 -0700 (PDT) In-Reply-To: <5411CC0B.1060603@galois.com> References: <540E2C77.6050007@galois.com> <540F3340.2060400@galois.com> <6061161E-C0A7-4EAA-91D2-81410581B225@gazagnaire.org> <5411CC0B.1060603@galois.com> Date: Thu, 11 Sep 2014 18:39:33 +0100 X-Google-Sender-Auth: t3XTmvphrYuKcPl4ep2Qur7T2qo Message-ID: From: David Sheets To: James Bielman Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Merging XenStore+MAC X-BeenThere: mirageos-devel@lists.xenproject.org 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 Thu, Sep 11, 2014 at 5:21 PM, James Bielman wrote: > > On 09/11/2014 08:41 AM, Thomas Gazagnaire wrote: >>> Our case is a little unusual in that we want to expose the security label of >>> >>> /local/domain/1/name >>> >>> as a virtual path: >>> >>> /label/local/domain/1/name >> Is a virtual path a kind of symlink? You don't want to persist it for performance reason? >> >> Just trying to understand the use-cases for maybe implementing this natively in Irmin :-) >> > > Hi Thomas, > > If you think of XenStore like a filesystem, it's more like accessing an > extended attribute of a node rather than a symlink. In addition to the > value stored at "/local/domain/1/name" we also need a way to read and > write its security label. > > Using a virtual file system like "/label" lets us do this without > needing to modify the XenStore protocol. One could imagine extensions > to the XenStore protocol to make this more explicit, but we're currently > using this "/label" solution so protocol changes aren't required. > > I do think this data should be persisted---my concern is that persisting > security labels could raise consistency issues that don't come up when > everything is in-memory (because nodes might be created while our > security module is disabled or a different policy is loaded, leading to > them having missing or inconsistent labels). I suppose this situation > is not that different from a policy reload though, so perhaps this is a > non-issue. I just need to think about it a bit more. > > Personally, I don't think any Irmin changes are necessary---my plan is > to add either a "label" field or a map of "extended attributes" to > XenStore's "node" type and it will be stored like all the other data > associated with the node. Then I want a translation within XenStore > that routes "/label/X" to "X.label" rather than the usual "X.value". Hi James, I would like to humbly suggest that you name your virtual root "/label#/" rather than "/label/" for the following reasons: 1. By appending "#", you can now also have a sibling to "/label#/" called "/label" which, when read, can describe the nature of the virtual file system. 2. Receivers of a path like "/label#/X" can know that something funny is going on when they dereference the path by simply looking at the structure of the path to determine where they can find what strangeness awaits them. 3. No extra semantics or work needs to be done immediately to enable these future use cases, simply changing the name of the virtual root is sufficient. 4. The structure of the descriptive node can contain further parameters so that the view into the virtual tree is explicit and configurable. For instance, policy specifics could be included which would help with later reconciliation. Thanks for your consideration, David > Thanks, > James > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 23:04:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 23:04: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 1XSDPG-0007U3-OB; Thu, 11 Sep 2014 23:04:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSDPF-0007Tx-4Z for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 23:04:01 +0000 Received: from [85.158.143.35:14741] by server-1.bemta-4.messagelabs.com id 97/1B-05872-06A22145; Thu, 11 Sep 2014 23:04:00 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1410476639!5235593!1 X-Originating-IP: [74.125.82.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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24735 invoked from network); 11 Sep 2014 23:03:59 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 23:03:59 -0000 Received: by mail-we0-f179.google.com with SMTP id u56so6665328wes.24 for ; Thu, 11 Sep 2014 16:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=09Fn4TrmriGpoIRypaCyI82RP3dr9qzrodbIgRVzUms=; b=ccZIOEEOQQDDu3xtpHy9tguGoWyZg32Vgg3faJSQvp/mVFc9jN1RGZd5ZmBLtP2wMC xJh8aB7MnZLo9S29SD5N99RpZEsvcN4+TlErJ332Zc97IqEPk05XcONxMBjH/6p8Hfw2 nyU98P+Oa83x7pu2u850sR73ElQwEul7Hkx7a0WunA9X+fF7NwJQJHudutLbBtgw+9Km CVIqIM+mfStOYMR2PbWkviaFcrxjIHF4ZyXLUMYn+yncu2h6OaJvFmeXzjNOGjMSUpwL D4hxAeaSq5EF3/0pbaRxHmbhJRi6v9vxlUCOgxbmRDqyEF29R0gQKc9ckaDxwD6d9KLA 7YDQ== MIME-Version: 1.0 X-Received: by 10.194.200.137 with SMTP id js9mr5774602wjc.90.1410476638864; Thu, 11 Sep 2014 16:03:58 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Thu, 11 Sep 2014 16:03:58 -0700 (PDT) Date: Thu, 11 Sep 2014 20:03:58 -0300 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7098092505357235283==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7098092505357235283== Content-Type: multipart/alternative; boundary=047d7bb70c74060bf70502d22fe3 --047d7bb70c74060bf70502d22fe3 Content-Type: text/plain; charset=UTF-8 First I want to say that I feel like I am spamming the Mirage forum with question and not providing any meaningful advancement to the project (yet). I hope as my knowledge of Mirage grows these noobie emails will become fewer. With that I bet the best development platform for Mirage would be some Apple system and a Cubietrunk board. But that layout has a minimum price tag of about $1,300 to $1,500 US dollars. As a budget beginner I have been looking at other options. Since Xen allows installation of multiple operating systems and I would ideally like to be on an ARM system I have slowly worked my way down to the Samsung Chromebook 2 as the perfect solution at only $300 US dollars. If only Xen supported it. I understand the problems with the Chromebook (Samsung has not made it easy to convert this cool 8 core laptop into the ultimate hacktop). But I was wondering if there is still any development legs left in the Chromebook, is anyone still working on it as a platform for Xen? I am including my research here incase anyone else wants to look at the: Samsung Chromebook 2 XE503C12-K01US $300 US dollars * CPU: Samsung Exynos 5 Octa 5420 (8 Core) * SPEED: 1.9GHz Quad A15 / 1.3GHz Quad A7 * LCD SIZE: 11.6" * SYSTEM MEMORY: 4GB * MEMORY: DDR3L (1600MHz) * INCLUDED STORAGE: 16GB * STORAGE TECHNOLOGY: eMMC * LAN: Wireless 802.11a/b/g/n (No built-in NIC, but USB NIC supported) * BATTERY LIFE: Up to 8.0 hours * WEIGHT: 2.65 lbs./1.2 kilos Xen has installation instructions that point out that "*there is no serial port, for this reason you need to boot Xen blindly and wait for Linux in dom0 to start the display for seeing valuable information.*" However there is a kindly provided UART hack that requires some diy soldering skills. And of course there is the problem that the built-in keyboard does not work under Xen (you need to connect a USB keyboard for now) or that you need a USB NIC dongle to get wired internet access (or maybe any internet access). Apart from those simple (tongue in cheek) problems it seems like the ideal development device to run both Linux and Mirage under Xen. I guess a guy can dream of having a Mirage development laptop with 8 cores for $300.00 US dollars. --Stephen --047d7bb70c74060bf70502d22fe3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
First I want to say that I feel like I am spamming the Mir= age forum with question and not providing any meaningful advancement to the= project (yet). =C2=A0I hope as my knowledge of Mirage grows these noobie e= mails will become fewer.

With that I bet the best develo= pment platform for Mirage would be some Apple system and a Cubietrunk board= . =C2=A0But that layout has a minimum price tag of about $1,300 to $1,500 U= S dollars. =C2=A0As a budget beginner I have been looking at other options.= =C2=A0Since Xen allows installation of multiple operating systems and I wo= uld ideally like to be on an ARM system I have slowly worked my way down to= the Samsung Chromebook 2 as the perfect solution at only $300 US dollars. = =C2=A0If only Xen supported it.

I understand the p= roblems with the Chromebook (Samsung has not made it easy to convert this c= ool 8 core laptop into the ultimate hacktop). =C2=A0But I was wondering if = there is still any development legs left in the Chromebook, is anyone still= working on it as a platform for Xen?

I am includi= ng my research here incase anyone else wants to look at the:
* C= PU: Samsung Exynos 5 Octa 5420 (8 Core)
* SPEED: 1.9GHz Quad A15 = / 1.3GHz Quad A7
* LCD SIZE: 11.6"
* SYSTEM MEMORY= : 4GB
* MEMORY: DDR3L (1600MHz)
* INCLUDED STORAGE: 16G= B
* STORAGE TECHNOLOGY: eMMC
* LAN: Wireless 802.11a/b/= g/n (No built-in NIC, but USB NIC supported)
* BATTERY LIFE: Up t= o 8.0 hours
* WEIGHT: 2.65 lbs./1.2 kilos

Xen has installation instructions that point out that &qu= ot;there is no serial port, for this reason you need to boot Xen blindly= and wait for Linux in dom0 to start the display for seeing valuable inform= ation." =C2=A0However there is a kindly provided UART = hack that requires some diy soldering skills.

= And of course there is the problem that the built-in keyboard does not work= under Xen (you need to connect a USB keyboard for now) or that you need a = USB NIC dongle to get wired internet access (or maybe any internet access).=

Apart from those simple (tongue in cheek) problem= s it seems like the ideal development device to run both Linux and Mirage u= nder Xen.

I guess a guy can dream of having a Mira= ge development laptop with 8 cores for $300.00 US dollars.

--Stephen
--047d7bb70c74060bf70502d22fe3-- --===============7098092505357235283== 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 --===============7098092505357235283==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 11 23:04:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 11 Sep 2014 23:04: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 1XSDPG-0007U3-OB; Thu, 11 Sep 2014 23:04:02 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSDPF-0007Tx-4Z for mirageos-devel@lists.xenproject.org; Thu, 11 Sep 2014 23:04:01 +0000 Received: from [85.158.143.35:14741] by server-1.bemta-4.messagelabs.com id 97/1B-05872-06A22145; Thu, 11 Sep 2014 23:04:00 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1410476639!5235593!1 X-Originating-IP: [74.125.82.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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24735 invoked from network); 11 Sep 2014 23:03:59 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Sep 2014 23:03:59 -0000 Received: by mail-we0-f179.google.com with SMTP id u56so6665328wes.24 for ; Thu, 11 Sep 2014 16:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=09Fn4TrmriGpoIRypaCyI82RP3dr9qzrodbIgRVzUms=; b=ccZIOEEOQQDDu3xtpHy9tguGoWyZg32Vgg3faJSQvp/mVFc9jN1RGZd5ZmBLtP2wMC xJh8aB7MnZLo9S29SD5N99RpZEsvcN4+TlErJ332Zc97IqEPk05XcONxMBjH/6p8Hfw2 nyU98P+Oa83x7pu2u850sR73ElQwEul7Hkx7a0WunA9X+fF7NwJQJHudutLbBtgw+9Km CVIqIM+mfStOYMR2PbWkviaFcrxjIHF4ZyXLUMYn+yncu2h6OaJvFmeXzjNOGjMSUpwL D4hxAeaSq5EF3/0pbaRxHmbhJRi6v9vxlUCOgxbmRDqyEF29R0gQKc9ckaDxwD6d9KLA 7YDQ== MIME-Version: 1.0 X-Received: by 10.194.200.137 with SMTP id js9mr5774602wjc.90.1410476638864; Thu, 11 Sep 2014 16:03:58 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Thu, 11 Sep 2014 16:03:58 -0700 (PDT) Date: Thu, 11 Sep 2014 20:03:58 -0300 Message-ID: From: Stephen Mack To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7098092505357235283==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7098092505357235283== Content-Type: multipart/alternative; boundary=047d7bb70c74060bf70502d22fe3 --047d7bb70c74060bf70502d22fe3 Content-Type: text/plain; charset=UTF-8 First I want to say that I feel like I am spamming the Mirage forum with question and not providing any meaningful advancement to the project (yet). I hope as my knowledge of Mirage grows these noobie emails will become fewer. With that I bet the best development platform for Mirage would be some Apple system and a Cubietrunk board. But that layout has a minimum price tag of about $1,300 to $1,500 US dollars. As a budget beginner I have been looking at other options. Since Xen allows installation of multiple operating systems and I would ideally like to be on an ARM system I have slowly worked my way down to the Samsung Chromebook 2 as the perfect solution at only $300 US dollars. If only Xen supported it. I understand the problems with the Chromebook (Samsung has not made it easy to convert this cool 8 core laptop into the ultimate hacktop). But I was wondering if there is still any development legs left in the Chromebook, is anyone still working on it as a platform for Xen? I am including my research here incase anyone else wants to look at the: Samsung Chromebook 2 XE503C12-K01US $300 US dollars * CPU: Samsung Exynos 5 Octa 5420 (8 Core) * SPEED: 1.9GHz Quad A15 / 1.3GHz Quad A7 * LCD SIZE: 11.6" * SYSTEM MEMORY: 4GB * MEMORY: DDR3L (1600MHz) * INCLUDED STORAGE: 16GB * STORAGE TECHNOLOGY: eMMC * LAN: Wireless 802.11a/b/g/n (No built-in NIC, but USB NIC supported) * BATTERY LIFE: Up to 8.0 hours * WEIGHT: 2.65 lbs./1.2 kilos Xen has installation instructions that point out that "*there is no serial port, for this reason you need to boot Xen blindly and wait for Linux in dom0 to start the display for seeing valuable information.*" However there is a kindly provided UART hack that requires some diy soldering skills. And of course there is the problem that the built-in keyboard does not work under Xen (you need to connect a USB keyboard for now) or that you need a USB NIC dongle to get wired internet access (or maybe any internet access). Apart from those simple (tongue in cheek) problems it seems like the ideal development device to run both Linux and Mirage under Xen. I guess a guy can dream of having a Mirage development laptop with 8 cores for $300.00 US dollars. --Stephen --047d7bb70c74060bf70502d22fe3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
First I want to say that I feel like I am spamming the Mir= age forum with question and not providing any meaningful advancement to the= project (yet). =C2=A0I hope as my knowledge of Mirage grows these noobie e= mails will become fewer.

With that I bet the best develo= pment platform for Mirage would be some Apple system and a Cubietrunk board= . =C2=A0But that layout has a minimum price tag of about $1,300 to $1,500 U= S dollars. =C2=A0As a budget beginner I have been looking at other options.= =C2=A0Since Xen allows installation of multiple operating systems and I wo= uld ideally like to be on an ARM system I have slowly worked my way down to= the Samsung Chromebook 2 as the perfect solution at only $300 US dollars. = =C2=A0If only Xen supported it.

I understand the p= roblems with the Chromebook (Samsung has not made it easy to convert this c= ool 8 core laptop into the ultimate hacktop). =C2=A0But I was wondering if = there is still any development legs left in the Chromebook, is anyone still= working on it as a platform for Xen?

I am includi= ng my research here incase anyone else wants to look at the:
* C= PU: Samsung Exynos 5 Octa 5420 (8 Core)
* SPEED: 1.9GHz Quad A15 = / 1.3GHz Quad A7
* LCD SIZE: 11.6"
* SYSTEM MEMORY= : 4GB
* MEMORY: DDR3L (1600MHz)
* INCLUDED STORAGE: 16G= B
* STORAGE TECHNOLOGY: eMMC
* LAN: Wireless 802.11a/b/= g/n (No built-in NIC, but USB NIC supported)
* BATTERY LIFE: Up t= o 8.0 hours
* WEIGHT: 2.65 lbs./1.2 kilos

Xen has installation instructions that point out that &qu= ot;there is no serial port, for this reason you need to boot Xen blindly= and wait for Linux in dom0 to start the display for seeing valuable inform= ation." =C2=A0However there is a kindly provided UART = hack that requires some diy soldering skills.

= And of course there is the problem that the built-in keyboard does not work= under Xen (you need to connect a USB keyboard for now) or that you need a = USB NIC dongle to get wired internet access (or maybe any internet access).=

Apart from those simple (tongue in cheek) problem= s it seems like the ideal development device to run both Linux and Mirage u= nder Xen.

I guess a guy can dream of having a Mira= ge development laptop with 8 cores for $300.00 US dollars.

--Stephen
--047d7bb70c74060bf70502d22fe3-- --===============7098092505357235283== 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 --===============7098092505357235283==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 11:41:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 11:41: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 1XSPEf-0001dN-3S; Fri, 12 Sep 2014 11:41:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSPEe-0001dE-7n for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 11:41:52 +0000 Received: from [85.158.143.35:59443] by server-3.bemta-4.messagelabs.com id 69/1F-06192-FFBD2145; Fri, 12 Sep 2014 11:41:51 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1410522110!6113658!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18549 invoked from network); 12 Sep 2014 11:41:50 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-13.tower-21.messagelabs.com with SMTP; 12 Sep 2014 11:41:50 -0000 Received: (qmail 32324 invoked from network); 12 Sep 2014 11:40:23 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 12 Sep 2014 11:40:23 -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 29828-09 for ; Fri, 12 Sep 2014 12:40:16 +0100 (BST) Received: (qmail 32136 invoked by uid 599); 12 Sep 2014 11:40:16 -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, 12 Sep 2014 12:40:16 +0100 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 1XSPD6-0005yZ-S4; Fri, 12 Sep 2014 12:40:16 +0100 From: Richard Mortier To: Stephen Mack Date: Fri, 12 Sep 2014 12:40:13 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/OflJAjKZX868ATjuLpB6qG5ZHCQ== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7211406512894460894==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7211406512894460894== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Sep 2014, at 00:03, Stephen Mack wrote: > First I want to say that I feel like I am spamming the Mirage forum = with question and not providing any meaningful advancement to the = project (yet). I hope as my knowledge of Mirage grows these noobie = emails will become fewer. no problem! questions are good :) > With that I bet the best development platform for Mirage would be some = Apple system and a Cubietrunk board. But that layout has a minimum = price tag of about $1,300 to $1,500 US dollars. As a budget beginner I = have been looking at other options. =20 fwiw i'd be interested in a discussion of good (portable) mirage = development platforms generally. what do people use? i'm on a macbook = with virtualbox/xen/ubuntu for occasional linux testing but i doubt = that's the ideal... anyone else? --=20 Cheers, R. --Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUEtueAAoJEOLF27JWwSg3LGIP/2rmOd6ZCgRRYyNyvL109upw HFi/nsNriytr6UUOGYIWPT9/10zXpZDw4LEE4I9NIBmPpsPyziVkYedVQaZEmVEJ JdRv+tuxu6YyVmi64UHuPIHjwDBaFqG1jQgDqtEmxJ18r7W6d6fB12a/wpZwa3gU XFurfuNUP6HM73hzmCS/0PJZN/3FQPC49DuvvBZTOXaKZdLqx5VolsSMmZrt1MIB ln1YTzbHji7SLrSFWgBJ9Nv/mWKVeP1br6f1cUYrJeAusGbGkVzvF71w3GMFlPIR AOoprQFPQQ41wopedhbw3Sk3IGk0HpmdDYaKqATDB46RhZyJkIveQW0txAI+irlt VpO4646DJrHjxlK5IAzitY/xWQ5gQq72OpuXDEkDpRg1IC0CjZszQcv7SsOql+ol TuU+A/UQnAMDheHqcIo1V47cuiTuAJjSONVb873A8vE6+IIjqzaa3TMyJV1Zh+15 Nh3KP9B+UzPlolOFXrNI4O62YqSwpW594YkK+V7zsoVBqjLVo/kv6VoF5uAM8xYg ujGkrBVgT3R7+HPLIHck+SjfV8kqg+QDulIVhyDD9IFOV2mSTguPM9sijw/1L3Gp ZEJS0GdAh6CHt5TXHwWtioPH8QRkhh64vcIE1sbTvlbO+EP4l2GDrS3H3UZLThSp vHnLc6pvZZhkzqiimAKu =1Gnz -----END PGP SIGNATURE----- --Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928-- --===============7211406512894460894== 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 --===============7211406512894460894==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 11:41:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 11:41: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 1XSPEf-0001dN-3S; Fri, 12 Sep 2014 11:41:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSPEe-0001dE-7n for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 11:41:52 +0000 Received: from [85.158.143.35:59443] by server-3.bemta-4.messagelabs.com id 69/1F-06192-FFBD2145; Fri, 12 Sep 2014 11:41:51 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1410522110!6113658!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18549 invoked from network); 12 Sep 2014 11:41:50 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-13.tower-21.messagelabs.com with SMTP; 12 Sep 2014 11:41:50 -0000 Received: (qmail 32324 invoked from network); 12 Sep 2014 11:40:23 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 12 Sep 2014 11:40:23 -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 29828-09 for ; Fri, 12 Sep 2014 12:40:16 +0100 (BST) Received: (qmail 32136 invoked by uid 599); 12 Sep 2014 11:40:16 -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, 12 Sep 2014 12:40:16 +0100 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 1XSPD6-0005yZ-S4; Fri, 12 Sep 2014 12:40:16 +0100 From: Richard Mortier To: Stephen Mack Date: Fri, 12 Sep 2014 12:40:13 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/OflJAjKZX868ATjuLpB6qG5ZHCQ== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7211406512894460894==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7211406512894460894== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Sep 2014, at 00:03, Stephen Mack wrote: > First I want to say that I feel like I am spamming the Mirage forum = with question and not providing any meaningful advancement to the = project (yet). I hope as my knowledge of Mirage grows these noobie = emails will become fewer. no problem! questions are good :) > With that I bet the best development platform for Mirage would be some = Apple system and a Cubietrunk board. But that layout has a minimum = price tag of about $1,300 to $1,500 US dollars. As a budget beginner I = have been looking at other options. =20 fwiw i'd be interested in a discussion of good (portable) mirage = development platforms generally. what do people use? i'm on a macbook = with virtualbox/xen/ubuntu for occasional linux testing but i doubt = that's the ideal... anyone else? --=20 Cheers, R. --Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUEtueAAoJEOLF27JWwSg3LGIP/2rmOd6ZCgRRYyNyvL109upw HFi/nsNriytr6UUOGYIWPT9/10zXpZDw4LEE4I9NIBmPpsPyziVkYedVQaZEmVEJ JdRv+tuxu6YyVmi64UHuPIHjwDBaFqG1jQgDqtEmxJ18r7W6d6fB12a/wpZwa3gU XFurfuNUP6HM73hzmCS/0PJZN/3FQPC49DuvvBZTOXaKZdLqx5VolsSMmZrt1MIB ln1YTzbHji7SLrSFWgBJ9Nv/mWKVeP1br6f1cUYrJeAusGbGkVzvF71w3GMFlPIR AOoprQFPQQ41wopedhbw3Sk3IGk0HpmdDYaKqATDB46RhZyJkIveQW0txAI+irlt VpO4646DJrHjxlK5IAzitY/xWQ5gQq72OpuXDEkDpRg1IC0CjZszQcv7SsOql+ol TuU+A/UQnAMDheHqcIo1V47cuiTuAJjSONVb873A8vE6+IIjqzaa3TMyJV1Zh+15 Nh3KP9B+UzPlolOFXrNI4O62YqSwpW594YkK+V7zsoVBqjLVo/kv6VoF5uAM8xYg ujGkrBVgT3R7+HPLIHck+SjfV8kqg+QDulIVhyDD9IFOV2mSTguPM9sijw/1L3Gp ZEJS0GdAh6CHt5TXHwWtioPH8QRkhh64vcIE1sbTvlbO+EP4l2GDrS3H3UZLThSp vHnLc6pvZZhkzqiimAKu =1Gnz -----END PGP SIGNATURE----- --Apple-Mail=_461796B9-9B46-4377-9485-567EF2B71928-- --===============7211406512894460894== 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 --===============7211406512894460894==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 14:13:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 14:13:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRbQ-0006Tk-Ri; Fri, 12 Sep 2014 14:13:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRbQ-0006TZ-1n for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 14:13:32 +0000 Received: from [193.109.254.147:16826] by server-15.bemta-14.messagelabs.com id 6D/91-30948-B8FF2145; Fri, 12 Sep 2014 14:13:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1410531210!15218376!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22989 invoked from network); 12 Sep 2014 14:13:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-27.messagelabs.com with SMTP; 12 Sep 2014 14:13:30 -0000 Received: (qmail 19352 invoked by uid 634); 12 Sep 2014 14:13:29 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 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; Fri, 12 Sep 2014 15:13:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 12 Sep 2014 15:13:28 +0100 Message-Id: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Sep 2014, at 12:40, Richard Mortier wrote: > > On 12 Sep 2014, at 00:03, Stephen Mack wrote: > >> First I want to say that I feel like I am spamming the Mirage forum with question and not providing any meaningful advancement to the project (yet). I hope as my knowledge of Mirage grows these noobie emails will become fewer. > > no problem! questions are good :) Indeed! > >> With that I bet the best development platform for Mirage would be some Apple system and a Cubietrunk board. But that layout has a minimum price tag of about $1,300 to $1,500 US dollars. As a budget beginner I have been looking at other options. > > fwiw i'd be interested in a discussion of good (portable) mirage development platforms generally. what do people use? i'm on a macbook with virtualbox/xen/ubuntu for occasional linux testing but i doubt that's the ideal... > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or Cubietrick) directly as the development environment. We already use a Ubuntu dom0, and so it should just be a matter of Linux kernel configuration to get a desktop up and running from the HDMI port. It would also be *extremely* convenient to be able to do Mirage presentations without having a Mac, by plugging a mouse and projector into the Cubieboard directly :-) -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 Sep 12 14:13:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 14:13:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRbQ-0006Tk-Ri; Fri, 12 Sep 2014 14:13:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRbQ-0006TZ-1n for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 14:13:32 +0000 Received: from [193.109.254.147:16826] by server-15.bemta-14.messagelabs.com id 6D/91-30948-B8FF2145; Fri, 12 Sep 2014 14:13:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1410531210!15218376!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22989 invoked from network); 12 Sep 2014 14:13:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-27.messagelabs.com with SMTP; 12 Sep 2014 14:13:30 -0000 Received: (qmail 19352 invoked by uid 634); 12 Sep 2014 14:13:29 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 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; Fri, 12 Sep 2014 15:13:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 12 Sep 2014 15:13:28 +0100 Message-Id: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Sep 2014, at 12:40, Richard Mortier wrote: > > On 12 Sep 2014, at 00:03, Stephen Mack wrote: > >> First I want to say that I feel like I am spamming the Mirage forum with question and not providing any meaningful advancement to the project (yet). I hope as my knowledge of Mirage grows these noobie emails will become fewer. > > no problem! questions are good :) Indeed! > >> With that I bet the best development platform for Mirage would be some Apple system and a Cubietrunk board. But that layout has a minimum price tag of about $1,300 to $1,500 US dollars. As a budget beginner I have been looking at other options. > > fwiw i'd be interested in a discussion of good (portable) mirage development platforms generally. what do people use? i'm on a macbook with virtualbox/xen/ubuntu for occasional linux testing but i doubt that's the ideal... > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or Cubietrick) directly as the development environment. We already use a Ubuntu dom0, and so it should just be a matter of Linux kernel configuration to get a desktop up and running from the HDMI port. It would also be *extremely* convenient to be able to do Mirage presentations without having a Mac, by plugging a mouse and projector into the Cubieboard directly :-) -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 Sep 12 14:30:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 14:30: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 1XSRrh-000792-LI; Fri, 12 Sep 2014 14:30:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRrg-00078u-95 for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 14:30:20 +0000 Received: from [85.158.139.211:48794] by server-11.bemta-5.messagelabs.com id 79/A9-11011-B7303145; Fri, 12 Sep 2014 14:30:19 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1410532218!10757798!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19498 invoked from network); 12 Sep 2014 14:30:18 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-15.tower-206.messagelabs.com with SMTP; 12 Sep 2014 14:30:18 -0000 Received: (qmail 28208 invoked from network); 12 Sep 2014 14:27:11 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 12 Sep 2014 14:27:11 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 26880-07 for ; Fri, 12 Sep 2014 15:27:04 +0100 (BST) Received: (qmail 28030 invoked by uid 599); 12 Sep 2014 14:27:04 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 12 Sep 2014 15:27:04 +0100 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 1XSRoW-0007ic-8B; Fri, 12 Sep 2014 15:27:04 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Fri, 12 Sep 2014 15:26:53 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/OlZ74e8kfIOGITKGP0QZRt296Zg== Message-ID: References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> In-Reply-To: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4224718828130125913==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4224718828130125913== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Sep 2014, at 15:13, Anil Madhavapeddy wrote: >>> With that I bet the best development platform for Mirage would be = some Apple system and a Cubietrunk board. But that layout has a minimum = price tag of about $1,300 to $1,500 US dollars. As a budget beginner I = have been looking at other options. =20 >>=20 >> fwiw i'd be interested in a discussion of good (portable) mirage = development platforms generally. what do people use? i'm on a macbook = with virtualbox/xen/ubuntu for occasional linux testing but i doubt = that's the ideal... >=20 > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or = Cubietrick) directly as the development environment. >=20 > We already use a Ubuntu dom0, and so it should just be a matter of = Linux kernel configuration to get a desktop up and running from the HDMI = port. It would also be *extremely* convenient to be able to do Mirage = presentations without having a Mac, by plugging a mouse and projector = into the Cubieboard directly :-) time is fleeting(*) though -- how speedy are the CB2/Ts when building? = where's ocaml up to with cross-platform compilation? --=20 Cheers, R. (*) let's dooooo the timewarp agaaaaaain. ahem. --Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUEwKuAAoJEOLF27JWwSg3mqQQAMabFI2a9K/uzwInTxA0YbDo YfKgTwcUiPbKpwgGUCw98bpR25Xm3oYi4v/0YsVPwScOirbk0+IgRFCJ3Y552K73 G7udRu/dfWx7qY0Fq4tat8B0C2eyRktaeEAcocNB4HmXf1GM841DxFo1XfB18OIE gXZfhRTxVfhmbQMqxu04sZKmYvGnpLHLOfNU50NfMlcQ/fAVsirFkNiGqvBtnP8n EC5dHF5i2YUbFH+sMr+JuRZawFNBnlplKb7T+sf4FOndlghMewXq5ZIY8Cfy0sw7 ARtVAWUR5r1z7osRgBfuLatiLInOH/evvKzl9sRPSMIGukTtzwQ5r6JXZBBR0Ru1 yFxyMwlqQTCbybxThWJfo9b9NO2LxzSSaMqCljZR0HXLIjsEjYnyhrfyg4Icqqm9 ywTi4tQeaG6JManzep1Uvm35p8V0p9YGgvCI1Wdgblsg2Pt2fvHhlSiHMrrLcLnz W0U9gBe8636sdkNTBhuYZBuavIYJ1hvaIVJNC0MMGWCIhc+W4xB2x55EKLpbQxn/ 3Jqsyt3rcJk0BaOlUu8zNMi7WZP/xQqDjBIcZ+xorgK9INAGW5EOKs0s83anc99K ZO/m2Jg7aZ3xKGGpx0FJFPh1+V9B3AqiqOOiya4OOH7TDUjRbIUHfB1B5WnWQcsA YtMVVrJ2fgTsnNwKfj0D =6B4K -----END PGP SIGNATURE----- --Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28-- --===============4224718828130125913== 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 --===============4224718828130125913==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 14:30:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 14:30: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 1XSRrh-000792-LI; Fri, 12 Sep 2014 14:30:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRrg-00078u-95 for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 14:30:20 +0000 Received: from [85.158.139.211:48794] by server-11.bemta-5.messagelabs.com id 79/A9-11011-B7303145; Fri, 12 Sep 2014 14:30:19 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1410532218!10757798!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19498 invoked from network); 12 Sep 2014 14:30:18 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-15.tower-206.messagelabs.com with SMTP; 12 Sep 2014 14:30:18 -0000 Received: (qmail 28208 invoked from network); 12 Sep 2014 14:27:11 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 12 Sep 2014 14:27:11 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 26880-07 for ; Fri, 12 Sep 2014 15:27:04 +0100 (BST) Received: (qmail 28030 invoked by uid 599); 12 Sep 2014 14:27:04 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 12 Sep 2014 15:27:04 +0100 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 1XSRoW-0007ic-8B; Fri, 12 Sep 2014 15:27:04 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Fri, 12 Sep 2014 15:26:53 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/OlZ74e8kfIOGITKGP0QZRt296Zg== Message-ID: References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> In-Reply-To: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4224718828130125913==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4224718828130125913== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 12 Sep 2014, at 15:13, Anil Madhavapeddy wrote: >>> With that I bet the best development platform for Mirage would be = some Apple system and a Cubietrunk board. But that layout has a minimum = price tag of about $1,300 to $1,500 US dollars. As a budget beginner I = have been looking at other options. =20 >>=20 >> fwiw i'd be interested in a discussion of good (portable) mirage = development platforms generally. what do people use? i'm on a macbook = with virtualbox/xen/ubuntu for occasional linux testing but i doubt = that's the ideal... >=20 > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or = Cubietrick) directly as the development environment. >=20 > We already use a Ubuntu dom0, and so it should just be a matter of = Linux kernel configuration to get a desktop up and running from the HDMI = port. It would also be *extremely* convenient to be able to do Mirage = presentations without having a Mac, by plugging a mouse and projector = into the Cubieboard directly :-) time is fleeting(*) though -- how speedy are the CB2/Ts when building? = where's ocaml up to with cross-platform compilation? --=20 Cheers, R. (*) let's dooooo the timewarp agaaaaaain. ahem. --Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUEwKuAAoJEOLF27JWwSg3mqQQAMabFI2a9K/uzwInTxA0YbDo YfKgTwcUiPbKpwgGUCw98bpR25Xm3oYi4v/0YsVPwScOirbk0+IgRFCJ3Y552K73 G7udRu/dfWx7qY0Fq4tat8B0C2eyRktaeEAcocNB4HmXf1GM841DxFo1XfB18OIE gXZfhRTxVfhmbQMqxu04sZKmYvGnpLHLOfNU50NfMlcQ/fAVsirFkNiGqvBtnP8n EC5dHF5i2YUbFH+sMr+JuRZawFNBnlplKb7T+sf4FOndlghMewXq5ZIY8Cfy0sw7 ARtVAWUR5r1z7osRgBfuLatiLInOH/evvKzl9sRPSMIGukTtzwQ5r6JXZBBR0Ru1 yFxyMwlqQTCbybxThWJfo9b9NO2LxzSSaMqCljZR0HXLIjsEjYnyhrfyg4Icqqm9 ywTi4tQeaG6JManzep1Uvm35p8V0p9YGgvCI1Wdgblsg2Pt2fvHhlSiHMrrLcLnz W0U9gBe8636sdkNTBhuYZBuavIYJ1hvaIVJNC0MMGWCIhc+W4xB2x55EKLpbQxn/ 3Jqsyt3rcJk0BaOlUu8zNMi7WZP/xQqDjBIcZ+xorgK9INAGW5EOKs0s83anc99K ZO/m2Jg7aZ3xKGGpx0FJFPh1+V9B3AqiqOOiya4OOH7TDUjRbIUHfB1B5WnWQcsA YtMVVrJ2fgTsnNwKfj0D =6B4K -----END PGP SIGNATURE----- --Apple-Mail=_791D0D68-2C26-481E-8554-3C3271DC4A28-- --===============4224718828130125913== 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 --===============4224718828130125913==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 14:32:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 14:32: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 1XSRu1-0007Cr-0L; Fri, 12 Sep 2014 14:32:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRu0-0007Cl-C2 for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 14:32:44 +0000 Received: from [85.158.139.211:25575] by server-4.bemta-5.messagelabs.com id CB/93-10551-B0403145; Fri, 12 Sep 2014 14:32:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1410532363!10758525!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7822 invoked from network); 12 Sep 2014 14:32:43 -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; 12 Sep 2014 14:32:43 -0000 Received: (qmail 2206 invoked by uid 634); 12 Sep 2014 14:32:42 -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; Fri, 12 Sep 2014 15:32:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 12 Sep 2014 15:32:40 +0100 Message-Id: <4196DECE-E447-499E-9411-921D8B9A64EF@recoil.org> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Sep 2014, at 15:26, Richard Mortier wrote: > On 12 Sep 2014, at 15:13, Anil Madhavapeddy wrote: > >>>> With that I bet the best development platform for Mirage would be some Apple system and a Cubietrunk board. But that layout has a minimum price tag of about $1,300 to $1,500 US dollars. As a budget beginner I have been looking at other options. >>> >>> fwiw i'd be interested in a discussion of good (portable) mirage development platforms generally. what do people use? i'm on a macbook with virtualbox/xen/ubuntu for occasional linux testing but i doubt that's the ideal... >> >> I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or Cubietrick) directly as the development environment. >> >> We already use a Ubuntu dom0, and so it should just be a matter of Linux kernel configuration to get a desktop up and running from the HDMI port. It would also be *extremely* convenient to be able to do Mirage presentations without having a Mac, by plugging a mouse and projector into the Cubieboard directly :-) > > time is fleeting(*) though -- how speedy are the CB2/Ts when building? They're just fine. I use one for most of my Xen hacking now, since the ARM/Cubie is so much easier to manage than an x86 Xen server. > where's ocaml up to with cross-platform compilation? It's not there yet. -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 Sep 12 14:32:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 14:32: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 1XSRu1-0007Cr-0L; Fri, 12 Sep 2014 14:32:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSRu0-0007Cl-C2 for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 14:32:44 +0000 Received: from [85.158.139.211:25575] by server-4.bemta-5.messagelabs.com id CB/93-10551-B0403145; Fri, 12 Sep 2014 14:32:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-206.messagelabs.com!1410532363!10758525!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7822 invoked from network); 12 Sep 2014 14:32:43 -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; 12 Sep 2014 14:32:43 -0000 Received: (qmail 2206 invoked by uid 634); 12 Sep 2014 14:32:42 -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; Fri, 12 Sep 2014 15:32:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 12 Sep 2014 15:32:40 +0100 Message-Id: <4196DECE-E447-499E-9411-921D8B9A64EF@recoil.org> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Sep 2014, at 15:26, Richard Mortier wrote: > On 12 Sep 2014, at 15:13, Anil Madhavapeddy wrote: > >>>> With that I bet the best development platform for Mirage would be some Apple system and a Cubietrunk board. But that layout has a minimum price tag of about $1,300 to $1,500 US dollars. As a budget beginner I have been looking at other options. >>> >>> fwiw i'd be interested in a discussion of good (portable) mirage development platforms generally. what do people use? i'm on a macbook with virtualbox/xen/ubuntu for occasional linux testing but i doubt that's the ideal... >> >> I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or Cubietrick) directly as the development environment. >> >> We already use a Ubuntu dom0, and so it should just be a matter of Linux kernel configuration to get a desktop up and running from the HDMI port. It would also be *extremely* convenient to be able to do Mirage presentations without having a Mac, by plugging a mouse and projector into the Cubieboard directly :-) > > time is fleeting(*) though -- how speedy are the CB2/Ts when building? They're just fine. I use one for most of my Xen hacking now, since the ARM/Cubie is so much easier to manage than an x86 Xen server. > where's ocaml up to with cross-platform compilation? It's not there yet. -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 Sep 12 15:12:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 15:12:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSSWR-0000nY-6z; Fri, 12 Sep 2014 15:12:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSSWP-0000nO-OW for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 15:12:25 +0000 Received: from [85.158.137.68:21772] by server-9.bemta-3.messagelabs.com id A9/0E-30790-95D03145; Fri, 12 Sep 2014 15:12:25 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-7.tower-31.messagelabs.com!1410534742!14176419!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1255 invoked from network); 12 Sep 2014 15:12:23 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2014 15:12:23 -0000 Received: by mail-wg0-f45.google.com with SMTP id z12so904334wgg.16 for ; Fri, 12 Sep 2014 08:12:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hm5+bUo8whUhEyBjX5VJDt7Aj3pvb+XEMzrLtVS7jHM=; b=gSTawDt6NwCueEStmBLbh5JJa7zBlIp5nOcOgHLOoDYQlCc+BFPcRSK2eYkMxBjk5g yF7jAdOc7v69egy+SpbttLSHHl7QQO8jpuaGxfqQ+8Ei36/aFytaMbSy05yqOs7GwxaZ MD44ked9t2wlLi5XfZRjZQKmV2mUnVCMiwO3FLCd2FyN4rlQnHxoJQ8SBfHBiZkEVg1q f+myvjmdX4LX7HSVCXuePHjyCUMkC5n8cLvLJV8DnwOuWiwy/q0HHdTBr+rOlweFe2ar Z/nxE/OKrUxAiK9SP/qxOPCYx3GWn0hU8EytEjE3ZPJMHuFe+AeYWjaagjzXqCVB3Sfa FHfA== X-Gm-Message-State: ALoCoQls2SfWSfcylPylrptZnhwj9XtwPM7s7gOdMSnhOuCWyNHGEWj7T8ejZ4wNMXkodhXBusKf MIME-Version: 1.0 X-Received: by 10.194.61.65 with SMTP id n1mr11342485wjr.19.1410534741811; Fri, 12 Sep 2014 08:12:21 -0700 (PDT) Received: by 10.194.100.201 with HTTP; Fri, 12 Sep 2014 08:12:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 12 Sep 2014 11:12:21 -0400 Message-ID: From: Len Maxwell To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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 Hello, On Fri, Sep 12, 2014 at 7:40 AM, Richard Mortier wrote: > fwiw i'd be interested in a discussion of good (portable) mirage development platforms generally. what do people use? i'm on a macbook with virtualbox/xen/ubuntu for occasional linux testing but i doubt that's the ideal... > > anyone else? I recently switched from a laptop to an Intel NUC (DC3217IYE). It's a tiny PC that you buy as a "kit" and add your own mSATA SSD, RAM (up to 16GB), and optional wifi. Working well so far with Ubuntu 14 desktop. (Haven't installed Xen yet, that still runs on the old laptop) -- Len _______________________________________________ MirageOS-devel 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 Sep 12 15:12:34 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 15:12:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSSWR-0000nY-6z; Fri, 12 Sep 2014 15:12:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSSWP-0000nO-OW for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 15:12:25 +0000 Received: from [85.158.137.68:21772] by server-9.bemta-3.messagelabs.com id A9/0E-30790-95D03145; Fri, 12 Sep 2014 15:12:25 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-7.tower-31.messagelabs.com!1410534742!14176419!1 X-Originating-IP: [74.125.82.45] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1255 invoked from network); 12 Sep 2014 15:12:23 -0000 Received: from mail-wg0-f45.google.com (HELO mail-wg0-f45.google.com) (74.125.82.45) by server-7.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 12 Sep 2014 15:12:23 -0000 Received: by mail-wg0-f45.google.com with SMTP id z12so904334wgg.16 for ; Fri, 12 Sep 2014 08:12:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hm5+bUo8whUhEyBjX5VJDt7Aj3pvb+XEMzrLtVS7jHM=; b=gSTawDt6NwCueEStmBLbh5JJa7zBlIp5nOcOgHLOoDYQlCc+BFPcRSK2eYkMxBjk5g yF7jAdOc7v69egy+SpbttLSHHl7QQO8jpuaGxfqQ+8Ei36/aFytaMbSy05yqOs7GwxaZ MD44ked9t2wlLi5XfZRjZQKmV2mUnVCMiwO3FLCd2FyN4rlQnHxoJQ8SBfHBiZkEVg1q f+myvjmdX4LX7HSVCXuePHjyCUMkC5n8cLvLJV8DnwOuWiwy/q0HHdTBr+rOlweFe2ar Z/nxE/OKrUxAiK9SP/qxOPCYx3GWn0hU8EytEjE3ZPJMHuFe+AeYWjaagjzXqCVB3Sfa FHfA== X-Gm-Message-State: ALoCoQls2SfWSfcylPylrptZnhwj9XtwPM7s7gOdMSnhOuCWyNHGEWj7T8ejZ4wNMXkodhXBusKf MIME-Version: 1.0 X-Received: by 10.194.61.65 with SMTP id n1mr11342485wjr.19.1410534741811; Fri, 12 Sep 2014 08:12:21 -0700 (PDT) Received: by 10.194.100.201 with HTTP; Fri, 12 Sep 2014 08:12:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 12 Sep 2014 11:12:21 -0400 Message-ID: From: Len Maxwell To: Richard Mortier Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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 Hello, On Fri, Sep 12, 2014 at 7:40 AM, Richard Mortier wrote: > fwiw i'd be interested in a discussion of good (portable) mirage development platforms generally. what do people use? i'm on a macbook with virtualbox/xen/ubuntu for occasional linux testing but i doubt that's the ideal... > > anyone else? I recently switched from a laptop to an Intel NUC (DC3217IYE). It's a tiny PC that you buy as a "kit" and add your own mSATA SSD, RAM (up to 16GB), and optional wifi. Working well so far with Ubuntu 14 desktop. (Haven't installed Xen yet, that still runs on the old laptop) -- Len _______________________________________________ MirageOS-devel 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 Sep 12 16:18:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 16:18: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 1XSTYE-0003oK-KA; Fri, 12 Sep 2014 16:18:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSTYC-0003oF-Dw for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 16:18:20 +0000 Received: from [85.158.137.68:15911] by server-6.bemta-3.messagelabs.com id 86/DC-29521-ACC13145; Fri, 12 Sep 2014 16:18:18 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1410538698!14170231!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24489 invoked from network); 12 Sep 2014 16:18:18 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-11.tower-31.messagelabs.com with SMTP; 12 Sep 2014 16:18:18 -0000 Received: (qmail 22672 invoked from network); 12 Sep 2014 16:12:41 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 12 Sep 2014 16:12:41 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20402-08 for ; Fri, 12 Sep 2014 17:12:34 +0100 (BST) Received: (qmail 22496 invoked by uid 599); 12 Sep 2014 16:12:34 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 12 Sep 2014 17:12:34 +0100 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 1XSTSg-0002F3-VJ; Fri, 12 Sep 2014 17:12:38 +0100 From: Richard Mortier To: Len Maxwell Date: Fri, 12 Sep 2014 17:12:37 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/OpF7ngO7VwC9cScmA99T1ihSR9g== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6452668188443701099==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6452668188443701099== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 12 Sep 2014, at 16:12, Len Maxwell wrote: > I recently switched from a laptop to an Intel NUC (DC3217IYE). It's a > tiny PC that you buy as a "kit" and add your own mSATA SSD, RAM (up to > 16GB), and optional wifi. Working well so far with Ubuntu 14 desktop. cool-- hadn't come across those... :) -- Cheers, R. --Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUExpAAAoJEOLF27JWwSg3CSwP/jYpz+C6pCAb1saaD3PZEJcY gJBMOqpRfwkny9+85l2Swa7KhHbbeRJGW6RJucyBZFJ9AqKXiWrA+nPfyRDtIJyF mbFvzNxVwLh6wktMf9P1Fb4Ak3vswPsOUVNgUji8AbNNssC8zrtJTBD5OfERMmBs wsqCbY+UIDc2PlO6SIlEoO98Hdfgief5sncthv2JhvPVxEtVBdGR7HnqLdfhnSLL Q/RaSxdAfbZ/gfYpDqHcReyvsAiBRgWfeeRjDc5EmYCCbDCb9iK8yvl2IFMnvD+z +T0AJgTOZEodbseuNFUXdhBIrN5VUTxBcmSLhX4Iem6cufYU6FFaH92pNz1qoRaU v+gHBEMIfctpIr2cGbDBFIj1uAA2YhItW1mXyaBjjixmxIi9ZDLykGuv3/i/2Zj0 CflDero8ekm31PLZtAf+GCvh6Ko+X09NINLXyWHvLKvisBnWjinl6IY45997q0Vs N1jCvx++PhBN+Ww53XbZS4oW81/hmixfSE/y/fteiiP9HFrbGfu9Jkkfbtp8L/OV +vSOcmhieF/oitA8+wMUt48J9Qn62nBLXsVc7HuQaKDIRdTJdCs//PkWe+FMx5MH i+F/M0TGeSYURPdke0xyV4bIDV6C7KNCjMKRUqc5wDhmXbKX0w6JVxDPRlA3eN8J GJOi5q/QbxPM+L6CAIwA =kvEU -----END PGP SIGNATURE----- --Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304-- --===============6452668188443701099== 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 --===============6452668188443701099==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 16:18:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 16:18: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 1XSTYE-0003oK-KA; Fri, 12 Sep 2014 16:18:22 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSTYC-0003oF-Dw for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 16:18:20 +0000 Received: from [85.158.137.68:15911] by server-6.bemta-3.messagelabs.com id 86/DC-29521-ACC13145; Fri, 12 Sep 2014 16:18:18 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-11.tower-31.messagelabs.com!1410538698!14170231!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24489 invoked from network); 12 Sep 2014 16:18:18 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-11.tower-31.messagelabs.com with SMTP; 12 Sep 2014 16:18:18 -0000 Received: (qmail 22672 invoked from network); 12 Sep 2014 16:12:41 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 12 Sep 2014 16:12:41 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20402-08 for ; Fri, 12 Sep 2014 17:12:34 +0100 (BST) Received: (qmail 22496 invoked by uid 599); 12 Sep 2014 16:12:34 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 12 Sep 2014 17:12:34 +0100 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 1XSTSg-0002F3-VJ; Fri, 12 Sep 2014 17:12:38 +0100 From: Richard Mortier To: Len Maxwell Date: Fri, 12 Sep 2014 17:12:37 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/OpF7ngO7VwC9cScmA99T1ihSR9g== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6452668188443701099==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6452668188443701099== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 12 Sep 2014, at 16:12, Len Maxwell wrote: > I recently switched from a laptop to an Intel NUC (DC3217IYE). It's a > tiny PC that you buy as a "kit" and add your own mSATA SSD, RAM (up to > 16GB), and optional wifi. Working well so far with Ubuntu 14 desktop. cool-- hadn't come across those... :) -- Cheers, R. --Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUExpAAAoJEOLF27JWwSg3CSwP/jYpz+C6pCAb1saaD3PZEJcY gJBMOqpRfwkny9+85l2Swa7KhHbbeRJGW6RJucyBZFJ9AqKXiWrA+nPfyRDtIJyF mbFvzNxVwLh6wktMf9P1Fb4Ak3vswPsOUVNgUji8AbNNssC8zrtJTBD5OfERMmBs wsqCbY+UIDc2PlO6SIlEoO98Hdfgief5sncthv2JhvPVxEtVBdGR7HnqLdfhnSLL Q/RaSxdAfbZ/gfYpDqHcReyvsAiBRgWfeeRjDc5EmYCCbDCb9iK8yvl2IFMnvD+z +T0AJgTOZEodbseuNFUXdhBIrN5VUTxBcmSLhX4Iem6cufYU6FFaH92pNz1qoRaU v+gHBEMIfctpIr2cGbDBFIj1uAA2YhItW1mXyaBjjixmxIi9ZDLykGuv3/i/2Zj0 CflDero8ekm31PLZtAf+GCvh6Ko+X09NINLXyWHvLKvisBnWjinl6IY45997q0Vs N1jCvx++PhBN+Ww53XbZS4oW81/hmixfSE/y/fteiiP9HFrbGfu9Jkkfbtp8L/OV +vSOcmhieF/oitA8+wMUt48J9Qn62nBLXsVc7HuQaKDIRdTJdCs//PkWe+FMx5MH i+F/M0TGeSYURPdke0xyV4bIDV6C7KNCjMKRUqc5wDhmXbKX0w6JVxDPRlA3eN8J GJOi5q/QbxPM+L6CAIwA =kvEU -----END PGP SIGNATURE----- --Apple-Mail=_40B93A40-10B5-400C-B043-ABAF47428304-- --===============6452668188443701099== 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 --===============6452668188443701099==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 12 17:32:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 17:32: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 1XSUhY-0006A0-G6; Fri, 12 Sep 2014 17:32:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSUeb-0005zo-2W for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 17:29:01 +0000 Received: from [85.158.139.211:25231] by server-9.bemta-5.messagelabs.com id 6B/77-20744-C5D23145; Fri, 12 Sep 2014 17:29:00 +0000 X-Env-Sender: sweeks@janestreet.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1410542939!6595901!1 X-Originating-IP: [38.105.200.115] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11242 invoked from network); 12 Sep 2014 17:28:59 -0000 Received: from mxout2.mail.janestreet.com (HELO mxout2.mail.janestreet.com) (38.105.200.115) by server-3.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Sep 2014 17:28:59 -0000 Received: from tot-smtp.delacy.com ([172.27.22.15] helo=tot-smtp) by mxout2.mail.janestreet.com with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XSUeY-0002bV-EA for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 13:28:58 -0400 Received: from [172.27.229.230] (helo=mxgoog1.mail.janestreet.com) by tot-smtp with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from ) id 1XSUeY-0006Tn-9B for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 13:28:58 -0400 Received: from mail-vc0-f172.google.com ([209.85.220.172]) by mxgoog1.mail.janestreet.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1XSUeY-000199-58 for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 13:28:58 -0400 Received: by mail-vc0-f172.google.com with SMTP id hy10so1039894vcb.3 for ; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TCHPg4aCKN4NBWWdA3SfT2z/U7SJiBTeHF8Sfa1n0c4=; b=iFrBPJI89oa5cFIYQa0+f0GoJe+Ue3VmsaQK7bhfTZv6r9mFeZchttMMlQLfCv44tP V4LJwkTxMX3tiJ1eRNuteU1vt6aXlnuVQlGo2Z7s+W+anZLzC1/e0qT9iUKt2+FwBfpj 9xAGrKOX8G4dzSgcxWDrxRJ7GBlEbi0X6Cgmg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TCHPg4aCKN4NBWWdA3SfT2z/U7SJiBTeHF8Sfa1n0c4=; b=fN4IPQNvxbHFV+sT+XvVF34uBqIKjwUkJXk1u5HZIq3wy6VY5xQXtGG5Kq3l2pnvUd LpwtYOOw7Wfxopnxw1W1mjjfMDw2XIxd8kvu2ghBb8iaqHgcS3Ft8RgpCtDMecwXfqxF 2cUJjFzUyOA8Rk+FTlcq0IFefWRoZau+e89yD0Pd2xFBQD6jFDSbIckmrQXvomzBeU8C snZbhOq6WwBQnCJUkXwhb04q46C6JFg6Ot2vSg+7VtAjoyCczukueu8h+tPvTtYACsWP gfDvF48CXbefOb5aBl5ryaxhh1pGbFHTid/RGji672bdbngoicKNdTUyp6o21qhiwMUt qfdw== X-Gm-Message-State: ALoCoQk1+JOD8ZluELWi+MtkpGmEng72yqZFWMm+ZObz7rpia9w4Kc98bbGh399VSWQkK91XyNohQyGYtslcrFDsvZC1XLMdgBfY5K9qvinV1EPnOy4OObzWteLqyc87Q064TJUtaiedjxPH5MSw48ijLCBwWjaXsg== X-Received: by 10.220.4.137 with SMTP id 9mr7954006vcr.27.1410542937910; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.220.4.137 with SMTP id 9mr7953990vcr.27.1410542937758; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) Received: by 10.221.44.74 with HTTP; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) In-Reply-To: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> Date: Fri, 12 Sep 2014 13:28:57 -0400 Message-ID: From: Stephen Weeks To: Yaron Minsky X-Mailman-Approved-At: Fri, 12 Sep 2014 17:32:03 +0000 Cc: Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > CC'ing Sweeks. I think the concrete work is just getting started > now. Sweeks, can you come up with a rough estimate? two months. _______________________________________________ MirageOS-devel 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 Sep 12 17:32:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 12 Sep 2014 17:32: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 1XSUhY-0006A0-G6; Fri, 12 Sep 2014 17:32:04 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSUeb-0005zo-2W for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 17:29:01 +0000 Received: from [85.158.139.211:25231] by server-9.bemta-5.messagelabs.com id 6B/77-20744-C5D23145; Fri, 12 Sep 2014 17:29:00 +0000 X-Env-Sender: sweeks@janestreet.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1410542939!6595901!1 X-Originating-IP: [38.105.200.115] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11242 invoked from network); 12 Sep 2014 17:28:59 -0000 Received: from mxout2.mail.janestreet.com (HELO mxout2.mail.janestreet.com) (38.105.200.115) by server-3.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Sep 2014 17:28:59 -0000 Received: from tot-smtp.delacy.com ([172.27.22.15] helo=tot-smtp) by mxout2.mail.janestreet.com with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XSUeY-0002bV-EA for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 13:28:58 -0400 Received: from [172.27.229.230] (helo=mxgoog1.mail.janestreet.com) by tot-smtp with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from ) id 1XSUeY-0006Tn-9B for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 13:28:58 -0400 Received: from mail-vc0-f172.google.com ([209.85.220.172]) by mxgoog1.mail.janestreet.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.72) (envelope-from ) id 1XSUeY-000199-58 for mirageos-devel@lists.xenproject.org; Fri, 12 Sep 2014 13:28:58 -0400 Received: by mail-vc0-f172.google.com with SMTP id hy10so1039894vcb.3 for ; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TCHPg4aCKN4NBWWdA3SfT2z/U7SJiBTeHF8Sfa1n0c4=; b=iFrBPJI89oa5cFIYQa0+f0GoJe+Ue3VmsaQK7bhfTZv6r9mFeZchttMMlQLfCv44tP V4LJwkTxMX3tiJ1eRNuteU1vt6aXlnuVQlGo2Z7s+W+anZLzC1/e0qT9iUKt2+FwBfpj 9xAGrKOX8G4dzSgcxWDrxRJ7GBlEbi0X6Cgmg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=TCHPg4aCKN4NBWWdA3SfT2z/U7SJiBTeHF8Sfa1n0c4=; b=fN4IPQNvxbHFV+sT+XvVF34uBqIKjwUkJXk1u5HZIq3wy6VY5xQXtGG5Kq3l2pnvUd LpwtYOOw7Wfxopnxw1W1mjjfMDw2XIxd8kvu2ghBb8iaqHgcS3Ft8RgpCtDMecwXfqxF 2cUJjFzUyOA8Rk+FTlcq0IFefWRoZau+e89yD0Pd2xFBQD6jFDSbIckmrQXvomzBeU8C snZbhOq6WwBQnCJUkXwhb04q46C6JFg6Ot2vSg+7VtAjoyCczukueu8h+tPvTtYACsWP gfDvF48CXbefOb5aBl5ryaxhh1pGbFHTid/RGji672bdbngoicKNdTUyp6o21qhiwMUt qfdw== X-Gm-Message-State: ALoCoQk1+JOD8ZluELWi+MtkpGmEng72yqZFWMm+ZObz7rpia9w4Kc98bbGh399VSWQkK91XyNohQyGYtslcrFDsvZC1XLMdgBfY5K9qvinV1EPnOy4OObzWteLqyc87Q064TJUtaiedjxPH5MSw48ijLCBwWjaXsg== X-Received: by 10.220.4.137 with SMTP id 9mr7954006vcr.27.1410542937910; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.220.4.137 with SMTP id 9mr7953990vcr.27.1410542937758; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) Received: by 10.221.44.74 with HTTP; Fri, 12 Sep 2014 10:28:57 -0700 (PDT) In-Reply-To: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> Date: Fri, 12 Sep 2014 13:28:57 -0400 Message-ID: From: Stephen Weeks To: Yaron Minsky X-Mailman-Approved-At: Fri, 12 Sep 2014 17:32:03 +0000 Cc: Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > CC'ing Sweeks. I think the concrete work is just getting started > now. Sweeks, can you come up with a rough estimate? two months. _______________________________________________ MirageOS-devel 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 Sep 13 08:39:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 08:39:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSiqt-0003ao-NY; Sat, 13 Sep 2014 08:38:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSiqs-0003aj-K3 for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 08:38:38 +0000 Received: from [193.109.254.147:38954] by server-1.bemta-14.messagelabs.com id EA/DE-24760-D8204145; Sat, 13 Sep 2014 08:38:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-27.messagelabs.com!1410597517!15316300!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7885 invoked from network); 13 Sep 2014 08:38:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-27.messagelabs.com with SMTP; 13 Sep 2014 08:38:37 -0000 Received: (qmail 28133 invoked by uid 634); 13 Sep 2014 08:38: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.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 13 Sep 2014 09:38:32 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 13 Sep 2014 09:38:30 +0100 Message-Id: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> To: Stephen Weeks X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Sep 2014, at 18:28, Stephen Weeks wrote: >> CC'ing Sweeks. I think the concrete work is just getting started >> now. Sweeks, can you come up with a rough estimate? > > two months. Sounds good; meanwhile there's a bunch of things we can get on with in Async code that's intended to be more widely portable, such as moving away from exposing Reader/Writer towards using Pipes for the protocol core. -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 Sep 13 08:39:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 08:39:06 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSiqt-0003ao-NY; Sat, 13 Sep 2014 08:38:39 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSiqs-0003aj-K3 for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 08:38:38 +0000 Received: from [193.109.254.147:38954] by server-1.bemta-14.messagelabs.com id EA/DE-24760-D8204145; Sat, 13 Sep 2014 08:38:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-27.messagelabs.com!1410597517!15316300!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7885 invoked from network); 13 Sep 2014 08:38:37 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-27.messagelabs.com with SMTP; 13 Sep 2014 08:38:37 -0000 Received: (qmail 28133 invoked by uid 634); 13 Sep 2014 08:38: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.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 13 Sep 2014 09:38:32 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 13 Sep 2014 09:38:30 +0100 Message-Id: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> To: Stephen Weeks X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Sep 2014, at 18:28, Stephen Weeks wrote: >> CC'ing Sweeks. I think the concrete work is just getting started >> now. Sweeks, can you come up with a rough estimate? > > two months. Sounds good; meanwhile there's a bunch of things we can get on with in Async code that's intended to be more widely portable, such as moving away from exposing Reader/Writer towards using Pipes for the protocol core. -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 Sep 13 12:08:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 12:08: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 1XSm83-0006BH-WA; Sat, 13 Sep 2014 12:08:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSm82-0006BC-LG for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 12:08:34 +0000 Received: from [85.158.143.35:20752] by server-1.bemta-4.messagelabs.com id DE/B3-05872-2C334145; Sat, 13 Sep 2014 12:08:34 +0000 X-Env-Sender: jac22@cl.cam.ac.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1410610112!9140449!1 X-Originating-IP: [128.232.25.21] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29946 invoked from network); 13 Sep 2014 12:08:33 -0000 Received: from mta1.cl.cam.ac.uk (HELO mta1.cl.cam.ac.uk) (128.232.25.21) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2014 12:08:33 -0000 Received: from ssh-remote-0.cl.cam.ac.uk ([128.232.0.69] helo=cl.cam.ac.uk) by mta1.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1XSm7w-0002Vp-BX; Sat, 13 Sep 2014 13:08:28 +0100 To: Thomas Gazagnaire In-reply-to: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> Comments: In-reply-to Thomas Gazagnaire message dated "Tue, 09 Sep 2014 16:57:43 +0100." MIME-Version: 1.0 Content-ID: <5729.1410610104.1@cl.cam.ac.uk> Date: Sat, 13 Sep 2014 13:08:25 +0100 From: Jon Crowcroft Message-Id: Cc: mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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 v cool here's a (another) possible use case for irmin: http://queue.acm.org/detail.cfm?id=2668154 In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas Gazagn aire typed: >>Hi all, >> >>Lots of people starting asked me about the status of Irmin. As you might have notice, I'vent had much time to spend on Irmin last month, but I plan to fix that. My current priorities are: >> >>1/ make Irmin compiles on the Xen backend of Mirage. https://github.com/mirage/irmin/issues/81 >>This means dropping the dependency to core_kernel (for now on). The external API will not change. >> >>2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80 >>Currently, we only have a JSON API for the low-level stores, and the very partial implementation of the higher-level calls. Needs to complete and document that. >> >>3/ implement a pure-ocaml Git server to be able to at least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15 >>Together with 1/ this will make possible to query the state of a running Mirage unikernel with a simple `git pull ` >> >>4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82 >>Could use Benjamin's rope implementation, that I first need to release properly. >> >>5/ try to come up with a solution to the "unlimited" memory/storage usage issues https://github.com/mirage/irmin/issues/83 >>This is the most uncertain part of the short-term roadmap. I'll need to check again what are the limitation of Git shallow copies and see how we can use them to limit the history size to remember. >> >>There are also few open embarrassing bugs that I want to fix as well (regarding fd leaks ...). >> >>If anyone is interested to help me on any of these topics, please feel free to comment on the related issues on Github -- I'll gladly share the workload. Also, feel free to reply to that email if you think there is any important Imrin features that you think are missing now. >> >>Best, >>Thomas >>_______________________________________________ >>MirageOS-devel mailing list >>MirageOS-devel@lists.xenproject.org >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel cheers jon _______________________________________________ MirageOS-devel 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 Sep 13 12:08:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 12:08: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 1XSm83-0006BH-WA; Sat, 13 Sep 2014 12:08:35 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSm82-0006BC-LG for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 12:08:34 +0000 Received: from [85.158.143.35:20752] by server-1.bemta-4.messagelabs.com id DE/B3-05872-2C334145; Sat, 13 Sep 2014 12:08:34 +0000 X-Env-Sender: jac22@cl.cam.ac.uk X-Msg-Ref: server-16.tower-21.messagelabs.com!1410610112!9140449!1 X-Originating-IP: [128.232.25.21] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29946 invoked from network); 13 Sep 2014 12:08:33 -0000 Received: from mta1.cl.cam.ac.uk (HELO mta1.cl.cam.ac.uk) (128.232.25.21) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2014 12:08:33 -0000 Received: from ssh-remote-0.cl.cam.ac.uk ([128.232.0.69] helo=cl.cam.ac.uk) by mta1.cl.cam.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1XSm7w-0002Vp-BX; Sat, 13 Sep 2014 13:08:28 +0100 To: Thomas Gazagnaire In-reply-to: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> Comments: In-reply-to Thomas Gazagnaire message dated "Tue, 09 Sep 2014 16:57:43 +0100." MIME-Version: 1.0 Content-ID: <5729.1410610104.1@cl.cam.ac.uk> Date: Sat, 13 Sep 2014 13:08:25 +0100 From: Jon Crowcroft Message-Id: Cc: mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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 v cool here's a (another) possible use case for irmin: http://queue.acm.org/detail.cfm?id=2668154 In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas Gazagn aire typed: >>Hi all, >> >>Lots of people starting asked me about the status of Irmin. As you might have notice, I'vent had much time to spend on Irmin last month, but I plan to fix that. My current priorities are: >> >>1/ make Irmin compiles on the Xen backend of Mirage. https://github.com/mirage/irmin/issues/81 >>This means dropping the dependency to core_kernel (for now on). The external API will not change. >> >>2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80 >>Currently, we only have a JSON API for the low-level stores, and the very partial implementation of the higher-level calls. Needs to complete and document that. >> >>3/ implement a pure-ocaml Git server to be able to at least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15 >>Together with 1/ this will make possible to query the state of a running Mirage unikernel with a simple `git pull ` >> >>4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82 >>Could use Benjamin's rope implementation, that I first need to release properly. >> >>5/ try to come up with a solution to the "unlimited" memory/storage usage issues https://github.com/mirage/irmin/issues/83 >>This is the most uncertain part of the short-term roadmap. I'll need to check again what are the limitation of Git shallow copies and see how we can use them to limit the history size to remember. >> >>There are also few open embarrassing bugs that I want to fix as well (regarding fd leaks ...). >> >>If anyone is interested to help me on any of these topics, please feel free to comment on the related issues on Github -- I'll gladly share the workload. Also, feel free to reply to that email if you think there is any important Imrin features that you think are missing now. >> >>Best, >>Thomas >>_______________________________________________ >>MirageOS-devel mailing list >>MirageOS-devel@lists.xenproject.org >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel cheers jon _______________________________________________ MirageOS-devel 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 Sep 13 13:14:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 13:14: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 1XSn9L-0006qS-2M; Sat, 13 Sep 2014 13:13:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSn9J-0006qN-Al for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 13:13:57 +0000 Received: from [193.109.254.147:51365] by server-10.bemta-14.messagelabs.com id C3/1A-01463-41344145; Sat, 13 Sep 2014 13:13:56 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1410614035!15341234!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15500 invoked from network); 13 Sep 2014 13:13:55 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2014 13:13:55 -0000 Received: by mail-wg0-f43.google.com with SMTP id x12so1923438wgg.14 for ; Sat, 13 Sep 2014 06:13:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p8JsuEE9eeGJpaC3427JK+rXR3WltnD5lylcLRg91q8=; b=Y+MsAOASVfDeTGtwjcUFQaOVrSURuItMe+nt21JN8Ca16En32v84ujnkssaxfLOtSk Zoh27tNJOgoHTt5LO37WBLKIstpesO/0yEhH/VdR89D3E35NK0GmgxYCYVyn3TNJw0Kw hVbY2a2wyoyQDQAGuuJEOCQctmVlMQPKz7rGzMVGjoZfaJosqo5ExufLzSHNE57xsf4K 8lEy+gkWhAfDJqr6Xh/IOHqra6go0DuVsrv2QSOOs150wshDTTBm782juMkaq2mtxp8W 4BWLKMAgRnYIDVnlOAeT6bSOBuuZVs/2RzwNaVoTBQDS0bJ6VrUenb/BXcCfaGdzzCMj S+Hw== MIME-Version: 1.0 X-Received: by 10.194.57.237 with SMTP id l13mr19829061wjq.102.1410614034067; Sat, 13 Sep 2014 06:13:54 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Sat, 13 Sep 2014 06:13:54 -0700 (PDT) In-Reply-To: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> Date: Sat, 13 Sep 2014 10:13:54 -0300 Message-ID: From: Stephen Mack To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4855756444730353758==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4855756444730353758== Content-Type: multipart/alternative; boundary=047d7b86c92e6a75e60502f22cbe --047d7b86c92e6a75e60502f22cbe Content-Type: text/plain; charset=UTF-8 On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy wrote: > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or > Cubietrick) directly as the development environment. > I was going down the cubietrunk (cubieboard 3) road but after you buy the board, monitor, keyboard, and mouse additions I ended up with about the same price as the portable laptop style chromebook and you get less hardware CubieTrunk --- Samsung Chromebook * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) * 2 GB memory --- 4 GB * 8 GB storage --- 16 GB Ok so I know that someone has to invest their time and energy to make it happen and to work out all the hardware issues and that is not trivial. So, I assume that the chromebook development is all but dead. Such a same because that would have been a sweet compact mobile system for Xen/Mirage. It even has an HDMI out port that could be used for presentations. P.S. Anil, are there any videos of your recent presentations at the various conferences you have been attending? You are a very gifted orator. --Stephen --047d7b86c92e6a75e60502f22cbe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Sep 12, 2014 at 11:13 AM,= Anil Madhavapeddy=C2=A0<anil@recoil.org>=C2=A0wrote:
I'd suggest an even simpler mode -- just use the $50 Cubieb= oard2 (or Cubietrick) directly as the development environment.

I was going down the cubietrunk (cubieboard 3) road but after you= buy the board, monitor, keyboard, and mouse additions I ended up with abou= t the same price as the portable laptop style chromebook and you get less h= ardware
CubieTrun= k --- Samsung Chromebook
* Dual core 1GHz =C2=A0--- 8 core (4 x 1.9 GHz/4 x 1.3 GHz)
* 2 GB memor= y =C2=A0--- 4 GB
* 8 GB storage --- 16 GB

Ok so I know that someone has to invest their time and energy= to make it happen and to work out all the hardware issues and that is not = trivial. So, I assume that the chromebook development is all but dead. =C2= =A0Such a same because that would have been a sweet compact mobile system f= or Xen/Mirage. =C2=A0It even has an HDMI out port that could be used for pr= esentations.

P.S.= Anil, are there any videos of your recent presentations at the various con= ferences you have been attending? =C2=A0You are a very gifted orator.=C2=A0=

=
--Stephen
<= /div>
--047d7b86c92e6a75e60502f22cbe-- --===============4855756444730353758== 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 --===============4855756444730353758==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 13:14:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 13:14: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 1XSn9L-0006qS-2M; Sat, 13 Sep 2014 13:13:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSn9J-0006qN-Al for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 13:13:57 +0000 Received: from [193.109.254.147:51365] by server-10.bemta-14.messagelabs.com id C3/1A-01463-41344145; Sat, 13 Sep 2014 13:13:56 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1410614035!15341234!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15500 invoked from network); 13 Sep 2014 13:13:55 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2014 13:13:55 -0000 Received: by mail-wg0-f43.google.com with SMTP id x12so1923438wgg.14 for ; Sat, 13 Sep 2014 06:13:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p8JsuEE9eeGJpaC3427JK+rXR3WltnD5lylcLRg91q8=; b=Y+MsAOASVfDeTGtwjcUFQaOVrSURuItMe+nt21JN8Ca16En32v84ujnkssaxfLOtSk Zoh27tNJOgoHTt5LO37WBLKIstpesO/0yEhH/VdR89D3E35NK0GmgxYCYVyn3TNJw0Kw hVbY2a2wyoyQDQAGuuJEOCQctmVlMQPKz7rGzMVGjoZfaJosqo5ExufLzSHNE57xsf4K 8lEy+gkWhAfDJqr6Xh/IOHqra6go0DuVsrv2QSOOs150wshDTTBm782juMkaq2mtxp8W 4BWLKMAgRnYIDVnlOAeT6bSOBuuZVs/2RzwNaVoTBQDS0bJ6VrUenb/BXcCfaGdzzCMj S+Hw== MIME-Version: 1.0 X-Received: by 10.194.57.237 with SMTP id l13mr19829061wjq.102.1410614034067; Sat, 13 Sep 2014 06:13:54 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Sat, 13 Sep 2014 06:13:54 -0700 (PDT) In-Reply-To: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> Date: Sat, 13 Sep 2014 10:13:54 -0300 Message-ID: From: Stephen Mack To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4855756444730353758==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4855756444730353758== Content-Type: multipart/alternative; boundary=047d7b86c92e6a75e60502f22cbe --047d7b86c92e6a75e60502f22cbe Content-Type: text/plain; charset=UTF-8 On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy wrote: > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or > Cubietrick) directly as the development environment. > I was going down the cubietrunk (cubieboard 3) road but after you buy the board, monitor, keyboard, and mouse additions I ended up with about the same price as the portable laptop style chromebook and you get less hardware CubieTrunk --- Samsung Chromebook * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) * 2 GB memory --- 4 GB * 8 GB storage --- 16 GB Ok so I know that someone has to invest their time and energy to make it happen and to work out all the hardware issues and that is not trivial. So, I assume that the chromebook development is all but dead. Such a same because that would have been a sweet compact mobile system for Xen/Mirage. It even has an HDMI out port that could be used for presentations. P.S. Anil, are there any videos of your recent presentations at the various conferences you have been attending? You are a very gifted orator. --Stephen --047d7b86c92e6a75e60502f22cbe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Sep 12, 2014 at 11:13 AM,= Anil Madhavapeddy=C2=A0<anil@recoil.org>=C2=A0wrote:
I'd suggest an even simpler mode -- just use the $50 Cubieb= oard2 (or Cubietrick) directly as the development environment.

I was going down the cubietrunk (cubieboard 3) road but after you= buy the board, monitor, keyboard, and mouse additions I ended up with abou= t the same price as the portable laptop style chromebook and you get less h= ardware
CubieTrun= k --- Samsung Chromebook
* Dual core 1GHz =C2=A0--- 8 core (4 x 1.9 GHz/4 x 1.3 GHz)
* 2 GB memor= y =C2=A0--- 4 GB
* 8 GB storage --- 16 GB

Ok so I know that someone has to invest their time and energy= to make it happen and to work out all the hardware issues and that is not = trivial. So, I assume that the chromebook development is all but dead. =C2= =A0Such a same because that would have been a sweet compact mobile system f= or Xen/Mirage. =C2=A0It even has an HDMI out port that could be used for pr= esentations.

P.S.= Anil, are there any videos of your recent presentations at the various con= ferences you have been attending? =C2=A0You are a very gifted orator.=C2=A0=

=
--Stephen
<= /div>
--047d7b86c92e6a75e60502f22cbe-- --===============4855756444730353758== 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 --===============4855756444730353758==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 13:46:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 13:46:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSneW-00077l-KK; Sat, 13 Sep 2014 13:46:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSneU-00077g-Pv for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 13:46:10 +0000 Received: from [85.158.137.68:54414] by server-11.bemta-3.messagelabs.com id A6/DD-01568-1AA44145; Sat, 13 Sep 2014 13:46:09 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1410615968!11446794!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13583 invoked from network); 13 Sep 2014 13:46:09 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-10.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2014 13:46:09 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from gw-eduroam.dar.cam.ac.uk ([131.111.194.10]:49593 helo=[192.168.99.105]) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XSneR-0005KO-Sr (Exim 4.82_3-c0e5623) (return-path ); Sat, 13 Sep 2014 14:46:07 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Sat, 13 Sep 2014 14:46:07 +0100 Message-Id: <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> To: Stephen Mack X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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 13 Sep 2014, at 14:13, Stephen Mack wrote: > On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy wrote: > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or Cubietrick) directly as the development environment. > > I was going down the cubietrunk (cubieboard 3) road but after you buy the board, monitor, keyboard, and mouse additions I ended up with about the same price as the portable laptop style chromebook and you get less hardware > > CubieTrunk --- Samsung Chromebook > * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) > * 2 GB memory --- 4 GB > * 8 GB storage --- 16 GB > > Ok so I know that someone has to invest their time and energy to make it happen and to work out all the hardware issues and that is not trivial. So, I assume that the chromebook development is all but dead. Such a same because that would have been a sweet compact mobile system for Xen/Mirage. It even has an HDMI out port that could be used for presentations. > > P.S. Anil, are there any videos of your recent presentations at the various conferences you have been attending? You are a very gifted orator. Not quite a presentation but there's a good video interview at http://twit.tv/show/floss-weekly/302 Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 13:46:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 13:46:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSneW-00077l-KK; Sat, 13 Sep 2014 13:46:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSneU-00077g-Pv for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 13:46:10 +0000 Received: from [85.158.137.68:54414] by server-11.bemta-3.messagelabs.com id A6/DD-01568-1AA44145; Sat, 13 Sep 2014 13:46:09 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1410615968!11446794!1 X-Originating-IP: [131.111.8.141] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MSA9PiAxNTQ4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13583 invoked from network); 13 Sep 2014 13:46:09 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-10.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Sep 2014 13:46:09 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from gw-eduroam.dar.cam.ac.uk ([131.111.194.10]:49593 helo=[192.168.99.105]) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XSneR-0005KO-Sr (Exim 4.82_3-c0e5623) (return-path ); Sat, 13 Sep 2014 14:46:07 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Sat, 13 Sep 2014 14:46:07 +0100 Message-Id: <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> To: Stephen Mack X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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 13 Sep 2014, at 14:13, Stephen Mack wrote: > On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy wrote: > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or Cubietrick) directly as the development environment. > > I was going down the cubietrunk (cubieboard 3) road but after you buy the board, monitor, keyboard, and mouse additions I ended up with about the same price as the portable laptop style chromebook and you get less hardware > > CubieTrunk --- Samsung Chromebook > * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) > * 2 GB memory --- 4 GB > * 8 GB storage --- 16 GB > > Ok so I know that someone has to invest their time and energy to make it happen and to work out all the hardware issues and that is not trivial. So, I assume that the chromebook development is all but dead. Such a same because that would have been a sweet compact mobile system for Xen/Mirage. It even has an HDMI out port that could be used for presentations. > > P.S. Anil, are there any videos of your recent presentations at the various conferences you have been attending? You are a very gifted orator. Not quite a presentation but there's a good video interview at http://twit.tv/show/floss-weekly/302 Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 14:01:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 14:01: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 1XSntM-0007NC-Rk; Sat, 13 Sep 2014 14:01:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSntK-0007N7-Sp for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 14:01:31 +0000 Received: from [85.158.143.35:46505] by server-2.bemta-4.messagelabs.com id 19/D5-04525-83E44145; Sat, 13 Sep 2014 14:01:28 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1410616888!12863275!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24665 invoked from network); 13 Sep 2014 14:01:28 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2014 14:01:28 -0000 Received: by mail-wi0-f174.google.com with SMTP id n3so2048110wiv.7 for ; Sat, 13 Sep 2014 07:01:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RN0RVPUE5XTZNpCWy5MteXc0yiDa/bAd9JoqHrvbuk8=; b=kiQ051TbwTbqW7FhT+hnvpr46mIhCtW6AI9w6j7+Bkvxxb0DHB8YZdcJdwaKtE7XLZ npjyMWM6QmpTFGzJKkZCa0cZ6h94/ku/n4Y2xIftNJuDHJnVb0qY4+kYdd0qah7bxadg Afl/U8Sq7R1vUtRyUU9s0M4LqQuV7d37TGHI5g4+aAmpJKHVeODs4iqyunceNEHtwSwg 5mx0apUWvxMPkjiZ6YG+zrercmGDcBLuzJHwnHpuKdER+Ex0XvIqUmGldmoaXvB7fbyX JssMzI6TOxm0phP7KuDdSjsqqwaRIhzjfnJyt3ibeprCCSj+J7DQUmNtzpAc7QG9VMNi l0Qw== MIME-Version: 1.0 X-Received: by 10.194.57.237 with SMTP id l13mr20134128wjq.102.1410616887426; Sat, 13 Sep 2014 07:01:27 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Sat, 13 Sep 2014 07:01:27 -0700 (PDT) In-Reply-To: <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> Date: Sat, 13 Sep 2014 11:01:27 -0300 Message-ID: From: Stephen Mack To: Amir Chaudhry Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8436401894816103310==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8436401894816103310== Content-Type: multipart/alternative; boundary=047d7b86c92e7d44270502f2d6ca --047d7b86c92e7d44270502f2d6ca Content-Type: text/plain; charset=UTF-8 That is the video that captured my attention and started my unikernal adventure. But thanks! On Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhry wrote: > > On 13 Sep 2014, at 14:13, Stephen Mack wrote: > > > On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy > wrote: > > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or > Cubietrick) directly as the development environment. > > > > I was going down the cubietrunk (cubieboard 3) road but after you buy > the board, monitor, keyboard, and mouse additions I ended up with about the > same price as the portable laptop style chromebook and you get less hardware > > > > CubieTrunk --- Samsung Chromebook > > * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) > > * 2 GB memory --- 4 GB > > * 8 GB storage --- 16 GB > > > > Ok so I know that someone has to invest their time and energy to make it > happen and to work out all the hardware issues and that is not trivial. So, > I assume that the chromebook development is all but dead. Such a same > because that would have been a sweet compact mobile system for Xen/Mirage. > It even has an HDMI out port that could be used for presentations. > > > > P.S. Anil, are there any videos of your recent presentations at the > various conferences you have been attending? You are a very gifted orator. > > Not quite a presentation but there's a good video interview at > http://twit.tv/show/floss-weekly/302 > > Amir > > --047d7b86c92e7d44270502f2d6ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That is the video that captured my attention and started m= y unikernal adventure. =C2=A0But thanks!
On Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhr= y <amc79@cam.ac.uk> wrote:
<= div class=3D"HOEnZb">

On 13 Sep 2014, at 14:13, Stephen Mack <smack815@gmail.com> wrote:

> On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (= or Cubietrick) directly as the development environment.
>
> I was going down the cubietrunk (cubieboard 3) road but after you buy = the board, monitor, keyboard, and mouse additions I ended up with about the= same price as the portable laptop style chromebook and you get less hardwa= re
>
> CubieTrunk --- Samsung Chromebook
> * Dual core 1GHz=C2=A0 --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz)
> * 2 GB memory=C2=A0 --- 4 GB
> * 8 GB storage --- 16 GB
>
> Ok so I know that someone has to invest their time and energy to make = it happen and to work out all the hardware issues and that is not trivial. = So, I assume that the chromebook development is all but dead.=C2=A0 Such a = same because that would have been a sweet compact mobile system for Xen/Mir= age.=C2=A0 It even has an HDMI out port that could be used for presentation= s.
>
> P.S. Anil, are there any videos of your recent presentations at the va= rious conferences you have been attending?=C2=A0 You are a very gifted orat= or.

Not quite a presentation but there's a good video interview= at http= ://twit.tv/show/floss-weekly/302

Amir


--047d7b86c92e7d44270502f2d6ca-- --===============8436401894816103310== 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 --===============8436401894816103310==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 14:01:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 14:01: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 1XSntM-0007NC-Rk; Sat, 13 Sep 2014 14:01:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XSntK-0007N7-Sp for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 14:01:31 +0000 Received: from [85.158.143.35:46505] by server-2.bemta-4.messagelabs.com id 19/D5-04525-83E44145; Sat, 13 Sep 2014 14:01:28 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1410616888!12863275!1 X-Originating-IP: [209.85.212.174] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24665 invoked from network); 13 Sep 2014 14:01:28 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Sep 2014 14:01:28 -0000 Received: by mail-wi0-f174.google.com with SMTP id n3so2048110wiv.7 for ; Sat, 13 Sep 2014 07:01:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RN0RVPUE5XTZNpCWy5MteXc0yiDa/bAd9JoqHrvbuk8=; b=kiQ051TbwTbqW7FhT+hnvpr46mIhCtW6AI9w6j7+Bkvxxb0DHB8YZdcJdwaKtE7XLZ npjyMWM6QmpTFGzJKkZCa0cZ6h94/ku/n4Y2xIftNJuDHJnVb0qY4+kYdd0qah7bxadg Afl/U8Sq7R1vUtRyUU9s0M4LqQuV7d37TGHI5g4+aAmpJKHVeODs4iqyunceNEHtwSwg 5mx0apUWvxMPkjiZ6YG+zrercmGDcBLuzJHwnHpuKdER+Ex0XvIqUmGldmoaXvB7fbyX JssMzI6TOxm0phP7KuDdSjsqqwaRIhzjfnJyt3ibeprCCSj+J7DQUmNtzpAc7QG9VMNi l0Qw== MIME-Version: 1.0 X-Received: by 10.194.57.237 with SMTP id l13mr20134128wjq.102.1410616887426; Sat, 13 Sep 2014 07:01:27 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Sat, 13 Sep 2014 07:01:27 -0700 (PDT) In-Reply-To: <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> Date: Sat, 13 Sep 2014 11:01:27 -0300 Message-ID: From: Stephen Mack To: Amir Chaudhry Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8436401894816103310==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8436401894816103310== Content-Type: multipart/alternative; boundary=047d7b86c92e7d44270502f2d6ca --047d7b86c92e7d44270502f2d6ca Content-Type: text/plain; charset=UTF-8 That is the video that captured my attention and started my unikernal adventure. But thanks! On Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhry wrote: > > On 13 Sep 2014, at 14:13, Stephen Mack wrote: > > > On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy > wrote: > > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or > Cubietrick) directly as the development environment. > > > > I was going down the cubietrunk (cubieboard 3) road but after you buy > the board, monitor, keyboard, and mouse additions I ended up with about the > same price as the portable laptop style chromebook and you get less hardware > > > > CubieTrunk --- Samsung Chromebook > > * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) > > * 2 GB memory --- 4 GB > > * 8 GB storage --- 16 GB > > > > Ok so I know that someone has to invest their time and energy to make it > happen and to work out all the hardware issues and that is not trivial. So, > I assume that the chromebook development is all but dead. Such a same > because that would have been a sweet compact mobile system for Xen/Mirage. > It even has an HDMI out port that could be used for presentations. > > > > P.S. Anil, are there any videos of your recent presentations at the > various conferences you have been attending? You are a very gifted orator. > > Not quite a presentation but there's a good video interview at > http://twit.tv/show/floss-weekly/302 > > Amir > > --047d7b86c92e7d44270502f2d6ca Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That is the video that captured my attention and started m= y unikernal adventure. =C2=A0But thanks!
On Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhr= y <amc79@cam.ac.uk> wrote:
<= div class=3D"HOEnZb">

On 13 Sep 2014, at 14:13, Stephen Mack <smack815@gmail.com> wrote:

> On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (= or Cubietrick) directly as the development environment.
>
> I was going down the cubietrunk (cubieboard 3) road but after you buy = the board, monitor, keyboard, and mouse additions I ended up with about the= same price as the portable laptop style chromebook and you get less hardwa= re
>
> CubieTrunk --- Samsung Chromebook
> * Dual core 1GHz=C2=A0 --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz)
> * 2 GB memory=C2=A0 --- 4 GB
> * 8 GB storage --- 16 GB
>
> Ok so I know that someone has to invest their time and energy to make = it happen and to work out all the hardware issues and that is not trivial. = So, I assume that the chromebook development is all but dead.=C2=A0 Such a = same because that would have been a sweet compact mobile system for Xen/Mir= age.=C2=A0 It even has an HDMI out port that could be used for presentation= s.
>
> P.S. Anil, are there any videos of your recent presentations at the va= rious conferences you have been attending?=C2=A0 You are a very gifted orat= or.

Not quite a presentation but there's a good video interview= at http= ://twit.tv/show/floss-weekly/302

Amir


--047d7b86c92e7d44270502f2d6ca-- --===============8436401894816103310== 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 --===============8436401894816103310==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 15:38:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 15:38: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 1XSpPU-0008KZ-Fw; Sat, 13 Sep 2014 15: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 1XSpPT-0008KU-8C for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 15:38:47 +0000 Received: from [193.109.254.147:17090] by server-9.bemta-14.messagelabs.com id 0B/B9-31535-60564145; Sat, 13 Sep 2014 15:38:46 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-27.messagelabs.com!1410622725!15337813!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 630 invoked from network); 13 Sep 2014 15:38:45 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-10.tower-27.messagelabs.com with SMTP; 13 Sep 2014 15:38:45 -0000 Received: (qmail 13479 invoked from network); 13 Sep 2014 15:38:44 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 13 Sep 2014 15:38:44 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 10336-07 for ; Sat, 13 Sep 2014 16:38:37 +0100 (BST) Received: (qmail 13383 invoked by uid 599); 13 Sep 2014 15:38:37 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 13 Sep 2014 16:38:37 +0100 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 1XSpPI-0001TG-PI; Sat, 13 Sep 2014 16:38:36 +0100 From: Richard Mortier To: Stephen Mack Date: Sat, 13 Sep 2014 16:37:57 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/PaMg7+Oud0Y14Rx2eRS/hwJL8Lw== Message-ID: <33F6C4E9-5A8A-4966-93C8-6FBAD39E8340@nottingham.ac.uk> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Anil Madhavapeddy , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1260345107971259397==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1260345107971259397== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4 Content-Type: multipart/alternative; boundary="Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16" --Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii oscon have the oscon 14 talk videos online now i believe, but it might = be that you need to pay for access...=20 On 13 Sep 2014, at 15:01, Stephen Mack wrote: > That is the video that captured my attention and started my unikernal = adventure. But thanks! >=20 > On Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhry = wrote: >=20 > On 13 Sep 2014, at 14:13, Stephen Mack wrote: >=20 > > On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy = wrote: > > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or = Cubietrick) directly as the development environment. > > > > I was going down the cubietrunk (cubieboard 3) road but after you = buy the board, monitor, keyboard, and mouse additions I ended up with = about the same price as the portable laptop style chromebook and you get = less hardware > > > > CubieTrunk --- Samsung Chromebook > > * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) > > * 2 GB memory --- 4 GB > > * 8 GB storage --- 16 GB > > > > Ok so I know that someone has to invest their time and energy to = make it happen and to work out all the hardware issues and that is not = trivial. So, I assume that the chromebook development is all but dead. = Such a same because that would have been a sweet compact mobile system = for Xen/Mirage. It even has an HDMI out port that could be used for = presentations. > > > > P.S. Anil, are there any videos of your recent presentations at the = various conferences you have been attending? You are a very gifted = orator. >=20 > Not quite a presentation but there's a good video interview at = http://twit.tv/show/floss-weekly/302 >=20 > Amir >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --=20 Cheers, R. --Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii oscon = have the oscon 14 talk videos online now i believe, but it might be that = you need to pay for access... 

On 13 Sep 2014, at = 15:01, Stephen Mack <smack815@gmail.com> = wrote:

That is the video that captured my = attention and started my unikernal adventure.  But = thanks!

On = Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:

On 13 Sep 2014, at 14:13, Stephen Mack <smack815@gmail.com> wrote:

> On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> I'd suggest an even simpler mode -- just use the $50 Cubieboard2 = (or Cubietrick) directly as the development environment.
>
> I was going down the cubietrunk (cubieboard 3) road but after you = buy the board, monitor, keyboard, and mouse additions I ended up with = about the same price as the portable laptop style chromebook and you get = less hardware
>
> CubieTrunk --- Samsung Chromebook
> * Dual core 1GHz  --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz)
> * 2 GB memory  --- 4 GB
> * 8 GB storage --- 16 GB
>
> Ok so I know that someone has to invest their time and energy to = make it happen and to work out all the hardware issues and that is not = trivial. So, I assume that the chromebook development is all but = dead.  Such a same because that would have been a sweet compact = mobile system for Xen/Mirage.  It even has an HDMI out port that = could be used for presentations.
>
> P.S. Anil, are there any videos of your recent presentations at the = various conferences you have been attending?  You are a very gifted = orator.

Not quite a presentation but there's a good video interview = at http://twit.tv/show/floss-weekly/302

Amir


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


--
Cheers,
R.


= --Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16-- --Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUFGTVAAoJEOLF27JWwSg3C10P/3h++vstXFX/U5bGr2RSCPvB FyWGAtzhK/PSLInM34S+Z2Q2Td9tO1TbogNxYbKlF4+N9snYahfiPhnDsPUxb5Hm 2lWTLMR4cTpkob1iOwIGkZPcfcWA7D7uf0WEiJKW6vwlvez0qX4/eUUCCX0q6S0m 8oL2iMgDiwcgtWxIvd0cT1SeAFtFXfeu2CLpE4xu4awEGjtX3KwyJfP2PIDkmK1d SUUDWvuj4xmsCUcU4iIMnXehvwzjXE4wB/x+0KHWzBQcpGjBsVf+267/DJgQmmTO CDt6hfJ52Vcu6JbWNEbKYE5w0ngpbGiX0I6D/iXxA7y3OpLDZEwPJEy4OzQ5zQ8E pM6qsvOoHuCH1nPJgyOniuC7ftcKw/i6j9KH5r5qsTvlEG9PkpQyuiSQez4Q/IEh nBp/gliuu5aNa0WA+XEe998jfoCYT424ir/2m8RlihTm1K7+/rm06pS86YJ8BsKz iIKYNTgpcf5mRk4GUxMw2OnXkSXkUsjYwxRLRSD6BXvgGQ4tYVH1qhZlEK0jQgax nliEmcsb1HrGq8GvrUzLw34jAaDEFsLB9m0Sp8jSuAnxqzc5RpjI57Umvqy7I4fK 4C6+5nuVD2ZnMbCYQkc4PzAufXqJlySp39VCXOjOIAqJe4M8Qq3emu6cPh31QE6V Z4mOnJBGv+eFirfmJCHd =JgjE -----END PGP SIGNATURE----- --Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4-- --===============1260345107971259397== 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 --===============1260345107971259397==-- From mirageos-devel-bounces@lists.xenproject.org Sat Sep 13 15:38:53 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 13 Sep 2014 15:38: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 1XSpPU-0008KZ-Fw; Sat, 13 Sep 2014 15: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 1XSpPT-0008KU-8C for mirageos-devel@lists.xenproject.org; Sat, 13 Sep 2014 15:38:47 +0000 Received: from [193.109.254.147:17090] by server-9.bemta-14.messagelabs.com id 0B/B9-31535-60564145; Sat, 13 Sep 2014 15:38:46 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-27.messagelabs.com!1410622725!15337813!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 630 invoked from network); 13 Sep 2014 15:38:45 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-10.tower-27.messagelabs.com with SMTP; 13 Sep 2014 15:38:45 -0000 Received: (qmail 13479 invoked from network); 13 Sep 2014 15:38:44 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 13 Sep 2014 15:38:44 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 10336-07 for ; Sat, 13 Sep 2014 16:38:37 +0100 (BST) Received: (qmail 13383 invoked by uid 599); 13 Sep 2014 15:38:37 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Sat, 13 Sep 2014 16:38:37 +0100 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 1XSpPI-0001TG-PI; Sat, 13 Sep 2014 16:38:36 +0100 From: Richard Mortier To: Stephen Mack Date: Sat, 13 Sep 2014 16:37:57 +0100 Thread-Topic: [MirageOS-devel] Mirage budget development platform Thread-Index: Ac/PaMg7+Oud0Y14Rx2eRS/hwJL8Lw== Message-ID: <33F6C4E9-5A8A-4966-93C8-6FBAD39E8340@nottingham.ac.uk> References: <01FC073E-FC97-49B8-96BB-BA32E86ABADD@recoil.org> <16F45E39-7F7A-4659-8E02-6ED33A097745@cam.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Anil Madhavapeddy , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage budget development platform X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1260345107971259397==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1260345107971259397== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4 Content-Type: multipart/alternative; boundary="Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16" --Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii oscon have the oscon 14 talk videos online now i believe, but it might = be that you need to pay for access...=20 On 13 Sep 2014, at 15:01, Stephen Mack wrote: > That is the video that captured my attention and started my unikernal = adventure. But thanks! >=20 > On Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhry = wrote: >=20 > On 13 Sep 2014, at 14:13, Stephen Mack wrote: >=20 > > On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy = wrote: > > I'd suggest an even simpler mode -- just use the $50 Cubieboard2 (or = Cubietrick) directly as the development environment. > > > > I was going down the cubietrunk (cubieboard 3) road but after you = buy the board, monitor, keyboard, and mouse additions I ended up with = about the same price as the portable laptop style chromebook and you get = less hardware > > > > CubieTrunk --- Samsung Chromebook > > * Dual core 1GHz --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz) > > * 2 GB memory --- 4 GB > > * 8 GB storage --- 16 GB > > > > Ok so I know that someone has to invest their time and energy to = make it happen and to work out all the hardware issues and that is not = trivial. So, I assume that the chromebook development is all but dead. = Such a same because that would have been a sweet compact mobile system = for Xen/Mirage. It even has an HDMI out port that could be used for = presentations. > > > > P.S. Anil, are there any videos of your recent presentations at the = various conferences you have been attending? You are a very gifted = orator. >=20 > Not quite a presentation but there's a good video interview at = http://twit.tv/show/floss-weekly/302 >=20 > Amir >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --=20 Cheers, R. --Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii oscon = have the oscon 14 talk videos online now i believe, but it might be that = you need to pay for access... 

On 13 Sep 2014, at = 15:01, Stephen Mack <smack815@gmail.com> = wrote:

That is the video that captured my = attention and started my unikernal adventure.  But = thanks!

On = Sat, Sep 13, 2014 at 10:46 AM, Amir Chaudhry <amc79@cam.ac.uk> wrote:

On 13 Sep 2014, at 14:13, Stephen Mack <smack815@gmail.com> wrote:

> On Fri, Sep 12, 2014 at 11:13 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> I'd suggest an even simpler mode -- just use the $50 Cubieboard2 = (or Cubietrick) directly as the development environment.
>
> I was going down the cubietrunk (cubieboard 3) road but after you = buy the board, monitor, keyboard, and mouse additions I ended up with = about the same price as the portable laptop style chromebook and you get = less hardware
>
> CubieTrunk --- Samsung Chromebook
> * Dual core 1GHz  --- 8 core (4 x 1.9 GHz/4 x 1.3 GHz)
> * 2 GB memory  --- 4 GB
> * 8 GB storage --- 16 GB
>
> Ok so I know that someone has to invest their time and energy to = make it happen and to work out all the hardware issues and that is not = trivial. So, I assume that the chromebook development is all but = dead.  Such a same because that would have been a sweet compact = mobile system for Xen/Mirage.  It even has an HDMI out port that = could be used for presentations.
>
> P.S. Anil, are there any videos of your recent presentations at the = various conferences you have been attending?  You are a very gifted = orator.

Not quite a presentation but there's a good video interview = at http://twit.tv/show/floss-weekly/302

Amir


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


--
Cheers,
R.


= --Apple-Mail=_F45AD004-EC08-4FEF-A683-D7F4841EBC16-- --Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUFGTVAAoJEOLF27JWwSg3C10P/3h++vstXFX/U5bGr2RSCPvB FyWGAtzhK/PSLInM34S+Z2Q2Td9tO1TbogNxYbKlF4+N9snYahfiPhnDsPUxb5Hm 2lWTLMR4cTpkob1iOwIGkZPcfcWA7D7uf0WEiJKW6vwlvez0qX4/eUUCCX0q6S0m 8oL2iMgDiwcgtWxIvd0cT1SeAFtFXfeu2CLpE4xu4awEGjtX3KwyJfP2PIDkmK1d SUUDWvuj4xmsCUcU4iIMnXehvwzjXE4wB/x+0KHWzBQcpGjBsVf+267/DJgQmmTO CDt6hfJ52Vcu6JbWNEbKYE5w0ngpbGiX0I6D/iXxA7y3OpLDZEwPJEy4OzQ5zQ8E pM6qsvOoHuCH1nPJgyOniuC7ftcKw/i6j9KH5r5qsTvlEG9PkpQyuiSQez4Q/IEh nBp/gliuu5aNa0WA+XEe998jfoCYT424ir/2m8RlihTm1K7+/rm06pS86YJ8BsKz iIKYNTgpcf5mRk4GUxMw2OnXkSXkUsjYwxRLRSD6BXvgGQ4tYVH1qhZlEK0jQgax nliEmcsb1HrGq8GvrUzLw34jAaDEFsLB9m0Sp8jSuAnxqzc5RpjI57Umvqy7I4fK 4C6+5nuVD2ZnMbCYQkc4PzAufXqJlySp39VCXOjOIAqJe4M8Qq3emu6cPh31QE6V Z4mOnJBGv+eFirfmJCHd =JgjE -----END PGP SIGNATURE----- --Apple-Mail=_72AE19E9-CC0F-4CD3-9B5B-02F9E6454AF4-- --===============1260345107971259397== 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 --===============1260345107971259397==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:05:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:05: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 1XTWuE-0003dn-6E; Mon, 15 Sep 2014 14:05:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTWuB-0003cB-DB for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:05:23 +0000 Received: from [193.109.254.147:32778] by server-12.bemta-14.messagelabs.com id 4A/5D-01461-222F6145; Mon, 15 Sep 2014 14:05:22 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1410789920!15648957!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4053 invoked from network); 15 Sep 2014 14:05:21 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-13.tower-27.messagelabs.com with SMTP; 15 Sep 2014 14:05:21 -0000 Received: (qmail 11735 invoked from network); 15 Sep 2014 14:05:13 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 15 Sep 2014 14:05:13 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 09595-09 for ; Mon, 15 Sep 2014 15:05:09 +0100 (BST) Received: (qmail 11587 invoked by uid 599); 15 Sep 2014 14:05:09 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 15 Sep 2014 15:05:09 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp3.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XTWu3-0006jj-4l; Mon, 15 Sep 2014 15:05:15 +0100 Message-ID: <5416F21A.3010505@nottingham.ac.uk> Date: Mon, 15 Sep 2014 15:05:14 +0100 From: Masoud Koleini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Anil Madhavapeddy , Yaron Minsky References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> In-Reply-To: <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2428461774435934616==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============2428461774435934616== Content-Type: multipart/alternative; boundary="------------000208050003000908070505" This is a multi-part message in MIME format. --------------000208050003000908070505 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Anil, By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error: Error: No implementations provided for the following modules: Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) any suggestion? On 10/09/14 15:55, Anil Madhavapeddy wrote: > (Re-adding the devel list to CC) > > The s-expression library is actually independent of Unix, so that's > fine. It's easiest to fork Frenetic in the short term and shift it to > using Core_kernel instead of Core. There will be probably be an Async > scheduler, which is a lot more work to fix. This requires shifting > the Async portions to use Async_kernel instead, which Jane Street is > working on. > > CCing Yaron -- any sense of how far away Async_kernel is from a public > release? We can get started on an Async_xen port then as well. > > -anil > > On 10 Sep 2014, at 10:55, Masoud Koleini > > wrote: > >> Oh, we will have the same problem! >> >> Frenetic protocol library uses Core, mostly for s-expressions. So >> far, I was testing it with unix config to figure out build and >> controller communication problems. >> >> Any idea of how we can make it work for xen? I think we have to >> modify Frenetic library to compile on both unix and xen, but try to >> keep this modification as light as possible until we have Core ported >> to Mirage. >> >> >> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>> Hi Ania, >>> >>> Mort is correct -- we haven't completely finishing porting Core to >>> Mirage. This requires breaking it down into smaller Unix-free >>> chunks, which the upstream maintainers (Jane Street) have already >>> started doing. Core consists of several sub-libraries, of which the >>> Unix-free subset is Core_kernel. Core_kernel still requires a few >>> minor C stubs (around Bigarray handling) which should work with the >>> trunk build of Mirage (untested). >>> >>> Overall though, if you're interested in getting on with applications >>> in Mirage *right now*, you should avoid Core for now. Using >>> Core_kernel is pretty close though, so I'll take a look at that. >>> >>> -anil >>> >>> On 10 Sep 2014, at 10:05, Richard Mortier >>> >> > wrote: >>> >>>> unfortunately, aiui, core can't presently be used to build for xen >>>> -- as i said, i think moves are afoot to fix this but it's a >>>> non-trivial thing to do so i don't know what the timeline is (or >>>> even if that's explicitly on the timeline). i don't know core well, >>>> but i know at least one issue is that the threading library >>>> (Core.Async) is alike to but not completely compatible with Lwt. >>>> >>>> others on the list are better placed to comment on if/when Core >>>> code will be usable with Xen :) >>>> >>>> On 10 Sep 2014, at 09:43, Ania Skorupa >>> > wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> thanks for your reply :) I am trying to build a piece of ocaml >>>>> program in mirage, which doesn't have a very large codebase. >>>>> >>>>> from errors, it looks that core is one of the libraries that >>>>> results in this error. in the code, I found that Core.Std is >>>>> opened. Is that a library that can not be used for xen? skimming >>>>> through the code, I didn't find explicit unix dependencies. >>>>> >>>>> >>>>> >>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier >>>>> >>>> > wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> I'd guess so, yes. Anything that depends on the underlying >>>>> platform (Unix) needs to be abstracted to work with mirage. >>>>> >>>>> Specifically, all those modules in the error message have unix >>>>> dependencies that aren't being satisfied, though I believe work is >>>>> ongoing to split js core up to have a kernel part that will be >>>>> more compatible with he mirage approach. >>>>> >>>>> What are you trying to do? It might be that there are alternative >>>>> mirage compatible libraries already available (though that might >>>>> not help much if you're looking at porting a large codebase of >>>>> course :) >>>>> >>>>> -- >>>>> Cheers, >>>>> >>>>> R. >>>>> >>>>> >>>>> >>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" >>>> > wrote: >>>>> >>>>>> Hello guys, >>>>>> >>>>>> When I compile my mirage application for xen, the following error >>>>>> happens: >>>>>> >>>>>> File "_none_", line 1: >>>>>> Error: No implementations provided for the following modules: >>>>>> UnixLabels referenced from >>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>> Unix referenced from >>>>>> /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>> /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>> /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>> Command exited with code 2. >>>>>> >>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> MirageOS-devel mailing list >>>>>> MirageOS-devel@lists.xenproject.org >>>>>> >>>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>> >>>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> >>>> R. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >> >> >> 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. --------------000208050003000908070505 Content-Type: text/html; charset=utf-8 Content-Length: 34097 Content-Transfer-Encoding: quoted-printable Hi Anil,

By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

any suggestion=3F

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine. =C2=A0It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core. =C2=A0There will be probably be an Async scheduler, which is a lot more work to fix. =C2=A0This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release=3F =C2=A0We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen=3F I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage. =C2=A0This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing. =C2=A0Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel. =C2=A0Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now. =C2=A0Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase.=C2=A0

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen=3F skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes. =C2=A0Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do=3F It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

-- =C2=A0
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel=3F


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




--=C2=A0
Cheers,

R.




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



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.=C2=A0=C2=A0 Please do not use, copy or disclose the information contained in this message or in any attachment.=C2=A0 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.


--------------000208050003000908070505-- --===============2428461774435934616== 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 --===============2428461774435934616==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:05:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:05: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 1XTWuE-0003dn-6E; Mon, 15 Sep 2014 14:05:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTWuB-0003cB-DB for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:05:23 +0000 Received: from [193.109.254.147:32778] by server-12.bemta-14.messagelabs.com id 4A/5D-01461-222F6145; Mon, 15 Sep 2014 14:05:22 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1410789920!15648957!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4053 invoked from network); 15 Sep 2014 14:05:21 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-13.tower-27.messagelabs.com with SMTP; 15 Sep 2014 14:05:21 -0000 Received: (qmail 11735 invoked from network); 15 Sep 2014 14:05:13 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 15 Sep 2014 14:05:13 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 09595-09 for ; Mon, 15 Sep 2014 15:05:09 +0100 (BST) Received: (qmail 11587 invoked by uid 599); 15 Sep 2014 14:05:09 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 15 Sep 2014 15:05:09 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp3.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XTWu3-0006jj-4l; Mon, 15 Sep 2014 15:05:15 +0100 Message-ID: <5416F21A.3010505@nottingham.ac.uk> Date: Mon, 15 Sep 2014 15:05:14 +0100 From: Masoud Koleini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Anil Madhavapeddy , Yaron Minsky References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> In-Reply-To: <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2428461774435934616==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============2428461774435934616== Content-Type: multipart/alternative; boundary="------------000208050003000908070505" This is a multi-part message in MIME format. --------------000208050003000908070505 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi Anil, By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error: Error: No implementations provided for the following modules: Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) any suggestion? On 10/09/14 15:55, Anil Madhavapeddy wrote: > (Re-adding the devel list to CC) > > The s-expression library is actually independent of Unix, so that's > fine. It's easiest to fork Frenetic in the short term and shift it to > using Core_kernel instead of Core. There will be probably be an Async > scheduler, which is a lot more work to fix. This requires shifting > the Async portions to use Async_kernel instead, which Jane Street is > working on. > > CCing Yaron -- any sense of how far away Async_kernel is from a public > release? We can get started on an Async_xen port then as well. > > -anil > > On 10 Sep 2014, at 10:55, Masoud Koleini > > wrote: > >> Oh, we will have the same problem! >> >> Frenetic protocol library uses Core, mostly for s-expressions. So >> far, I was testing it with unix config to figure out build and >> controller communication problems. >> >> Any idea of how we can make it work for xen? I think we have to >> modify Frenetic library to compile on both unix and xen, but try to >> keep this modification as light as possible until we have Core ported >> to Mirage. >> >> >> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>> Hi Ania, >>> >>> Mort is correct -- we haven't completely finishing porting Core to >>> Mirage. This requires breaking it down into smaller Unix-free >>> chunks, which the upstream maintainers (Jane Street) have already >>> started doing. Core consists of several sub-libraries, of which the >>> Unix-free subset is Core_kernel. Core_kernel still requires a few >>> minor C stubs (around Bigarray handling) which should work with the >>> trunk build of Mirage (untested). >>> >>> Overall though, if you're interested in getting on with applications >>> in Mirage *right now*, you should avoid Core for now. Using >>> Core_kernel is pretty close though, so I'll take a look at that. >>> >>> -anil >>> >>> On 10 Sep 2014, at 10:05, Richard Mortier >>> >> > wrote: >>> >>>> unfortunately, aiui, core can't presently be used to build for xen >>>> -- as i said, i think moves are afoot to fix this but it's a >>>> non-trivial thing to do so i don't know what the timeline is (or >>>> even if that's explicitly on the timeline). i don't know core well, >>>> but i know at least one issue is that the threading library >>>> (Core.Async) is alike to but not completely compatible with Lwt. >>>> >>>> others on the list are better placed to comment on if/when Core >>>> code will be usable with Xen :) >>>> >>>> On 10 Sep 2014, at 09:43, Ania Skorupa >>> > wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> thanks for your reply :) I am trying to build a piece of ocaml >>>>> program in mirage, which doesn't have a very large codebase. >>>>> >>>>> from errors, it looks that core is one of the libraries that >>>>> results in this error. in the code, I found that Core.Std is >>>>> opened. Is that a library that can not be used for xen? skimming >>>>> through the code, I didn't find explicit unix dependencies. >>>>> >>>>> >>>>> >>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier >>>>> >>>> > wrote: >>>>> >>>>> >>>>> Hi, >>>>> >>>>> I'd guess so, yes. Anything that depends on the underlying >>>>> platform (Unix) needs to be abstracted to work with mirage. >>>>> >>>>> Specifically, all those modules in the error message have unix >>>>> dependencies that aren't being satisfied, though I believe work is >>>>> ongoing to split js core up to have a kernel part that will be >>>>> more compatible with he mirage approach. >>>>> >>>>> What are you trying to do? It might be that there are alternative >>>>> mirage compatible libraries already available (though that might >>>>> not help much if you're looking at porting a large codebase of >>>>> course :) >>>>> >>>>> -- >>>>> Cheers, >>>>> >>>>> R. >>>>> >>>>> >>>>> >>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" >>>> > wrote: >>>>> >>>>>> Hello guys, >>>>>> >>>>>> When I compile my mirage application for xen, the following error >>>>>> happens: >>>>>> >>>>>> File "_none_", line 1: >>>>>> Error: No implementations provided for the following modules: >>>>>> UnixLabels referenced from >>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>> Unix referenced from >>>>>> /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>> /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>> /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>> Command exited with code 2. >>>>>> >>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> MirageOS-devel mailing list >>>>>> MirageOS-devel@lists.xenproject.org >>>>>> >>>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>> >>>>> >>>> >>>> >>>> -- >>>> Cheers, >>>> >>>> R. >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> MirageOS-devel mailing list >>>> MirageOS-devel@lists.xenproject.org >>>> >>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>> >> >> >> 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. --------------000208050003000908070505 Content-Type: text/html; charset=utf-8 Content-Length: 34097 Content-Transfer-Encoding: quoted-printable Hi Anil,

By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

any suggestion=3F

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine. =C2=A0It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core. =C2=A0There will be probably be an Async scheduler, which is a lot more work to fix. =C2=A0This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release=3F =C2=A0We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen=3F I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage. =C2=A0This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing. =C2=A0Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel. =C2=A0Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now. =C2=A0Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase.=C2=A0

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen=3F skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes. =C2=A0Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do=3F It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

-- =C2=A0
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel=3F


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




--=C2=A0
Cheers,

R.




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



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.=C2=A0=C2=A0 Please do not use, copy or disclose the information contained in this message or in any attachment.=C2=A0 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.


--------------000208050003000908070505-- --===============2428461774435934616== 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 --===============2428461774435934616==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:17:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:17:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTX64-0004Ws-R6; Mon, 15 Sep 2014 14:17:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTX63-0004Wl-B8 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:17:39 +0000 Received: from [85.158.143.35:2668] by server-3.bemta-4.messagelabs.com id 07/70-06192-205F6145; Mon, 15 Sep 2014 14:17:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1410790656!13853361!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31755 invoked from network); 15 Sep 2014 14:17:37 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 14:17:37 -0000 Received: by mail-wi0-f181.google.com with SMTP id bs8so4281387wib.2 for ; Mon, 15 Sep 2014 07:17:36 -0700 (PDT) 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=G2OSaR4bUDLMTBifiOW+T1V/LttS/zQ93/V9L2VG+YI=; b=RgLOB95ScWZtvJj4aOpzhPiElUhrPRHFiIHA10CNUxkOf+43ltadyyLjp+0S2gfeZ2 abhSu/+IfAZdGbKNS/b3QN/Y/bXHbadaGSq8ZJlZZRMg6Sjtqiqsi74xigf9Kt3aZb0+ 6r4DMR3AywkoMfFxDbwMMBoet1PEP4MTtZz4/wP0cz8qGFcomgGK55ivNWsQnDjgrTAJ jrWds2JiJc2fsPGPIohFlwk1BCoicYQ/eZ1PZv0UF93dYkZBSLxxf+7IwLuhs/vQGbMK 8yYfDUZutB0Z/aG8TJzkN6UVGBOiSn4FmhF3SGlsqU/krg0UrwgS82lEicMaekvfSxOB QkXQ== X-Received: by 10.180.106.5 with SMTP id gq5mr7616572wib.28.1410790656745; Mon, 15 Sep 2014 07:17:36 -0700 (PDT) Received: from dhcp-172-17-168-65.eduroam.wireless.private.cam.ac.uk (global-1-27.nat.csx.cam.ac.uk. [131.111.184.27]) by mx.google.com with ESMTPSA id bj7sm14927453wjc.33.2014.09.15.07.17.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 07:17:35 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <5416F21A.3010505@nottingham.ac.uk> Date: Mon, 15 Sep 2014 15:17:28 +0100 Message-Id: <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5294315914238128109==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5294315914238128109== Content-Type: multipart/alternative; boundary="Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED" --Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic = library, and adding core_kernel to the config.ml, I receive error: >=20 > Error: No implementations provided for the following modules: > Unix referenced from = /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) I guess you need to change your build system to link with core_cornel = (and if it's _oasis, regenerate the build files by running `oasis setup` = at the root of your project). Thomas >=20 > any suggestion? >=20 > On 10/09/14 15:55, Anil Madhavapeddy wrote: >> (Re-adding the devel list to CC) >>=20 >> The s-expression library is actually independent of Unix, so that's = fine. It's easiest to fork Frenetic in the short term and shift it to = using Core_kernel instead of Core. There will be probably be an Async = scheduler, which is a lot more work to fix. This requires shifting the = Async portions to use Async_kernel instead, which Jane Street is working = on. >>=20 >> CCing Yaron -- any sense of how far away Async_kernel is from a = public release? We can get started on an Async_xen port then as well. >>=20 >> -anil >>=20 >> On 10 Sep 2014, at 10:55, Masoud Koleini = wrote: >>=20 >>> Oh, we will have the same problem! >>>=20 >>> Frenetic protocol library uses Core, mostly for s-expressions. So = far, I was testing it with unix config to figure out build and = controller communication problems. >>>=20 >>> Any idea of how we can make it work for xen? I think we have to = modify Frenetic library to compile on both unix and xen, but try to keep = this modification as light as possible until we have Core ported to = Mirage. >>>=20 >>>=20 >>> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>>> Hi Ania, >>>>=20 >>>> Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). >>>>=20 >>>> Overall though, if you're interested in getting on with = applications in Mirage *right now*, you should avoid Core for now. = Using Core_kernel is pretty close though, so I'll take a look at that. >>>>=20 >>>> -anil >>>>=20 >>>> On 10 Sep 2014, at 10:05, Richard Mortier = wrote: >>>>=20 >>>>> unfortunately, aiui, core can't presently be used to build for xen = -- as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >>>>>=20 >>>>> others on the list are better placed to comment on if/when Core = code will be usable with Xen :) >>>>>=20 >>>>> On 10 Sep 2014, at 09:43, Ania Skorupa = wrote: >>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>>>>>=20 >>>>>> from errors, it looks that core is one of the libraries that = results in this error. in the code, I found that Core.Std is opened. Is = that a library that can not be used for xen? skimming through the code, = I didn't find explicit unix dependencies. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> I'd guess so, yes. Anything that depends on the underlying = platform (Unix) needs to be abstracted to work with mirage. >>>>>>=20 >>>>>> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>>>>>=20 >>>>>> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>>>>>=20 >>>>>> -- =20 >>>>>> Cheers, >>>>>>=20 >>>>>> R. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>>>>>=20 >>>>>>> Hello guys, >>>>>>>=20 >>>>>>> When I compile my mirage application for xen, the following = error happens: >>>>>>>=20 >>>>>>> File "_none_", line 1: >>>>>>> Error: No implementations provided for the following modules: >>>>>>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Command exited with code 2. >>>>>>>=20 >>>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>>>=20 >>>>>>>=20 >>>>>>> _______________________________________________ >>>>>>> MirageOS-devel mailing list >>>>>>> MirageOS-devel@lists.xenproject.org >>>>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> Cheers, >>>>>=20 >>>>> R. >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@lists.xenproject.org >>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>=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 >=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 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii
By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
         Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

I guess you need to change your build system to link with core_cornel (and if it's _oasis, regenerate the build files by running `oasis setup` at the root of your project).

Thomas


any suggestion?

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine.  It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core.  There will be probably be an Async scheduler, which is a lot more work to fix.  This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release?  We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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




-- 
Cheers,

R.




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



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.


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

--Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED-- --===============5294315914238128109== 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 --===============5294315914238128109==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:17:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:17:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTX64-0004Ws-R6; Mon, 15 Sep 2014 14:17:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTX63-0004Wl-B8 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:17:39 +0000 Received: from [85.158.143.35:2668] by server-3.bemta-4.messagelabs.com id 07/70-06192-205F6145; Mon, 15 Sep 2014 14:17:38 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1410790656!13853361!1 X-Originating-IP: [209.85.212.181] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31755 invoked from network); 15 Sep 2014 14:17:37 -0000 Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com) (209.85.212.181) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 14:17:37 -0000 Received: by mail-wi0-f181.google.com with SMTP id bs8so4281387wib.2 for ; Mon, 15 Sep 2014 07:17:36 -0700 (PDT) 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=G2OSaR4bUDLMTBifiOW+T1V/LttS/zQ93/V9L2VG+YI=; b=RgLOB95ScWZtvJj4aOpzhPiElUhrPRHFiIHA10CNUxkOf+43ltadyyLjp+0S2gfeZ2 abhSu/+IfAZdGbKNS/b3QN/Y/bXHbadaGSq8ZJlZZRMg6Sjtqiqsi74xigf9Kt3aZb0+ 6r4DMR3AywkoMfFxDbwMMBoet1PEP4MTtZz4/wP0cz8qGFcomgGK55ivNWsQnDjgrTAJ jrWds2JiJc2fsPGPIohFlwk1BCoicYQ/eZ1PZv0UF93dYkZBSLxxf+7IwLuhs/vQGbMK 8yYfDUZutB0Z/aG8TJzkN6UVGBOiSn4FmhF3SGlsqU/krg0UrwgS82lEicMaekvfSxOB QkXQ== X-Received: by 10.180.106.5 with SMTP id gq5mr7616572wib.28.1410790656745; Mon, 15 Sep 2014 07:17:36 -0700 (PDT) Received: from dhcp-172-17-168-65.eduroam.wireless.private.cam.ac.uk (global-1-27.nat.csx.cam.ac.uk. [131.111.184.27]) by mx.google.com with ESMTPSA id bj7sm14927453wjc.33.2014.09.15.07.17.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Sep 2014 07:17:35 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <5416F21A.3010505@nottingham.ac.uk> Date: Mon, 15 Sep 2014 15:17:28 +0100 Message-Id: <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5294315914238128109==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5294315914238128109== Content-Type: multipart/alternative; boundary="Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED" --Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic = library, and adding core_kernel to the config.ml, I receive error: >=20 > Error: No implementations provided for the following modules: > Unix referenced from = /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) I guess you need to change your build system to link with core_cornel = (and if it's _oasis, regenerate the build files by running `oasis setup` = at the root of your project). Thomas >=20 > any suggestion? >=20 > On 10/09/14 15:55, Anil Madhavapeddy wrote: >> (Re-adding the devel list to CC) >>=20 >> The s-expression library is actually independent of Unix, so that's = fine. It's easiest to fork Frenetic in the short term and shift it to = using Core_kernel instead of Core. There will be probably be an Async = scheduler, which is a lot more work to fix. This requires shifting the = Async portions to use Async_kernel instead, which Jane Street is working = on. >>=20 >> CCing Yaron -- any sense of how far away Async_kernel is from a = public release? We can get started on an Async_xen port then as well. >>=20 >> -anil >>=20 >> On 10 Sep 2014, at 10:55, Masoud Koleini = wrote: >>=20 >>> Oh, we will have the same problem! >>>=20 >>> Frenetic protocol library uses Core, mostly for s-expressions. So = far, I was testing it with unix config to figure out build and = controller communication problems. >>>=20 >>> Any idea of how we can make it work for xen? I think we have to = modify Frenetic library to compile on both unix and xen, but try to keep = this modification as light as possible until we have Core ported to = Mirage. >>>=20 >>>=20 >>> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>>> Hi Ania, >>>>=20 >>>> Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). >>>>=20 >>>> Overall though, if you're interested in getting on with = applications in Mirage *right now*, you should avoid Core for now. = Using Core_kernel is pretty close though, so I'll take a look at that. >>>>=20 >>>> -anil >>>>=20 >>>> On 10 Sep 2014, at 10:05, Richard Mortier = wrote: >>>>=20 >>>>> unfortunately, aiui, core can't presently be used to build for xen = -- as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >>>>>=20 >>>>> others on the list are better placed to comment on if/when Core = code will be usable with Xen :) >>>>>=20 >>>>> On 10 Sep 2014, at 09:43, Ania Skorupa = wrote: >>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>>>>>=20 >>>>>> from errors, it looks that core is one of the libraries that = results in this error. in the code, I found that Core.Std is opened. Is = that a library that can not be used for xen? skimming through the code, = I didn't find explicit unix dependencies. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> I'd guess so, yes. Anything that depends on the underlying = platform (Unix) needs to be abstracted to work with mirage. >>>>>>=20 >>>>>> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>>>>>=20 >>>>>> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>>>>>=20 >>>>>> -- =20 >>>>>> Cheers, >>>>>>=20 >>>>>> R. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>>>>>=20 >>>>>>> Hello guys, >>>>>>>=20 >>>>>>> When I compile my mirage application for xen, the following = error happens: >>>>>>>=20 >>>>>>> File "_none_", line 1: >>>>>>> Error: No implementations provided for the following modules: >>>>>>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Command exited with code 2. >>>>>>>=20 >>>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>>>=20 >>>>>>>=20 >>>>>>> _______________________________________________ >>>>>>> MirageOS-devel mailing list >>>>>>> MirageOS-devel@lists.xenproject.org >>>>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> Cheers, >>>>>=20 >>>>> R. >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@lists.xenproject.org >>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>=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 >=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 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii
By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
         Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

I guess you need to change your build system to link with core_cornel (and if it's _oasis, regenerate the build files by running `oasis setup` at the root of your project).

Thomas


any suggestion?

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine.  It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core.  There will be probably be an Async scheduler, which is a lot more work to fix.  This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release?  We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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




-- 
Cheers,

R.




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



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.


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

--Apple-Mail=_A2B7273A-72C6-4FD0-A98A-4B0988E4A3ED-- --===============5294315914238128109== 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 --===============5294315914238128109==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:29:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:29: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 1XTXHw-0004qs-I4; Mon, 15 Sep 2014 14:29:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTXHu-0004qn-Q6 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:29:55 +0000 Received: from [85.158.143.35:36475] by server-2.bemta-4.messagelabs.com id 13/2A-04525-2E7F6145; Mon, 15 Sep 2014 14:29:54 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-8.tower-21.messagelabs.com!1410791389!13194157!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6919 invoked from network); 15 Sep 2014 14:29:49 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-8.tower-21.messagelabs.com with SMTP; 15 Sep 2014 14:29:49 -0000 Received: (qmail 31351 invoked from network); 15 Sep 2014 14:27:55 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 15 Sep 2014 14:27:55 -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 30111-03 for ; Mon, 15 Sep 2014 15:27:48 +0100 (BST) Received: (qmail 31071 invoked by uid 599); 15 Sep 2014 14:27:48 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 15 Sep 2014 15:27:48 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp3.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XTXFs-0007yi-6A; Mon, 15 Sep 2014 15:27:48 +0100 Message-ID: <5416F764.5090304@nottingham.ac.uk> Date: Mon, 15 Sep 2014 15:27:48 +0100 From: Masoud Koleini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Thomas Gazagnaire References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> In-Reply-To: <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3907025786484084022==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============3907025786484084022== Content-Type: multipart/alternative; boundary="------------040201060208060906030505" This is a multi-part message in MIME format. --------------040201060208060906030505 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I don't use _oasis. I have core_kernel added to the ocamlfind libraries in config.ml--and hence, it is added to the packages in Makefile. On 15/09/14 15:17, Thomas Gazagnaire wrote: >> By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic >> library, and adding core_kernel to the config.ml, I receive error: >> >> Error: No implementations provided for the following modules: >> Unix referenced from >> /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) > > I guess you need to change your build system to link with core_cornel > (and if it's _oasis, regenerate the build files by running `oasis > setup` at the root of your project). > > Thomas > >> >> any suggestion? >> >> On 10/09/14 15:55, Anil Madhavapeddy wrote: >>> (Re-adding the devel list to CC) >>> >>> The s-expression library is actually independent of Unix, so that's >>> fine. It's easiest to fork Frenetic in the short term and shift it >>> to using Core_kernel instead of Core. There will be probably be an >>> Async scheduler, which is a lot more work to fix. This requires >>> shifting the Async portions to use Async_kernel instead, which Jane >>> Street is working on. >>> >>> CCing Yaron -- any sense of how far away Async_kernel is from a >>> public release? We can get started on an Async_xen port then as well. >>> >>> -anil >>> >>> On 10 Sep 2014, at 10:55, Masoud Koleini >>> >> > wrote: >>> >>>> Oh, we will have the same problem! >>>> >>>> Frenetic protocol library uses Core, mostly for s-expressions. So >>>> far, I was testing it with unix config to figure out build and >>>> controller communication problems. >>>> >>>> Any idea of how we can make it work for xen? I think we have to >>>> modify Frenetic library to compile on both unix and xen, but try to >>>> keep this modification as light as possible until we have Core >>>> ported to Mirage. >>>> >>>> >>>> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>>>> Hi Ania, >>>>> >>>>> Mort is correct -- we haven't completely finishing porting Core to >>>>> Mirage. This requires breaking it down into smaller Unix-free >>>>> chunks, which the upstream maintainers (Jane Street) have already >>>>> started doing. Core consists of several sub-libraries, of which >>>>> the Unix-free subset is Core_kernel. Core_kernel still requires a >>>>> few minor C stubs (around Bigarray handling) which should work >>>>> with the trunk build of Mirage (untested). >>>>> >>>>> Overall though, if you're interested in getting on with >>>>> applications in Mirage *right now*, you should avoid Core for now. >>>>> Using Core_kernel is pretty close though, so I'll take a look at >>>>> that. >>>>> >>>>> -anil >>>>> >>>>> On 10 Sep 2014, at 10:05, Richard Mortier >>>>> >>>> > wrote: >>>>> >>>>>> unfortunately, aiui, core can't presently be used to build for >>>>>> xen -- as i said, i think moves are afoot to fix this but it's a >>>>>> non-trivial thing to do so i don't know what the timeline is (or >>>>>> even if that's explicitly on the timeline). i don't know core >>>>>> well, but i know at least one issue is that the threading library >>>>>> (Core.Async) is alike to but not completely compatible with Lwt. >>>>>> >>>>>> others on the list are better placed to comment on if/when Core >>>>>> code will be usable with Xen :) >>>>>> >>>>>> On 10 Sep 2014, at 09:43, Ania Skorupa >>>>> > wrote: >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> thanks for your reply :) I am trying to build a piece of ocaml >>>>>>> program in mirage, which doesn't have a very large codebase. >>>>>>> >>>>>>> from errors, it looks that core is one of the libraries that >>>>>>> results in this error. in the code, I found that Core.Std is >>>>>>> opened. Is that a library that can not be used for xen? skimming >>>>>>> through the code, I didn't find explicit unix dependencies. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier >>>>>>> >>>>>> > wrote: >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'd guess so, yes. Anything that depends on the underlying >>>>>>> platform (Unix) needs to be abstracted to work with mirage. >>>>>>> >>>>>>> Specifically, all those modules in the error message have unix >>>>>>> dependencies that aren't being satisfied, though I believe work >>>>>>> is ongoing to split js core up to have a kernel part that will >>>>>>> be more compatible with he mirage approach. >>>>>>> >>>>>>> What are you trying to do? It might be that there are >>>>>>> alternative mirage compatible libraries already available >>>>>>> (though that might not help much if you're looking at porting a >>>>>>> large codebase of course :) >>>>>>> >>>>>>> -- >>>>>>> Cheers, >>>>>>> >>>>>>> R. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" >>>>>> > wrote: >>>>>>> >>>>>>>> Hello guys, >>>>>>>> >>>>>>>> When I compile my mirage application for xen, the following >>>>>>>> error happens: >>>>>>>> >>>>>>>> File "_none_", line 1: >>>>>>>> Error: No implementations provided for the following modules: >>>>>>>> UnixLabels referenced from >>>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>>> Unix referenced from >>>>>>>> /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>>>> /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>>>> /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>>> Command exited with code 2. >>>>>>>> >>>>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> MirageOS-devel mailing list >>>>>>>> MirageOS-devel@lists.xenproject.org >>>>>>>> >>>>>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Cheers, >>>>>> >>>>>> R. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> MirageOS-devel mailing list >>>>>> MirageOS-devel@lists.xenproject.org >>>>>> >>>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>> >>>> >>>> >>>> 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. >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > 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. --------------040201060208060906030505 Content-Type: text/html; charset=windows-1252 Content-Length: 43388 Content-Transfer-Encoding: quoted-printable I don't use _oasis. I have core_kernel added to the ocamlfind libraries in config.ml--and hence, it is added to the packages in Makefile.

On 15/09/14 15:17, Thomas Gazagnaire wrote:
By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
=A0=A0=A0=A0=A0=A0=A0=A0 Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

I guess you need to change your build system to link with core_cornel (and if it's _oasis, regenerate the build files by running `oasis setup` at the root of your project).

Thomas


any suggestion=3F

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine. =A0It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core. =A0There will be probably be an Async scheduler, which is a lot more work to fix. =A0This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release=3F =A0We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen=3F I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage. =A0This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing. =A0Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel. =A0Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now. =A0Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase.=A0

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen=3F skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes. =A0Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do=3F It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

-- =A0
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
=A0=A0=A0=A0=A0=A0=A0=A0 UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
=A0=A0=A0=A0=A0=A0=A0=A0 Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel=3F


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




--=A0
Cheers,

R.




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



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.=A0=A0 Please do not use, copy or disclose the information contained in this message or in any attachment.=A0 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.=A0=A0 Please do not use, copy or disclose the information contained in this message or in any attachment.=A0 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



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.


--------------040201060208060906030505-- --===============3907025786484084022== 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 --===============3907025786484084022==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:29:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:29: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 1XTXHw-0004qs-I4; Mon, 15 Sep 2014 14:29:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTXHu-0004qn-Q6 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:29:55 +0000 Received: from [85.158.143.35:36475] by server-2.bemta-4.messagelabs.com id 13/2A-04525-2E7F6145; Mon, 15 Sep 2014 14:29:54 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-8.tower-21.messagelabs.com!1410791389!13194157!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6919 invoked from network); 15 Sep 2014 14:29:49 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-8.tower-21.messagelabs.com with SMTP; 15 Sep 2014 14:29:49 -0000 Received: (qmail 31351 invoked from network); 15 Sep 2014 14:27:55 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 15 Sep 2014 14:27:55 -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 30111-03 for ; Mon, 15 Sep 2014 15:27:48 +0100 (BST) Received: (qmail 31071 invoked by uid 599); 15 Sep 2014 14:27:48 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 15 Sep 2014 15:27:48 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp3.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XTXFs-0007yi-6A; Mon, 15 Sep 2014 15:27:48 +0100 Message-ID: <5416F764.5090304@nottingham.ac.uk> Date: Mon, 15 Sep 2014 15:27:48 +0100 From: Masoud Koleini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Thomas Gazagnaire References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> In-Reply-To: <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3907025786484084022==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============3907025786484084022== Content-Type: multipart/alternative; boundary="------------040201060208060906030505" This is a multi-part message in MIME format. --------------040201060208060906030505 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I don't use _oasis. I have core_kernel added to the ocamlfind libraries in config.ml--and hence, it is added to the packages in Makefile. On 15/09/14 15:17, Thomas Gazagnaire wrote: >> By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic >> library, and adding core_kernel to the config.ml, I receive error: >> >> Error: No implementations provided for the following modules: >> Unix referenced from >> /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) > > I guess you need to change your build system to link with core_cornel > (and if it's _oasis, regenerate the build files by running `oasis > setup` at the root of your project). > > Thomas > >> >> any suggestion? >> >> On 10/09/14 15:55, Anil Madhavapeddy wrote: >>> (Re-adding the devel list to CC) >>> >>> The s-expression library is actually independent of Unix, so that's >>> fine. It's easiest to fork Frenetic in the short term and shift it >>> to using Core_kernel instead of Core. There will be probably be an >>> Async scheduler, which is a lot more work to fix. This requires >>> shifting the Async portions to use Async_kernel instead, which Jane >>> Street is working on. >>> >>> CCing Yaron -- any sense of how far away Async_kernel is from a >>> public release? We can get started on an Async_xen port then as well. >>> >>> -anil >>> >>> On 10 Sep 2014, at 10:55, Masoud Koleini >>> >> > wrote: >>> >>>> Oh, we will have the same problem! >>>> >>>> Frenetic protocol library uses Core, mostly for s-expressions. So >>>> far, I was testing it with unix config to figure out build and >>>> controller communication problems. >>>> >>>> Any idea of how we can make it work for xen? I think we have to >>>> modify Frenetic library to compile on both unix and xen, but try to >>>> keep this modification as light as possible until we have Core >>>> ported to Mirage. >>>> >>>> >>>> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>>>> Hi Ania, >>>>> >>>>> Mort is correct -- we haven't completely finishing porting Core to >>>>> Mirage. This requires breaking it down into smaller Unix-free >>>>> chunks, which the upstream maintainers (Jane Street) have already >>>>> started doing. Core consists of several sub-libraries, of which >>>>> the Unix-free subset is Core_kernel. Core_kernel still requires a >>>>> few minor C stubs (around Bigarray handling) which should work >>>>> with the trunk build of Mirage (untested). >>>>> >>>>> Overall though, if you're interested in getting on with >>>>> applications in Mirage *right now*, you should avoid Core for now. >>>>> Using Core_kernel is pretty close though, so I'll take a look at >>>>> that. >>>>> >>>>> -anil >>>>> >>>>> On 10 Sep 2014, at 10:05, Richard Mortier >>>>> >>>> > wrote: >>>>> >>>>>> unfortunately, aiui, core can't presently be used to build for >>>>>> xen -- as i said, i think moves are afoot to fix this but it's a >>>>>> non-trivial thing to do so i don't know what the timeline is (or >>>>>> even if that's explicitly on the timeline). i don't know core >>>>>> well, but i know at least one issue is that the threading library >>>>>> (Core.Async) is alike to but not completely compatible with Lwt. >>>>>> >>>>>> others on the list are better placed to comment on if/when Core >>>>>> code will be usable with Xen :) >>>>>> >>>>>> On 10 Sep 2014, at 09:43, Ania Skorupa >>>>> > wrote: >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> thanks for your reply :) I am trying to build a piece of ocaml >>>>>>> program in mirage, which doesn't have a very large codebase. >>>>>>> >>>>>>> from errors, it looks that core is one of the libraries that >>>>>>> results in this error. in the code, I found that Core.Std is >>>>>>> opened. Is that a library that can not be used for xen? skimming >>>>>>> through the code, I didn't find explicit unix dependencies. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier >>>>>>> >>>>>> > wrote: >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I'd guess so, yes. Anything that depends on the underlying >>>>>>> platform (Unix) needs to be abstracted to work with mirage. >>>>>>> >>>>>>> Specifically, all those modules in the error message have unix >>>>>>> dependencies that aren't being satisfied, though I believe work >>>>>>> is ongoing to split js core up to have a kernel part that will >>>>>>> be more compatible with he mirage approach. >>>>>>> >>>>>>> What are you trying to do? It might be that there are >>>>>>> alternative mirage compatible libraries already available >>>>>>> (though that might not help much if you're looking at porting a >>>>>>> large codebase of course :) >>>>>>> >>>>>>> -- >>>>>>> Cheers, >>>>>>> >>>>>>> R. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" >>>>>> > wrote: >>>>>>> >>>>>>>> Hello guys, >>>>>>>> >>>>>>>> When I compile my mirage application for xen, the following >>>>>>>> error happens: >>>>>>>> >>>>>>>> File "_none_", line 1: >>>>>>>> Error: No implementations provided for the following modules: >>>>>>>> UnixLabels referenced from >>>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>>> Unix referenced from >>>>>>>> /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>>>> /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>>>> /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>>> Command exited with code 2. >>>>>>>> >>>>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> MirageOS-devel mailing list >>>>>>>> MirageOS-devel@lists.xenproject.org >>>>>>>> >>>>>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Cheers, >>>>>> >>>>>> R. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> MirageOS-devel mailing list >>>>>> MirageOS-devel@lists.xenproject.org >>>>>> >>>>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>> >>>> >>>> >>>> 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. >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > 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. --------------040201060208060906030505 Content-Type: text/html; charset=windows-1252 Content-Length: 43388 Content-Transfer-Encoding: quoted-printable I don't use _oasis. I have core_kernel added to the ocamlfind libraries in config.ml--and hence, it is added to the packages in Makefile.

On 15/09/14 15:17, Thomas Gazagnaire wrote:
By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
=A0=A0=A0=A0=A0=A0=A0=A0 Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

I guess you need to change your build system to link with core_cornel (and if it's _oasis, regenerate the build files by running `oasis setup` at the root of your project).

Thomas


any suggestion=3F

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine. =A0It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core. =A0There will be probably be an Async scheduler, which is a lot more work to fix. =A0This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release=3F =A0We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen=3F I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage. =A0This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing. =A0Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel. =A0Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now. =A0Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase.=A0

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen=3F skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes. =A0Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do=3F It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

-- =A0
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
=A0=A0=A0=A0=A0=A0=A0=A0 UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
=A0=A0=A0=A0=A0=A0=A0=A0 Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel=3F


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




--=A0
Cheers,

R.




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



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.=A0=A0 Please do not use, copy or disclose the information contained in this message or in any attachment.=A0 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.=A0=A0 Please do not use, copy or disclose the information contained in this message or in any attachment.=A0 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



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.


--------------040201060208060906030505-- --===============3907025786484084022== 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 --===============3907025786484084022==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:52:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:52:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTXe5-0006Sv-0x; Mon, 15 Sep 2014 14:52:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTXe3-0006Sg-Fm for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:52:47 +0000 Received: from [85.158.139.211:59533] by server-14.bemta-5.messagelabs.com id 5E/DF-12422-E3DF6145; Mon, 15 Sep 2014 14:52:46 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1410792763!11192317!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14816 invoked from network); 15 Sep 2014 14:52:44 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 14:52:44 -0000 Received: by mail-qc0-f170.google.com with SMTP id l6so4236100qcy.1 for ; Mon, 15 Sep 2014 07:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fVZdGztHFiE/AeVADaylPu3IW0VrdixDDKKfpPPsILE=; b=MAlUDSIapjQy2cwMkWFwucV0dmyb4VDMobT+1vL56XSi27siTfryOppqruVWmpGN2T Wyr7PyHTeBhSDTl90FmIOeWaBsxAzWc7U/xAJGcV1sKN+mAQa6NiFR4E0ZN1c/GOrbJn C7GDOaXRAZJjXt6V19WIHLrB9YZKtCaMIClIN5KOYr7wnta4u9ooNugataVwpxgOjhCF n6gNvIRoapLGTVfbAzv3Ctduzr6tAabya7nSZ4TBGJeEZ+bpeG0zOkwmox999F1Ke8b9 SMvgFuMG3X9MpzdHNzB0QarYo+8EArAHu2YX0ZllLHNsn3x+SKC977/vaCOnblhH5XaI LPdA== MIME-Version: 1.0 X-Received: by 10.224.3.5 with SMTP id 5mr38038812qal.1.1410792760921; Mon, 15 Sep 2014 07:52:40 -0700 (PDT) Received: by 10.140.101.20 with HTTP; Mon, 15 Sep 2014 07:52:40 -0700 (PDT) In-Reply-To: References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> Date: Mon, 15 Sep 2014 15:52:40 +0100 X-Google-Sender-Auth: FmtszhCN0vVmNL6Vus6hcyp4gko Message-ID: From: Jon Crowcroft To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7531196352678536942==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7531196352678536942== Content-Type: multipart/alternative; boundary=001a11c3cfda5dd3f505031bc94c --001a11c3cfda5dd3f505031bc94c Content-Type: text/plain; charset=UTF-8 esp. use of (sparse, very big) merkle trees, gossip for consistency, etc reminded me should also re-view work from MPI on dealing with adversaries (e.g. peer review etc http://www.mpi-sws.org/~druschel/publications/peerreview-sosp07.pdf On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft wrote: > v cool > > here's a (another) possible use case for irmin: > http://queue.acm.org/detail.cfm?id=2668154 > > In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas > Gazagn > aire typed: > > >>Hi all, > >> > >>Lots of people starting asked me about the status of Irmin. As you > might have notice, I'vent had much time to spend on Irmin last month, but I > plan to fix that. My current priorities are: > >> > >>1/ make Irmin compiles on the Xen backend of Mirage. > https://github.com/mirage/irmin/issues/81 > >>This means dropping the dependency to core_kernel (for now on). The > external API will not change. > >> > >>2/ improve the high-level JSON API. This is related to > https://github.com/mirage/irmin/issues/80 > >>Currently, we only have a JSON API for the low-level stores, and the > very partial implementation of the higher-level calls. Needs to complete > and document that. > >> > >>3/ implement a pure-ocaml Git server to be able to at least `git pull` > from it. https://github.com/mirage/ocaml-git/issues/15 > >>Together with 1/ this will make possible to query the state of a > running Mirage unikernel with a simple `git pull ` > >> > >>4/ implement a simple distributed log server . > https://github.com/mirage/irmin/issues/82 > >>Could use Benjamin's rope implementation, that I first need to release > properly. > >> > >>5/ try to come up with a solution to the "unlimited" memory/storage > usage issues https://github.com/mirage/irmin/issues/83 > >>This is the most uncertain part of the short-term roadmap. I'll need to > check again what are the limitation of Git shallow copies and see how we > can use them to limit the history size to remember. > >> > >>There are also few open embarrassing bugs that I want to fix as well > (regarding fd leaks ...). > >> > >>If anyone is interested to help me on any of these topics, please feel > free to comment on the related issues on Github -- I'll gladly share the > workload. Also, feel free to reply to that email if you think there is any > important Imrin features that you think are missing now. > >> > >>Best, > >>Thomas > >>_______________________________________________ > >>MirageOS-devel mailing list > >>MirageOS-devel@lists.xenproject.org > >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > cheers > > jon > > --001a11c3cfda5dd3f505031bc94c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
esp. use of (sparse, very big) merkle trees, gossip for co= nsistency, etc

reminded me should also re-view work from= MPI on dealing with adversaries (e.g. peer review etc

On Sat, Se= p 13, 2014 at 1:08 PM, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk<= /a>> wrote:
v cool

here's a (another) possible use case for irmin:
= http://queue.acm.org/detail.cfm?id=3D2668154

In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Tho= mas Gazagn
aire typed:

=C2=A0>>Hi all,
=C2=A0>>
=C2=A0>>Lots of people starting asked me about the status of Irmin. A= s you might have notice, I'vent had much time to spend on Irmin last mo= nth, but I plan to fix that. My current priorities are:
=C2=A0>>
=C2=A0>>1/ make Irmin compiles on the Xen backend of Mirage.=C2=A0 https= ://github.com/mirage/irmin/issues/81
=C2=A0>>This means dropping the dependency to core_kernel (for now on= ). The external API will not change.
=C2=A0>>
=C2=A0>>2/ improve the high-level JSON API. This is related to https://g= ithub.com/mirage/irmin/issues/80
=C2=A0>>Currently, we only have a JSON API for the low-level stores, = and the very partial implementation of the higher-level calls. Needs to com= plete and document that.
=C2=A0>>
=C2=A0>>3/ implement a pure-ocaml Git server to be able to at least `= git pull` from it. https://github.com/mirage/ocaml-git/issues/15
=C2=A0>>Together with 1/ this will make possible to query the state o= f a running Mirage unikernel with a simple `git pull <vm-address>` =C2=A0>>
=C2=A0>>4/ implement a simple distributed log server .https://github.com= /mirage/irmin/issues/82
=C2=A0>>Could use Benjamin's rope implementation, that I first ne= ed to release properly.
=C2=A0>>
=C2=A0>>5/ try to come up with a solution to the "unlimited"= ; memory/storage usage issues https://github.com/mirage/irmin/issues/83 =C2=A0>>This is the most uncertain part of the short-term roadmap. I&= #39;ll need to check again what are the limitation of Git shallow copies an= d see how we can use them to limit the history size to remember.
=C2=A0>>
=C2=A0>>There are also few open embarrassing bugs that I want to fix = as well (regarding fd leaks ...).
=C2=A0>>
=C2=A0>>If anyone is interested to help me on any of these topics, pl= ease feel free to comment on the related issues on Github -- I'll gladl= y share the workload. Also, feel free to reply to that email if you think t= here is any important Imrin features that you think are missing now.
=C2=A0>>
=C2=A0>>Best,
=C2=A0>>Thomas
=C2=A0>>_______________________________________________
=C2=A0>>MirageOS-devel mailing list
=C2=A0>>Mirage= OS-devel@lists.xenproject.org
=C2=A0>>http://lists.xenproject.org/cgi-bin/ma= ilman/listinfo/mirageos-devel

=C2=A0cheers

=C2=A0 =C2=A0jon


--001a11c3cfda5dd3f505031bc94c-- --===============7531196352678536942== 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 --===============7531196352678536942==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 14:52:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 14:52:50 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTXe5-0006Sv-0x; Mon, 15 Sep 2014 14:52:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTXe3-0006Sg-Fm for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 14:52:47 +0000 Received: from [85.158.139.211:59533] by server-14.bemta-5.messagelabs.com id 5E/DF-12422-E3DF6145; Mon, 15 Sep 2014 14:52:46 +0000 X-Env-Sender: crowcroft@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1410792763!11192317!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14816 invoked from network); 15 Sep 2014 14:52:44 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 14:52:44 -0000 Received: by mail-qc0-f170.google.com with SMTP id l6so4236100qcy.1 for ; Mon, 15 Sep 2014 07:52:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=fVZdGztHFiE/AeVADaylPu3IW0VrdixDDKKfpPPsILE=; b=MAlUDSIapjQy2cwMkWFwucV0dmyb4VDMobT+1vL56XSi27siTfryOppqruVWmpGN2T Wyr7PyHTeBhSDTl90FmIOeWaBsxAzWc7U/xAJGcV1sKN+mAQa6NiFR4E0ZN1c/GOrbJn C7GDOaXRAZJjXt6V19WIHLrB9YZKtCaMIClIN5KOYr7wnta4u9ooNugataVwpxgOjhCF n6gNvIRoapLGTVfbAzv3Ctduzr6tAabya7nSZ4TBGJeEZ+bpeG0zOkwmox999F1Ke8b9 SMvgFuMG3X9MpzdHNzB0QarYo+8EArAHu2YX0ZllLHNsn3x+SKC977/vaCOnblhH5XaI LPdA== MIME-Version: 1.0 X-Received: by 10.224.3.5 with SMTP id 5mr38038812qal.1.1410792760921; Mon, 15 Sep 2014 07:52:40 -0700 (PDT) Received: by 10.140.101.20 with HTTP; Mon, 15 Sep 2014 07:52:40 -0700 (PDT) In-Reply-To: References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> Date: Mon, 15 Sep 2014 15:52:40 +0100 X-Google-Sender-Auth: FmtszhCN0vVmNL6Vus6hcyp4gko Message-ID: From: Jon Crowcroft To: Thomas Gazagnaire Cc: mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7531196352678536942==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7531196352678536942== Content-Type: multipart/alternative; boundary=001a11c3cfda5dd3f505031bc94c --001a11c3cfda5dd3f505031bc94c Content-Type: text/plain; charset=UTF-8 esp. use of (sparse, very big) merkle trees, gossip for consistency, etc reminded me should also re-view work from MPI on dealing with adversaries (e.g. peer review etc http://www.mpi-sws.org/~druschel/publications/peerreview-sosp07.pdf On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft wrote: > v cool > > here's a (another) possible use case for irmin: > http://queue.acm.org/detail.cfm?id=2668154 > > In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas > Gazagn > aire typed: > > >>Hi all, > >> > >>Lots of people starting asked me about the status of Irmin. As you > might have notice, I'vent had much time to spend on Irmin last month, but I > plan to fix that. My current priorities are: > >> > >>1/ make Irmin compiles on the Xen backend of Mirage. > https://github.com/mirage/irmin/issues/81 > >>This means dropping the dependency to core_kernel (for now on). The > external API will not change. > >> > >>2/ improve the high-level JSON API. This is related to > https://github.com/mirage/irmin/issues/80 > >>Currently, we only have a JSON API for the low-level stores, and the > very partial implementation of the higher-level calls. Needs to complete > and document that. > >> > >>3/ implement a pure-ocaml Git server to be able to at least `git pull` > from it. https://github.com/mirage/ocaml-git/issues/15 > >>Together with 1/ this will make possible to query the state of a > running Mirage unikernel with a simple `git pull ` > >> > >>4/ implement a simple distributed log server . > https://github.com/mirage/irmin/issues/82 > >>Could use Benjamin's rope implementation, that I first need to release > properly. > >> > >>5/ try to come up with a solution to the "unlimited" memory/storage > usage issues https://github.com/mirage/irmin/issues/83 > >>This is the most uncertain part of the short-term roadmap. I'll need to > check again what are the limitation of Git shallow copies and see how we > can use them to limit the history size to remember. > >> > >>There are also few open embarrassing bugs that I want to fix as well > (regarding fd leaks ...). > >> > >>If anyone is interested to help me on any of these topics, please feel > free to comment on the related issues on Github -- I'll gladly share the > workload. Also, feel free to reply to that email if you think there is any > important Imrin features that you think are missing now. > >> > >>Best, > >>Thomas > >>_______________________________________________ > >>MirageOS-devel mailing list > >>MirageOS-devel@lists.xenproject.org > >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > cheers > > jon > > --001a11c3cfda5dd3f505031bc94c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
esp. use of (sparse, very big) merkle trees, gossip for co= nsistency, etc

reminded me should also re-view work from= MPI on dealing with adversaries (e.g. peer review etc

On Sat, Se= p 13, 2014 at 1:08 PM, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk<= /a>> wrote:
v cool

here's a (another) possible use case for irmin:
= http://queue.acm.org/detail.cfm?id=3D2668154

In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Tho= mas Gazagn
aire typed:

=C2=A0>>Hi all,
=C2=A0>>
=C2=A0>>Lots of people starting asked me about the status of Irmin. A= s you might have notice, I'vent had much time to spend on Irmin last mo= nth, but I plan to fix that. My current priorities are:
=C2=A0>>
=C2=A0>>1/ make Irmin compiles on the Xen backend of Mirage.=C2=A0 https= ://github.com/mirage/irmin/issues/81
=C2=A0>>This means dropping the dependency to core_kernel (for now on= ). The external API will not change.
=C2=A0>>
=C2=A0>>2/ improve the high-level JSON API. This is related to https://g= ithub.com/mirage/irmin/issues/80
=C2=A0>>Currently, we only have a JSON API for the low-level stores, = and the very partial implementation of the higher-level calls. Needs to com= plete and document that.
=C2=A0>>
=C2=A0>>3/ implement a pure-ocaml Git server to be able to at least `= git pull` from it. https://github.com/mirage/ocaml-git/issues/15
=C2=A0>>Together with 1/ this will make possible to query the state o= f a running Mirage unikernel with a simple `git pull <vm-address>` =C2=A0>>
=C2=A0>>4/ implement a simple distributed log server .https://github.com= /mirage/irmin/issues/82
=C2=A0>>Could use Benjamin's rope implementation, that I first ne= ed to release properly.
=C2=A0>>
=C2=A0>>5/ try to come up with a solution to the "unlimited"= ; memory/storage usage issues https://github.com/mirage/irmin/issues/83 =C2=A0>>This is the most uncertain part of the short-term roadmap. I&= #39;ll need to check again what are the limitation of Git shallow copies an= d see how we can use them to limit the history size to remember.
=C2=A0>>
=C2=A0>>There are also few open embarrassing bugs that I want to fix = as well (regarding fd leaks ...).
=C2=A0>>
=C2=A0>>If anyone is interested to help me on any of these topics, pl= ease feel free to comment on the related issues on Github -- I'll gladl= y share the workload. Also, feel free to reply to that email if you think t= here is any important Imrin features that you think are missing now.
=C2=A0>>
=C2=A0>>Best,
=C2=A0>>Thomas
=C2=A0>>_______________________________________________
=C2=A0>>MirageOS-devel mailing list
=C2=A0>>Mirage= OS-devel@lists.xenproject.org
=C2=A0>>http://lists.xenproject.org/cgi-bin/ma= ilman/listinfo/mirageos-devel

=C2=A0cheers

=C2=A0 =C2=A0jon


--001a11c3cfda5dd3f505031bc94c-- --===============7531196352678536942== 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 --===============7531196352678536942==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 15:31:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 15:31: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 1XTYFj-0007om-84; Mon, 15 Sep 2014 15:31:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTYFi-0007oS-26 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 15:31:42 +0000 Received: from [85.158.139.211:20444] by server-3.bemta-5.messagelabs.com id DA/1E-13873-D5607145; Mon, 15 Sep 2014 15:31:41 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1410795093!11202355!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12250 invoked from network); 15 Sep 2014 15:31:34 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-15.tower-206.messagelabs.com with SMTP; 15 Sep 2014 15:31:34 -0000 Received: (qmail 20235 invoked from network); 15 Sep 2014 15:31:33 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 15 Sep 2014 15:31:33 -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 19564-02 for ; Mon, 15 Sep 2014 16:31:24 +0100 (BST) Received: (qmail 19903 invoked by uid 599); 15 Sep 2014 15:31:24 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 15 Sep 2014 16:31:24 +0100 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 1XTYFN-0003Ma-Mu; Mon, 15 Sep 2014 16:31:21 +0100 From: Richard Mortier To: Masoud Koleini Date: Mon, 15 Sep 2014 16:31:13 +0100 Thread-Topic: [MirageOS-devel] Compile mirage application for xen Thread-Index: Ac/Q+hl0XGRMRLeQSQKGScA/wjE1Iw== Message-ID: <3D20168F-ED6B-4FDA-B755-B0F7D9A03245@nottingham.ac.uk> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> <5416F764.5090304@nottingham.ac.uk> In-Reply-To: <5416F764.5090304@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: Yaron Minsky , Spiros Eliopoulos , Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1549912867169668106==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1549912867169668106== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_" --_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On 15 Sep 2014, at 15:27, Masoud Koleini > wrote: I don't use _oasis. I have core_kernel added to the ocamlfind libraries in = config.ml--and hence, it is added to the packages in Makefile. (may be worth posting a pointer to the code in github...?) On 15/09/14 15:17, Thomas Gazagnaire wrote: By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, = and adding core_kernel to the config.ml, I receive error: Error: No implementations provided for the following modules: Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_k= ernel.cmxa(Core_kernel) I guess you need to change your build system to link with core_cornel (and = if it's _oasis, regenerate the build files by running `oasis setup` at the = root of your project). Thomas any suggestion? On 10/09/14 15:55, Anil Madhavapeddy wrote: (Re-adding the devel list to CC) The s-expression library is actually independent of Unix, so that's fine. = It's easiest to fork Frenetic in the short term and shift it to using Core_= kernel instead of Core. There will be probably be an Async scheduler, whic= h is a lot more work to fix. This requires shifting the Async portions to = use Async_kernel instead, which Jane Street is working on. CCing Yaron -- any sense of how far away Async_kernel is from a public rele= ase? We can get started on an Async_xen port then as well. -anil On 10 Sep 2014, at 10:55, Masoud Koleini > wrote: Oh, we will have the same problem! Frenetic protocol library uses Core, mostly for s-expressions. So far, I wa= s testing it with unix config to figure out build and controller communicat= ion problems. Any idea of how we can make it work for xen? I think we have to modify Fren= etic library to compile on both unix and xen, but try to keep this modifica= tion as light as possible until we have Core ported to Mirage. On 10/09/14 10:33, Anil Madhavapeddy wrote: Hi Ania, Mort is correct -- we haven't completely finishing porting Core to Mirage. = This requires breaking it down into smaller Unix-free chunks, which the up= stream maintainers (Jane Street) have already started doing. Core consists= of several sub-libraries, of which the Unix-free subset is Core_kernel. C= ore_kernel still requires a few minor C stubs (around Bigarray handling) wh= ich should work with the trunk build of Mirage (untested). Overall though, if you're interested in getting on with applications in Mir= age *right now*, you should avoid Core for now. Using Core_kernel is prett= y close though, so I'll take a look at that. -anil On 10 Sep 2014, at 10:05, Richard Mortier > wrote: unfortunately, aiui, core can't presently be used to build for xen -- as i = said, i think moves are afoot to fix this but it's a non-trivial thing to d= o so i don't know what the timeline is (or even if that's explicitly on the= timeline). i don't know core well, but i know at least one issue is that t= he threading library (Core.Async) is alike to but not completely compatible= with Lwt. others on the list are better placed to comment on if/when Core code will b= e usable with Xen :) On 10 Sep 2014, at 09:43, Ania Skorupa > wrote: Hi, thanks for your reply :) I am trying to build a piece of ocaml program in m= irage, which doesn't have a very large codebase. from errors, it looks that core is one of the libraries that results in thi= s error. in the code, I found that Core.Std is opened. Is that a library th= at can not be used for xen? skimming through the code, I didn't find explic= it unix dependencies. On Tuesday, September 9, 2014 6:32 PM, Richard Mortier > wrote: Hi, I'd guess so, yes. Anything that depends on the underlying platform (Unix)= needs to be abstracted to work with mirage. Specifically, all those modules in the error message have unix dependencies= that aren't being satisfied, though I believe work is ongoing to split js = core up to have a kernel part that will be more compatible with he mirage a= pproach. What are you trying to do? It might be that there are alternative mirage co= mpatible libraries already available (though that might not help much if yo= u're looking at porting a large codebase of course :) -- Cheers, R. On 9 Sep 2014, at 19:13, "Ania Skorupa" > wrote: Hello guys, When I compile my mirage application for xen, the following error happens: File "_none_", line 1: Error: No implementations provided for the following modules: UnixLabels referenced from /home/user/.opam/system/lib/core/core.c= mxa(Core) Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_ke= rnel), /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexpl= ib_unix), /home/user/.opam/system/lib/core/core.cmxa(Core) Command exited with code 2. Am I using libraries that can not be used to for xen unikernel? _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel -- Cheers, R. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel 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. 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 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 -- 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 er= ror, please send it back to me, and immediately delete it. Please do not u= se, copy or disclose the information contained in this message or in any att= achment. Any views or opinions expressed by the author of this email do not= necessarily reflect the views of the University of Nottingham.=0D=0A =0D=0A This message has been checked for viruses but the contents of an attachment= =0D=0A may still contain software viruses which could damage your computer system,= you are advised to perform your own checks. Email communications with the U= niversity of Nottingham may be monitored as permitted by UK legislation.=0D=0A =0D=0A =0D=0A =0D=0A =0D=0A --_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
On 15 Sep 20= 14, at 15:27, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

=20 =20
I don't use _oasis. I have core_kernel added to the ocamlfind libraries in config.ml--and hence, it is added to the packages in Makefile.

(may be worth posting a= pointer to the code in github...?)


On 15/09/14 15:17, Thomas Gazagnaire wrote:
By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
         Unix reference= d from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_ke= rnel)

I guess you need to change your build system to link with core_cornel (and if it's _oasis, regenerate the build files by running `oasis setup` at the root of your project).

Thomas


any suggestion?

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine.  It's easiest to fork Frenetic i= n the short term and shift it to using Core_kernel instead of Core.  There will be probably be an Async scheduler= , which is a lot more work to fix.  This requires shifti= ng the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release?  We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud= .koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires = a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.= uk> wrote:

unf= ortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com= > wrote:


= Hi,

thank= s for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <R= ichard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Speci= fically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Che= ers,
R.<= /div>
On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

H= ello guys,

When I compile my mirage application for xen, the following error happens:
File "_none_", line 1:
Error: No implementations provided for the following modules:
   = ;      UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
   = ;      Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
   = ;        /home/user/.opam/= system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
   = ;        /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),    = ;        /home/user/.opam/= system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?
<= br class=3D"" clear=3D"none">

_______________________________________________
= MirageOS-devel mailing list
= MirageOS-devel@lists.xenpro= ject.org
= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirage= os-devel




-- 
Cheers,<= span class=3D"Apple-style-span" style=3D"font-family: monospace;">

R.




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



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 d= o not use, copy or disclose the information contained in this message or in any attachment.  Any vie= ws or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message ha= s 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.


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


=20

This message and any attachment are intended solely for the addresse= e and may contain confidential information. If you have received this messa= ge in error, please send it back to me, and immediately delete it. &nb= sp; Please do not use, copy or disclose the information contained in this m= essage or in any attachment.  Any views or opinions expressed by the a= uthor of this email do not necessarily reflect the views of the University = of Nottingham.

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


_______________________________________________
MirageOS-devel mailing l= ist
MirageOS-deve= l@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/l= istinfo/mirageos-devel


-- 
Cheers,

R.





=

This message and any attachment are intended solely for the addressee an= d may contain confidential information. If you have received this message in= error, please send it back to me, and immediately delete it.   Pl= ease 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 Nottin= gham.

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


= = --_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_-- --===============1549912867169668106== 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 --===============1549912867169668106==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 15:31:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 15:31: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 1XTYFj-0007om-84; Mon, 15 Sep 2014 15:31:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTYFi-0007oS-26 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 15:31:42 +0000 Received: from [85.158.139.211:20444] by server-3.bemta-5.messagelabs.com id DA/1E-13873-D5607145; Mon, 15 Sep 2014 15:31:41 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1410795093!11202355!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12250 invoked from network); 15 Sep 2014 15:31:34 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-15.tower-206.messagelabs.com with SMTP; 15 Sep 2014 15:31:34 -0000 Received: (qmail 20235 invoked from network); 15 Sep 2014 15:31:33 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 15 Sep 2014 15:31:33 -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 19564-02 for ; Mon, 15 Sep 2014 16:31:24 +0100 (BST) Received: (qmail 19903 invoked by uid 599); 15 Sep 2014 15:31:24 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 15 Sep 2014 16:31:24 +0100 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 1XTYFN-0003Ma-Mu; Mon, 15 Sep 2014 16:31:21 +0100 From: Richard Mortier To: Masoud Koleini Date: Mon, 15 Sep 2014 16:31:13 +0100 Thread-Topic: [MirageOS-devel] Compile mirage application for xen Thread-Index: Ac/Q+hl0XGRMRLeQSQKGScA/wjE1Iw== Message-ID: <3D20168F-ED6B-4FDA-B755-B0F7D9A03245@nottingham.ac.uk> References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> <11119993-1D09-4FC3-98C6-A27BE428F6EC@gazagnaire.org> <5416F764.5090304@nottingham.ac.uk> In-Reply-To: <5416F764.5090304@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: Yaron Minsky , Spiros Eliopoulos , Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1549912867169668106==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1549912867169668106== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_" --_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On 15 Sep 2014, at 15:27, Masoud Koleini > wrote: I don't use _oasis. I have core_kernel added to the ocamlfind libraries in = config.ml--and hence, it is added to the packages in Makefile. (may be worth posting a pointer to the code in github...?) On 15/09/14 15:17, Thomas Gazagnaire wrote: By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, = and adding core_kernel to the config.ml, I receive error: Error: No implementations provided for the following modules: Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_k= ernel.cmxa(Core_kernel) I guess you need to change your build system to link with core_cornel (and = if it's _oasis, regenerate the build files by running `oasis setup` at the = root of your project). Thomas any suggestion? On 10/09/14 15:55, Anil Madhavapeddy wrote: (Re-adding the devel list to CC) The s-expression library is actually independent of Unix, so that's fine. = It's easiest to fork Frenetic in the short term and shift it to using Core_= kernel instead of Core. There will be probably be an Async scheduler, whic= h is a lot more work to fix. This requires shifting the Async portions to = use Async_kernel instead, which Jane Street is working on. CCing Yaron -- any sense of how far away Async_kernel is from a public rele= ase? We can get started on an Async_xen port then as well. -anil On 10 Sep 2014, at 10:55, Masoud Koleini > wrote: Oh, we will have the same problem! Frenetic protocol library uses Core, mostly for s-expressions. So far, I wa= s testing it with unix config to figure out build and controller communicat= ion problems. Any idea of how we can make it work for xen? I think we have to modify Fren= etic library to compile on both unix and xen, but try to keep this modifica= tion as light as possible until we have Core ported to Mirage. On 10/09/14 10:33, Anil Madhavapeddy wrote: Hi Ania, Mort is correct -- we haven't completely finishing porting Core to Mirage. = This requires breaking it down into smaller Unix-free chunks, which the up= stream maintainers (Jane Street) have already started doing. Core consists= of several sub-libraries, of which the Unix-free subset is Core_kernel. C= ore_kernel still requires a few minor C stubs (around Bigarray handling) wh= ich should work with the trunk build of Mirage (untested). Overall though, if you're interested in getting on with applications in Mir= age *right now*, you should avoid Core for now. Using Core_kernel is prett= y close though, so I'll take a look at that. -anil On 10 Sep 2014, at 10:05, Richard Mortier > wrote: unfortunately, aiui, core can't presently be used to build for xen -- as i = said, i think moves are afoot to fix this but it's a non-trivial thing to d= o so i don't know what the timeline is (or even if that's explicitly on the= timeline). i don't know core well, but i know at least one issue is that t= he threading library (Core.Async) is alike to but not completely compatible= with Lwt. others on the list are better placed to comment on if/when Core code will b= e usable with Xen :) On 10 Sep 2014, at 09:43, Ania Skorupa > wrote: Hi, thanks for your reply :) I am trying to build a piece of ocaml program in m= irage, which doesn't have a very large codebase. from errors, it looks that core is one of the libraries that results in thi= s error. in the code, I found that Core.Std is opened. Is that a library th= at can not be used for xen? skimming through the code, I didn't find explic= it unix dependencies. On Tuesday, September 9, 2014 6:32 PM, Richard Mortier > wrote: Hi, I'd guess so, yes. Anything that depends on the underlying platform (Unix)= needs to be abstracted to work with mirage. Specifically, all those modules in the error message have unix dependencies= that aren't being satisfied, though I believe work is ongoing to split js = core up to have a kernel part that will be more compatible with he mirage a= pproach. What are you trying to do? It might be that there are alternative mirage co= mpatible libraries already available (though that might not help much if yo= u're looking at porting a large codebase of course :) -- Cheers, R. On 9 Sep 2014, at 19:13, "Ania Skorupa" > wrote: Hello guys, When I compile my mirage application for xen, the following error happens: File "_none_", line 1: Error: No implementations provided for the following modules: UnixLabels referenced from /home/user/.opam/system/lib/core/core.c= mxa(Core) Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread), /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_ke= rnel), /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexpl= ib_unix), /home/user/.opam/system/lib/core/core.cmxa(Core) Command exited with code 2. Am I using libraries that can not be used to for xen unikernel? _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel -- Cheers, R. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel 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. 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 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 -- 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 er= ror, please send it back to me, and immediately delete it. Please do not u= se, copy or disclose the information contained in this message or in any att= achment. Any views or opinions expressed by the author of this email do not= necessarily reflect the views of the University of Nottingham.=0D=0A =0D=0A This message has been checked for viruses but the contents of an attachment= =0D=0A may still contain software viruses which could damage your computer system,= you are advised to perform your own checks. Email communications with the U= niversity of Nottingham may be monitored as permitted by UK legislation.=0D=0A =0D=0A =0D=0A =0D=0A =0D=0A --_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
On 15 Sep 20= 14, at 15:27, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

=20 =20
I don't use _oasis. I have core_kernel added to the ocamlfind libraries in config.ml--and hence, it is added to the packages in Makefile.

(may be worth posting a= pointer to the code in github...?)


On 15/09/14 15:17, Thomas Gazagnaire wrote:
By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
         Unix reference= d from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_ke= rnel)

I guess you need to change your build system to link with core_cornel (and if it's _oasis, regenerate the build files by running `oasis setup` at the root of your project).

Thomas


any suggestion?

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine.  It's easiest to fork Frenetic i= n the short term and shift it to using Core_kernel instead of Core.  There will be probably be an Async scheduler= , which is a lot more work to fix.  This requires shifti= ng the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release?  We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud= .koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires = a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.= uk> wrote:

unf= ortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com= > wrote:


= Hi,

thank= s for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <R= ichard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Speci= fically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Che= ers,
R.<= /div>
On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

H= ello guys,

When I compile my mirage application for xen, the following error happens:
File "_none_", line 1:
Error: No implementations provided for the following modules:
   = ;      UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
   = ;      Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
   = ;        /home/user/.opam/= system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
   = ;        /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),    = ;        /home/user/.opam/= system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?
<= br class=3D"" clear=3D"none">

_______________________________________________
= MirageOS-devel mailing list
= MirageOS-devel@lists.xenpro= ject.org
= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirage= os-devel




-- 
Cheers,<= span class=3D"Apple-style-span" style=3D"font-family: monospace;">

R.




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



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 d= o not use, copy or disclose the information contained in this message or in any attachment.  Any vie= ws or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message ha= s 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.


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


=20

This message and any attachment are intended solely for the addresse= e and may contain confidential information. If you have received this messa= ge in error, please send it back to me, and immediately delete it. &nb= sp; Please do not use, copy or disclose the information contained in this m= essage or in any attachment.  Any views or opinions expressed by the a= uthor of this email do not necessarily reflect the views of the University = of Nottingham.

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


_______________________________________________
MirageOS-devel mailing l= ist
MirageOS-deve= l@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/l= istinfo/mirageos-devel


-- 
Cheers,

R.





=

This message and any attachment are intended solely for the addressee an= d may contain confidential information. If you have received this message in= error, please send it back to me, and immediately delete it.   Pl= ease 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 Nottin= gham.

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


= = --_000_3D20168FED6B4FDAB755B0F7D9A03245nottinghamacuk_-- --===============1549912867169668106== 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 --===============1549912867169668106==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 16:50:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 16:50: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 1XTZU8-0001ih-Es; Mon, 15 Sep 2014 16:50:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTZU7-0001ic-Dn for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 16:50:39 +0000 Received: from [85.158.143.35:36901] by server-3.bemta-4.messagelabs.com id 6E/D8-06192-ED817145; Mon, 15 Sep 2014 16:50:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1410799836!13895680!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2789 invoked from network); 15 Sep 2014 16:50:36 -0000 Received: from bark.recoil.org (HELO bark.bytemark.co.uk) (5.153.225.51) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 16:50:36 -0000 Received: from [10.0.1.34] (host81-149-212-230.in-addr.btopenworld.com [81.149.212.230]); by bark.bytemark.co.uk (OpenSMTPD) with ESMTPSA id 23eaa74d; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 15 Sep 2014 17:51:18 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 15 Sep 2014 17:50:33 +0100 Message-Id: <63ECDAC5-438C-4113-92AE-748ABB4E206B@recoil.org> References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> To: Jon Crowcroft X-Mailer: Apple Mail (2.1878.6) Cc: Thomas Gazagnaire , mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1807491619975816667==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1807491619975816667== Content-Type: multipart/alternative; boundary="Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A" --Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Absolutely agree here -- the underlying structures in Irmin are = basically the same, with the challenge being the reconciliation = protocols to converge faster (which we worked on this summer with = Matthieu and Magnus) -a On 15 Sep 2014, at 15:52, Jon Crowcroft = wrote: > esp. use of (sparse, very big) merkle trees, gossip for consistency, = etc >=20 > reminded me should also re-view work from MPI on dealing with = adversaries (e.g. peer review etc > http://www.mpi-sws.org/~druschel/publications/peerreview-sosp07.pdf >=20 > On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = wrote: > v cool >=20 > here's a (another) possible use case for irmin: > http://queue.acm.org/detail.cfm?id=3D2668154 >=20 > In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, = Thomas Gazagn > aire typed: >=20 > >>Hi all, > >> > >>Lots of people starting asked me about the status of Irmin. As you = might have notice, I'vent had much time to spend on Irmin last month, = but I plan to fix that. My current priorities are: > >> > >>1/ make Irmin compiles on the Xen backend of Mirage. = https://github.com/mirage/irmin/issues/81 > >>This means dropping the dependency to core_kernel (for now on). The = external API will not change. > >> > >>2/ improve the high-level JSON API. This is related to = https://github.com/mirage/irmin/issues/80 > >>Currently, we only have a JSON API for the low-level stores, and = the very partial implementation of the higher-level calls. Needs to = complete and document that. > >> > >>3/ implement a pure-ocaml Git server to be able to at least `git = pull` from it. https://github.com/mirage/ocaml-git/issues/15 > >>Together with 1/ this will make possible to query the state of a = running Mirage unikernel with a simple `git pull ` > >> > >>4/ implement a simple distributed log server = .https://github.com/mirage/irmin/issues/82 > >>Could use Benjamin's rope implementation, that I first need to = release properly. > >> > >>5/ try to come up with a solution to the "unlimited" memory/storage = usage issues https://github.com/mirage/irmin/issues/83 > >>This is the most uncertain part of the short-term roadmap. I'll = need to check again what are the limitation of Git shallow copies and = see how we can use them to limit the history size to remember. > >> > >>There are also few open embarrassing bugs that I want to fix as = well (regarding fd leaks ...). > >> > >>If anyone is interested to help me on any of these topics, please = feel free to comment on the related issues on Github -- I'll gladly = share the workload. Also, feel free to reply to that email if you think = there is any important Imrin features that you think are missing now. > >> > >>Best, > >>Thomas > >>_______________________________________________ > >>MirageOS-devel mailing list > >>MirageOS-devel@lists.xenproject.org > >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > cheers >=20 > jon >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Absolutely agree here -- the underlying structures = in Irmin are basically the same, with the challenge being the = reconciliation protocols to converge faster (which we worked on this = summer with Matthieu and = Magnus)

-a

On 15 = Sep 2014, at 15:52, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk&= gt; wrote:

esp. use of (sparse, very big) merkle = trees, gossip for consistency, etc

reminded me should = also re-view work from MPI on dealing with adversaries (e.g. peer review = etc

On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = <Jon.Crowcroft@cl.cam.ac.uk> = wrote:
v cool

here's a (another) possible use case for irmin:
http://queue.acm.org/detail.cfm?id=3D2668154

In missive <69D665= AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas Gazagn
aire typed:

 >>Hi all,
 >>
 >>Lots of people starting asked me about the status of = Irmin. As you might have notice, I'vent had much time to spend on Irmin = last month, but I plan to fix that. My current priorities are:
 >>
 >>1/ make Irmin compiles on the Xen backend of Mirage.  = https://github.com/mirage/irmin/issues/81
 >>This means dropping the dependency to core_kernel (for now = on). The external API will not change.
 >>
 >>2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80
 >>Currently, we only have a JSON API for the low-level = stores, and the very partial implementation of the higher-level calls. = Needs to complete and document that.
 >>
 >>3/ implement a pure-ocaml Git server to be able to at = least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15
 >>Together with 1/ this will make possible to query the = state of a running Mirage unikernel with a simple `git pull = <vm-address>`
 >>
 >>4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82
 >>Could use Benjamin's rope implementation, that I first = need to release properly.
 >>
 >>5/ try to come up with a solution to the "unlimited" = memory/storage usage issues https://github.com/mirage/irmin/issues/83
 >>This is the most uncertain part of the short-term roadmap. = I'll need to check again what are the limitation of Git shallow copies = and see how we can use them to limit the history size to remember.
 >>
 >>There are also few open embarrassing bugs that I want to = fix as well (regarding fd leaks ...).
 >>
 >>If anyone is interested to help me on any of these topics, = please feel free to comment on the related issues on Github -- I'll = gladly share the workload. Also, feel free to reply to that email if you = think there is any important Imrin features that you think are missing = now.
 >>
 >>Best,
 >>Thomas
 >>_______________________________________________
 >>MirageOS-devel mailing list
 >>MirageOS-devel@lists.x= enproject.org
 >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel

 cheers

   jon


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

= --Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A-- --===============1807491619975816667== 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 --===============1807491619975816667==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 16:50:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 16:50: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 1XTZU8-0001ih-Es; Mon, 15 Sep 2014 16:50:40 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTZU7-0001ic-Dn for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 16:50:39 +0000 Received: from [85.158.143.35:36901] by server-3.bemta-4.messagelabs.com id 6E/D8-06192-ED817145; Mon, 15 Sep 2014 16:50:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1410799836!13895680!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_40_50,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2789 invoked from network); 15 Sep 2014 16:50:36 -0000 Received: from bark.recoil.org (HELO bark.bytemark.co.uk) (5.153.225.51) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 16:50:36 -0000 Received: from [10.0.1.34] (host81-149-212-230.in-addr.btopenworld.com [81.149.212.230]); by bark.bytemark.co.uk (OpenSMTPD) with ESMTPSA id 23eaa74d; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 15 Sep 2014 17:51:18 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 15 Sep 2014 17:50:33 +0100 Message-Id: <63ECDAC5-438C-4113-92AE-748ABB4E206B@recoil.org> References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> To: Jon Crowcroft X-Mailer: Apple Mail (2.1878.6) Cc: Thomas Gazagnaire , mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1807491619975816667==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1807491619975816667== Content-Type: multipart/alternative; boundary="Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A" --Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Absolutely agree here -- the underlying structures in Irmin are = basically the same, with the challenge being the reconciliation = protocols to converge faster (which we worked on this summer with = Matthieu and Magnus) -a On 15 Sep 2014, at 15:52, Jon Crowcroft = wrote: > esp. use of (sparse, very big) merkle trees, gossip for consistency, = etc >=20 > reminded me should also re-view work from MPI on dealing with = adversaries (e.g. peer review etc > http://www.mpi-sws.org/~druschel/publications/peerreview-sosp07.pdf >=20 > On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = wrote: > v cool >=20 > here's a (another) possible use case for irmin: > http://queue.acm.org/detail.cfm?id=3D2668154 >=20 > In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, = Thomas Gazagn > aire typed: >=20 > >>Hi all, > >> > >>Lots of people starting asked me about the status of Irmin. As you = might have notice, I'vent had much time to spend on Irmin last month, = but I plan to fix that. My current priorities are: > >> > >>1/ make Irmin compiles on the Xen backend of Mirage. = https://github.com/mirage/irmin/issues/81 > >>This means dropping the dependency to core_kernel (for now on). The = external API will not change. > >> > >>2/ improve the high-level JSON API. This is related to = https://github.com/mirage/irmin/issues/80 > >>Currently, we only have a JSON API for the low-level stores, and = the very partial implementation of the higher-level calls. Needs to = complete and document that. > >> > >>3/ implement a pure-ocaml Git server to be able to at least `git = pull` from it. https://github.com/mirage/ocaml-git/issues/15 > >>Together with 1/ this will make possible to query the state of a = running Mirage unikernel with a simple `git pull ` > >> > >>4/ implement a simple distributed log server = .https://github.com/mirage/irmin/issues/82 > >>Could use Benjamin's rope implementation, that I first need to = release properly. > >> > >>5/ try to come up with a solution to the "unlimited" memory/storage = usage issues https://github.com/mirage/irmin/issues/83 > >>This is the most uncertain part of the short-term roadmap. I'll = need to check again what are the limitation of Git shallow copies and = see how we can use them to limit the history size to remember. > >> > >>There are also few open embarrassing bugs that I want to fix as = well (regarding fd leaks ...). > >> > >>If anyone is interested to help me on any of these topics, please = feel free to comment on the related issues on Github -- I'll gladly = share the workload. Also, feel free to reply to that email if you think = there is any important Imrin features that you think are missing now. > >> > >>Best, > >>Thomas > >>_______________________________________________ > >>MirageOS-devel mailing list > >>MirageOS-devel@lists.xenproject.org > >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > cheers >=20 > jon >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Absolutely agree here -- the underlying structures = in Irmin are basically the same, with the challenge being the = reconciliation protocols to converge faster (which we worked on this = summer with Matthieu and = Magnus)

-a

On 15 = Sep 2014, at 15:52, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk&= gt; wrote:

esp. use of (sparse, very big) merkle = trees, gossip for consistency, etc

reminded me should = also re-view work from MPI on dealing with adversaries (e.g. peer review = etc

On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = <Jon.Crowcroft@cl.cam.ac.uk> = wrote:
v cool

here's a (another) possible use case for irmin:
http://queue.acm.org/detail.cfm?id=3D2668154

In missive <69D665= AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas Gazagn
aire typed:

 >>Hi all,
 >>
 >>Lots of people starting asked me about the status of = Irmin. As you might have notice, I'vent had much time to spend on Irmin = last month, but I plan to fix that. My current priorities are:
 >>
 >>1/ make Irmin compiles on the Xen backend of Mirage.  = https://github.com/mirage/irmin/issues/81
 >>This means dropping the dependency to core_kernel (for now = on). The external API will not change.
 >>
 >>2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80
 >>Currently, we only have a JSON API for the low-level = stores, and the very partial implementation of the higher-level calls. = Needs to complete and document that.
 >>
 >>3/ implement a pure-ocaml Git server to be able to at = least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15
 >>Together with 1/ this will make possible to query the = state of a running Mirage unikernel with a simple `git pull = <vm-address>`
 >>
 >>4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82
 >>Could use Benjamin's rope implementation, that I first = need to release properly.
 >>
 >>5/ try to come up with a solution to the "unlimited" = memory/storage usage issues https://github.com/mirage/irmin/issues/83
 >>This is the most uncertain part of the short-term roadmap. = I'll need to check again what are the limitation of Git shallow copies = and see how we can use them to limit the history size to remember.
 >>
 >>There are also few open embarrassing bugs that I want to = fix as well (regarding fd leaks ...).
 >>
 >>If anyone is interested to help me on any of these topics, = please feel free to comment on the related issues on Github -- I'll = gladly share the workload. Also, feel free to reply to that email if you = think there is any important Imrin features that you think are missing = now.
 >>
 >>Best,
 >>Thomas
 >>_______________________________________________
 >>MirageOS-devel mailing list
 >>MirageOS-devel@lists.x= enproject.org
 >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel

 cheers

   jon


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

= --Apple-Mail=_A2DE1CE0-2DD0-4184-84DB-A52763A8231A-- --===============1807491619975816667== 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 --===============1807491619975816667==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 16:59:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 16:59: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 1XTZd5-0001uP-O9; Mon, 15 Sep 2014 16:59:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTZd3-0001uH-Dn for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 16:59:53 +0000 Received: from [85.158.143.35:24717] by server-1.bemta-4.messagelabs.com id 35/EA-05872-80B17145; Mon, 15 Sep 2014 16:59:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1410800390!13906781!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21943 invoked from network); 15 Sep 2014 16:59:50 -0000 Received: from bark.recoil.org (HELO bark.bytemark.co.uk) (5.153.225.51) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 16:59:50 -0000 Received: from [10.0.1.34] (host81-149-212-230.in-addr.btopenworld.com [81.149.212.230]); by bark.bytemark.co.uk (OpenSMTPD) with ESMTPSA id 40745cca; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 15 Sep 2014 18:00:32 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <5416F21A.3010505@nottingham.ac.uk> Date: Mon, 15 Sep 2014 17:59:45 +0100 Message-Id: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4934587774659760290==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4934587774659760290== Content-Type: multipart/alternative; boundary="Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9" --Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This is expected behaviour (almost, which I'll get to shortly). By = replacing Core.Std with Core_kernel.Std, any uses of Unix within = Frenetic must now be factored out. However, there appears to be a small lurking reference to Unix in the = latest Core_kernel release, in one of the constituent modules. I've = opened a bug here: https://github.com/janestreet/core_kernel/issues/21 -anil On 15 Sep 2014, at 15:05, Masoud Koleini = wrote: > Hi Anil, >=20 > By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic = library, and adding core_kernel to the config.ml, I receive error: >=20 > Error: No implementations provided for the following modules: > Unix referenced from = /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) >=20 > any suggestion? >=20 > On 10/09/14 15:55, Anil Madhavapeddy wrote: >> (Re-adding the devel list to CC) >>=20 >> The s-expression library is actually independent of Unix, so that's = fine. It's easiest to fork Frenetic in the short term and shift it to = using Core_kernel instead of Core. There will be probably be an Async = scheduler, which is a lot more work to fix. This requires shifting the = Async portions to use Async_kernel instead, which Jane Street is working = on. >>=20 >> CCing Yaron -- any sense of how far away Async_kernel is from a = public release? We can get started on an Async_xen port then as well. >>=20 >> -anil >>=20 >> On 10 Sep 2014, at 10:55, Masoud Koleini = wrote: >>=20 >>> Oh, we will have the same problem! >>>=20 >>> Frenetic protocol library uses Core, mostly for s-expressions. So = far, I was testing it with unix config to figure out build and = controller communication problems. >>>=20 >>> Any idea of how we can make it work for xen? I think we have to = modify Frenetic library to compile on both unix and xen, but try to keep = this modification as light as possible until we have Core ported to = Mirage. >>>=20 >>>=20 >>> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>>> Hi Ania, >>>>=20 >>>> Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). >>>>=20 >>>> Overall though, if you're interested in getting on with = applications in Mirage *right now*, you should avoid Core for now. = Using Core_kernel is pretty close though, so I'll take a look at that. >>>>=20 >>>> -anil >>>>=20 >>>> On 10 Sep 2014, at 10:05, Richard Mortier = wrote: >>>>=20 >>>>> unfortunately, aiui, core can't presently be used to build for xen = -- as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >>>>>=20 >>>>> others on the list are better placed to comment on if/when Core = code will be usable with Xen :) >>>>>=20 >>>>> On 10 Sep 2014, at 09:43, Ania Skorupa = wrote: >>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>>>>>=20 >>>>>> from errors, it looks that core is one of the libraries that = results in this error. in the code, I found that Core.Std is opened. Is = that a library that can not be used for xen? skimming through the code, = I didn't find explicit unix dependencies. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> I'd guess so, yes. Anything that depends on the underlying = platform (Unix) needs to be abstracted to work with mirage. >>>>>>=20 >>>>>> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>>>>>=20 >>>>>> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>>>>>=20 >>>>>> -- =20 >>>>>> Cheers, >>>>>>=20 >>>>>> R. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>>>>>=20 >>>>>>> Hello guys, >>>>>>>=20 >>>>>>> When I compile my mirage application for xen, the following = error happens: >>>>>>>=20 >>>>>>> File "_none_", line 1: >>>>>>> Error: No implementations provided for the following modules: >>>>>>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Command exited with code 2. >>>>>>>=20 >>>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>>>=20 >>>>>>>=20 >>>>>>> _______________________________________________ >>>>>>> MirageOS-devel mailing list >>>>>>> MirageOS-devel@lists.xenproject.org >>>>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> Cheers, >>>>>=20 >>>>> R. >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@lists.xenproject.org >>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>=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 >=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 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii This is expected behaviour (almost, which I'll get to shortly).  By replacing Core.Std with Core_kernel.Std, any uses of Unix within Frenetic must now be factored out.

However, there appears to be a small lurking reference to Unix in the latest Core_kernel release, in one of the constituent modules.  I've opened a bug here:

-anil

On 15 Sep 2014, at 15:05, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Hi Anil,

By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
         Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

any suggestion?

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine.  It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core.  There will be probably be an Async scheduler, which is a lot more work to fix.  This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release?  We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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




-- 
Cheers,

R.




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



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.


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

--Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9-- --===============4934587774659760290== 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 --===============4934587774659760290==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 16:59:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 16:59: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 1XTZd5-0001uP-O9; Mon, 15 Sep 2014 16:59:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTZd3-0001uH-Dn for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 16:59:53 +0000 Received: from [85.158.143.35:24717] by server-1.bemta-4.messagelabs.com id 35/EA-05872-80B17145; Mon, 15 Sep 2014 16:59:52 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1410800390!13906781!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, HTML_MESSAGE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21943 invoked from network); 15 Sep 2014 16:59:50 -0000 Received: from bark.recoil.org (HELO bark.bytemark.co.uk) (5.153.225.51) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 16:59:50 -0000 Received: from [10.0.1.34] (host81-149-212-230.in-addr.btopenworld.com [81.149.212.230]); by bark.bytemark.co.uk (OpenSMTPD) with ESMTPSA id 40745cca; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 15 Sep 2014 18:00:32 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <5416F21A.3010505@nottingham.ac.uk> Date: Mon, 15 Sep 2014 17:59:45 +0100 Message-Id: References: <1410285991.50936.YahooMailNeo@web142402.mail.bf1.yahoo.com> <1410338600.12980.YahooMailNeo@web142405.mail.bf1.yahoo.com> <25707E90-222A-4239-8FBA-9339CB347755@recoil.org> <54101FF4.40109@nottingham.ac.uk> <06E7DFC8-CF0F-4909-AE64-F2B740F2C2DC@recoil.org> <5416F21A.3010505@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: Yaron Minsky , Spiros Eliopoulos , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Compile mirage application for xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4934587774659760290==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4934587774659760290== Content-Type: multipart/alternative; boundary="Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9" --Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This is expected behaviour (almost, which I'll get to shortly). By = replacing Core.Std with Core_kernel.Std, any uses of Unix within = Frenetic must now be factored out. However, there appears to be a small lurking reference to Unix in the = latest Core_kernel release, in one of the constituent modules. I've = opened a bug here: https://github.com/janestreet/core_kernel/issues/21 -anil On 15 Sep 2014, at 15:05, Masoud Koleini = wrote: > Hi Anil, >=20 > By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic = library, and adding core_kernel to the config.ml, I receive error: >=20 > Error: No implementations provided for the following modules: > Unix referenced from = /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel) >=20 > any suggestion? >=20 > On 10/09/14 15:55, Anil Madhavapeddy wrote: >> (Re-adding the devel list to CC) >>=20 >> The s-expression library is actually independent of Unix, so that's = fine. It's easiest to fork Frenetic in the short term and shift it to = using Core_kernel instead of Core. There will be probably be an Async = scheduler, which is a lot more work to fix. This requires shifting the = Async portions to use Async_kernel instead, which Jane Street is working = on. >>=20 >> CCing Yaron -- any sense of how far away Async_kernel is from a = public release? We can get started on an Async_xen port then as well. >>=20 >> -anil >>=20 >> On 10 Sep 2014, at 10:55, Masoud Koleini = wrote: >>=20 >>> Oh, we will have the same problem! >>>=20 >>> Frenetic protocol library uses Core, mostly for s-expressions. So = far, I was testing it with unix config to figure out build and = controller communication problems. >>>=20 >>> Any idea of how we can make it work for xen? I think we have to = modify Frenetic library to compile on both unix and xen, but try to keep = this modification as light as possible until we have Core ported to = Mirage. >>>=20 >>>=20 >>> On 10/09/14 10:33, Anil Madhavapeddy wrote: >>>> Hi Ania, >>>>=20 >>>> Mort is correct -- we haven't completely finishing porting Core to = Mirage. This requires breaking it down into smaller Unix-free chunks, = which the upstream maintainers (Jane Street) have already started doing. = Core consists of several sub-libraries, of which the Unix-free subset = is Core_kernel. Core_kernel still requires a few minor C stubs (around = Bigarray handling) which should work with the trunk build of Mirage = (untested). >>>>=20 >>>> Overall though, if you're interested in getting on with = applications in Mirage *right now*, you should avoid Core for now. = Using Core_kernel is pretty close though, so I'll take a look at that. >>>>=20 >>>> -anil >>>>=20 >>>> On 10 Sep 2014, at 10:05, Richard Mortier = wrote: >>>>=20 >>>>> unfortunately, aiui, core can't presently be used to build for xen = -- as i said, i think moves are afoot to fix this but it's a non-trivial = thing to do so i don't know what the timeline is (or even if that's = explicitly on the timeline). i don't know core well, but i know at least = one issue is that the threading library (Core.Async) is alike to but not = completely compatible with Lwt. >>>>>=20 >>>>> others on the list are better placed to comment on if/when Core = code will be usable with Xen :) >>>>>=20 >>>>> On 10 Sep 2014, at 09:43, Ania Skorupa = wrote: >>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> thanks for your reply :) I am trying to build a piece of ocaml = program in mirage, which doesn't have a very large codebase.=20 >>>>>>=20 >>>>>> from errors, it looks that core is one of the libraries that = results in this error. in the code, I found that Core.Std is opened. Is = that a library that can not be used for xen? skimming through the code, = I didn't find explicit unix dependencies. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On Tuesday, September 9, 2014 6:32 PM, Richard Mortier = wrote: >>>>>>=20 >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> I'd guess so, yes. Anything that depends on the underlying = platform (Unix) needs to be abstracted to work with mirage. >>>>>>=20 >>>>>> Specifically, all those modules in the error message have unix = dependencies that aren't being satisfied, though I believe work is = ongoing to split js core up to have a kernel part that will be more = compatible with he mirage approach. >>>>>>=20 >>>>>> What are you trying to do? It might be that there are alternative = mirage compatible libraries already available (though that might not = help much if you're looking at porting a large codebase of course :) >>>>>>=20 >>>>>> -- =20 >>>>>> Cheers, >>>>>>=20 >>>>>> R. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> On 9 Sep 2014, at 19:13, "Ania Skorupa" = wrote: >>>>>>=20 >>>>>>> Hello guys, >>>>>>>=20 >>>>>>> When I compile my mirage application for xen, the following = error happens: >>>>>>>=20 >>>>>>> File "_none_", line 1: >>>>>>> Error: No implementations provided for the following modules: >>>>>>> UnixLabels referenced from = /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Unix referenced from = /usr/lib/ocaml/threads/threads.cmxa(Thread), >>>>>>> = /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel), >>>>>>> = /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix), >>>>>>> /home/user/.opam/system/lib/core/core.cmxa(Core) >>>>>>> Command exited with code 2. >>>>>>>=20 >>>>>>> Am I using libraries that can not be used to for xen unikernel? >>>>>>>=20 >>>>>>>=20 >>>>>>> _______________________________________________ >>>>>>> MirageOS-devel mailing list >>>>>>> MirageOS-devel@lists.xenproject.org >>>>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>>>=20 >>>>>>=20 >>>>>=20 >>>>>=20 >>>>> --=20 >>>>> Cheers, >>>>>=20 >>>>> R. >>>>>=20 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> _______________________________________________ >>>>> MirageOS-devel mailing list >>>>> MirageOS-devel@lists.xenproject.org >>>>> = http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>>=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 >=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 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii This is expected behaviour (almost, which I'll get to shortly).  By replacing Core.Std with Core_kernel.Std, any uses of Unix within Frenetic must now be factored out.

However, there appears to be a small lurking reference to Unix in the latest Core_kernel release, in one of the constituent modules.  I've opened a bug here:

-anil

On 15 Sep 2014, at 15:05, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Hi Anil,

By changing "open Core.Std" to "open Core_kernel.Std" in Frenetic library, and adding core_kernel to the config.ml, I receive error:

Error: No implementations provided for the following modules:
         Unix referenced from /home/psz/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel)

any suggestion?

On 10/09/14 15:55, Anil Madhavapeddy wrote:
(Re-adding the devel list to CC)

The s-expression library is actually independent of Unix, so that's fine.  It's easiest to fork Frenetic in the short term and shift it to using Core_kernel instead of Core.  There will be probably be an Async scheduler, which is a lot more work to fix.  This requires shifting the Async portions to use Async_kernel instead, which Jane Street is working on.

CCing Yaron -- any sense of how far away Async_kernel is from a public release?  We can get started on an Async_xen port then as well.

-anil

On 10 Sep 2014, at 10:55, Masoud Koleini <masoud.koleini@nottingham.ac.uk> wrote:

Oh, we will have the same problem!

Frenetic protocol library uses Core, mostly for s-expressions. So far, I was testing it with unix config to figure out build and controller communication problems.

Any idea of how we can make it work for xen? I think we have to modify Frenetic library to compile on both unix and xen, but try to keep this modification as light as possible until we have Core ported to Mirage.


On 10/09/14 10:33, Anil Madhavapeddy wrote:
Hi Ania,

Mort is correct -- we haven't completely finishing porting Core to Mirage.  This requires breaking it down into smaller Unix-free chunks, which the upstream maintainers (Jane Street) have already started doing.  Core consists of several sub-libraries, of which the Unix-free subset is Core_kernel.  Core_kernel still requires a few minor C stubs (around Bigarray handling) which should work with the trunk build of Mirage (untested).

Overall though, if you're interested in getting on with applications in Mirage *right now*, you should avoid Core for now.  Using Core_kernel is pretty close though, so I'll take a look at that.

-anil

On 10 Sep 2014, at 10:05, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

unfortunately, aiui, core can't presently be used to build for xen -- as i said, i think moves are afoot to fix this but it's a non-trivial thing to do so i don't know what the timeline is (or even if that's explicitly on the timeline). i don't know core well, but i know at least one issue is that the threading library (Core.Async) is alike to but not completely compatible with Lwt.

others on the list are better placed to comment on if/when Core code will be usable with Xen :)

On 10 Sep 2014, at 09:43, Ania Skorupa <ania.skorupa@yahoo.com> wrote:


Hi,

thanks for your reply :) I am trying to build a piece of ocaml program in mirage, which doesn't have a very large codebase. 

from errors, it looks that core is one of the libraries that results in this error. in the code, I found that Core.Std is opened. Is that a library that can not be used for xen? skimming through the code, I didn't find explicit unix dependencies.



On Tuesday, September 9, 2014 6:32 PM, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:


Hi,

I'd guess so, yes.  Anything that depends on the underlying platform (Unix) needs to be abstracted to work with mirage.

Specifically, all those modules in the error message have unix dependencies that aren't being satisfied, though I believe work is ongoing to split js core up to have a kernel part that will be more compatible with he mirage approach.

What are you trying to do? It might be that there are alternative mirage compatible libraries already available (though that might not help much if you're looking at porting a large codebase of course :)

--  
Cheers,

R.



On 9 Sep 2014, at 19:13, "Ania Skorupa" <ania.skorupa@yahoo.com> wrote:

Hello guys,

When I compile my mirage application for xen, the following error happens:

File "_none_", line 1:
Error: No implementations provided for the following modules:
         UnixLabels referenced from /home/user/.opam/system/lib/core/core.cmxa(Core)
         Unix referenced from /usr/lib/ocaml/threads/threads.cmxa(Thread),
           /home/user/.opam/system/lib/core_kernel/core_kernel.cmxa(Core_kernel),
           /home/user/.opam/system/lib/sexplib_unix/sexplib_unix.cmxa(Sexplib_unix),
           /home/user/.opam/system/lib/core/core.cmxa(Core)
Command exited with code 2.

Am I using libraries that can not be used to for xen unikernel?


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




-- 
Cheers,

R.




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



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.


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

--Apple-Mail=_FC5F4007-5228-42F5-A88C-C1054A62FAF9-- --===============4934587774659760290== 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 --===============4934587774659760290==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 22:46:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 22:46:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTf2A-0008EC-Pz; Mon, 15 Sep 2014 22:46:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTf29-0008E5-KV for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 22:46:09 +0000 Received: from [85.158.139.211:41973] by server-2.bemta-5.messagelabs.com id D7/61-31832-03C67145; Mon, 15 Sep 2014 22:46:08 +0000 X-Env-Sender: n.oje.bar@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1410821165!14660870!1 X-Originating-IP: [209.85.192.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21133 invoked from network); 15 Sep 2014 22:46:06 -0000 Received: from mail-qg0-f52.google.com (HELO mail-qg0-f52.google.com) (209.85.192.52) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 22:46:06 -0000 Received: by mail-qg0-f52.google.com with SMTP id i50so4773278qgf.11 for ; Mon, 15 Sep 2014 15:46:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=5dc59+wH7tCxYRdnGuSj37Z8GMYwaeFBxsSydYGZ9Yo=; b=wx/cVmxgVi2LGrfX80Eas09hI4Y860lDSivzMhN1M3bgs4JUTcQ737M/HCdIngz6VX fjV/zqi38tmwjcUoZ6KPHy+Vk8N98dN7YybPF3jvoAEsRM1WY/1zEyDCUka/aXN8snMY IgmF5loKBbp9s2QbBCgYuDoNS0DznLjw08kGaD+zPfz5/6njE1Bl5G7c8oMZQQN6WXEJ zNBukfKEMYcB8ioejbtPqurr/MdcLTczmiGfcQea6K7pf+3UAPP7aITnuTfF/4kQJC5M AsOlsL+x8L61UO/KPbacNJAR0VzDDvSlt0g5dQfgVwz+MpAY8+C9s/4vmKmiL9/3fBS6 nQww== MIME-Version: 1.0 X-Received: by 10.140.33.228 with SMTP id j91mr34738026qgj.68.1410819824453; Mon, 15 Sep 2014 15:23:44 -0700 (PDT) Received: by 10.224.15.195 with HTTP; Mon, 15 Sep 2014 15:23:44 -0700 (PDT) Date: Mon, 15 Sep 2014 23:23:44 +0100 X-Google-Sender-Auth: DC4ckBbwST57YaQkZU665j8f-c0 Message-ID: From: Nicolas Ojeda Bar To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5185926119556801605==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5185926119556801605== Content-Type: multipart/alternative; boundary=001a113a78007aa8f80503221656 --001a113a78007aa8f80503221656 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear list, Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to install Xen/Mirage guided by the following sets of instructions: [1]: https://github.com/mirage/xen-arm-builder [2]: http://openmirage.org/wiki/install [3]: http://openmirage.org/wiki/hello-world TL;DR: The link to the pre-built binaries in [1] is broken, but building from source I was able to successfully install mirage on the Cubieboard and run the UNIX version of the Hello, World! unikernel. However, the Xen version did not work because the opam package mirage-xen 1.1.1 did not compile (some comman= d line options were not recognized by cc). The full build log is at . It seems that this problem should be quite easy to solve by someone more knowledgeable than me. I am also sharing the exact steps I took to set up the Cubieboard in case they are of use to someone else. Best wishes, Nicolas How to install Xen/Mirage on a Cubieboard 2 ------------------------------------------- This is a record of what I had to do to install Xen on a Cubieboard 2. I a= m sending it to the list in case it is of use to someone else. Before we start, ingredients: - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. - Cubieboard 2. See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg So, let's get started. Step 1: Go to https://github.com/mirage/xen-arm-builder. Click on the link that advertises a pre-built binary for the cubieboard2 and realize that it is not working. We have to build from source. Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Downloads = > VirtualBox 4.3.16 for OS X hosts). Run the provided installer. Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/server. Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can find it. Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive (this turned out to be extremely tight to build xen-arm-builder, so I recommend making it at least 9GB to give yourself some more room). When prompted for an installation CD, locate the ISO file that you downloaded in Step 3. Step 5: Follow the prompts and install Ubuntu. Make sure to install sshd when prompted (we want to avoid having to use the VirtualBox UI at all costs). Step 6: (Optional?) Fix the Wi-Fi in VirtualBox. For some reason the network speeds in VirtualBox would start up ok and then suddendly slow down to a crawl. After some googling and some blind guessing I could solve it for my setup. Simply go to Settings > Network and change the drop-down menu 'Attached to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart the VM. Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' interface. Step 7: SSH into the VM from your normal (OS X) terminal. Open a terminal and type 'ssh @' where is the addres= s from the previous step. Log in. Step 8: Install git and clone xen-arm-builder from github. sudo apt-get install git git clone https://github.com/mirage/xen-arm-builder cd xen-arm-builder Step 9: Follow the instructions in the xen-arm-builder README. export BOARD=3Dcubieboard2 make clone make build make cubieboard2.img # Exit the ssh session exit # Get the cubieboard2.img file over to the OS X side scp @:xen-arm-builder/cubieboard2.img . # Insert SDcard into your computer and copy the .img file into it # Find the disk device of the card you inserted, say diskN sudo diskutil list # Unmount the disk images sudo diskutil unmountDisk /dev/diskN # Copy the image - This automatically remounts the disk sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k # Unmount the image and eject sudo diskutil unmountDisk /dev/diskN # Insert SDcard into Cubieboard, connect the Cubieboard power & network. # The cubieboard will obtain an IP address via DHCP and will also # broadcast itself on Bonjour (Zeroconf) under the name # 'cubieboard2.local.' (note the dot at the end). So you should be able # to connect the cubieboard to your local network with an ethernet cable # and then do ssh mirage@cubieboard2.local. # (password is 'mirage') and voila! you're connected. Step 10: Install Mirage. # We follow the instructions at http://openmirage.org/wiki/install= , # except that we can skip the first section, 'Requirements'. opam init eval `opam config env` opam install mirage Step 11: Build Hello, World! example, UNIX version. git clone https://github.com/mirage/mirage-skeleton cd mirage-skeleton cd console mirage configure --unix make depend make ./mir-console Step 12: Build Hello, World! example, Xen version [FAILED!]. mirage configure --xen Fails while compiling mirage-xen 1.1.1 with the C compiler cc complaining about some unrecognized command line options cc: error: unrecognized command line option =E2=80=98-m64=E2=80=99 cc: error: unrecognized command line option =E2=80=98-mno-red-zone= =E2=80=99 cc: error: unrecognized command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99 cc: error: unrecognized command line option =E2=80=98-mfancy-math-= 387=E2=80=99 The full log is at < https://gist.github.com/nojb/b7972e42e317160771c5>. --001a113a78007aa8f80503221656 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set= out to
install Xen/Mirage guided by the following sets of instru= ctions:


TL= ;DR: The link to the pre-built binaries in [1] is broken, but building from=
source I was able to successfully install mirage on the Cubieboa= rd and run the
UNIX version of the Hello, World! unikernel. =C2= =A0However, the Xen version did not
work because the opam package= mirage-xen 1.1.1 did not compile (some command
line options were= not recognized by cc). =C2=A0The full build log is at

It seems t= hat this problem should be quite easy to solve by someone more
kn= owledgeable than me.

I am also sharing the exact s= teps I took to set up the Cubieboard in case they
are of use to s= omeone else.

Best wishes,
Nicolas
<= div>
How to install Xen/Mirage on a Cubieboard 2
--= -----------------------------------------

This is = a record of what I had to do to install Xen on a Cubieboard 2. =C2=A0I am
sending it to the list in case it is of use to someone else.
=

Before we start, ingredients:

= =C2=A0 =C2=A0 =C2=A0 =C2=A0 - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM= .
=C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Cubieboar= d 2.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 See pic here: http://s28.postimg.org/xdou7ajv= x/image.jpg

So, let's get started.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Click on the link that advertises a pre= -built binary for the cubieboard2
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and= realize that it is not working. =C2=A0We have to build from source.
<= div>
Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Downloads >
=C2=A0 =C2=A0 =C2=A0 =C2=A0 VirtualBox 4.3.16 for OS X hosts). Run the pr= ovided installer.

Step 3: Get Ubuntu Server 14.04.= 1 LTS from www.ubuntu.com= /download/server.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 = Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
=C2=A0 =C2=A0 =C2=A0 =C2=A0 find it.

Step 4:= In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I assigned 2GB RAM (out of a total of 8= GB) and 8GB Hard drive (this
=C2=A0 =C2=A0 =C2=A0 =C2=A0 turned o= ut to be extremely tight to build xen-arm-builder, so I
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 recommend making it at least 9GB to give yourself some= more room).
=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 When prompted for an installation CD, locate the ISO f= ile that you
=C2=A0 =C2=A0 =C2=A0 =C2=A0 downloaded in Step 3.

Step 5: Follow the prompts and install Ubuntu.
=

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Make sure to install sshd w= hen prompted (we want to avoid having to use
=C2=A0 =C2=A0 =C2=A0= =C2=A0 the VirtualBox UI at all costs).

Step 6: (= Optional?) Fix the Wi-Fi in VirtualBox.

=C2=A0 =C2= =A0 =C2=A0 =C2=A0 For some reason the network speeds in VirtualBox would st= art up ok and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 then suddendly slow dow= n to a crawl. =C2=A0After some googling and some blind
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 guessing I could solve it for my setup.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Simply go to Settings > Network and = change the drop-down menu 'Attached
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK= and restart the VM.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Log in and type = 'ifconfig'. Note the 'inet addr' of the 'eth0' inte= rface.

Step 7: SSH into the VM from your normal (O= S X) terminal.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Open a = terminal and type 'ssh <user>@<ip>' where <ip> is= the address
=C2=A0 =C2=A0 =C2=A0 =C2=A0 from the previous step. = Log in.

Step 8: Install git and clone xen-arm-buil= der from github.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo = apt-get install git
=C2=A0 =C2=A0 =C2=A0 =C2=A0 git clone https://github.com/mirage/xe= n-arm-builder
=C2=A0 =C2=A0 =C2=A0 =C2=A0 cd xen-arm-builder<= /div>

Step 9: Follow the instructions in the xen-arm-bui= lder README.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 export BO= ARD=3Dcubieboard2
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make clone
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make build
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 make cubieboard2.img
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Exit the s= sh session
=C2=A0 =C2=A0 =C2=A0 =C2=A0 exit
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 # Get the cubieboard2.img file over to the OS X side
=C2=A0 =C2=A0 =C2=A0 =C2=A0 scp <user>@<ip>:xen-arm-build= er/cubieboard2.img .

=C2=A0 =C2=A0 =C2=A0 =C2=A0 #= Insert SDcard into your computer and copy the .img file into it
=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Find the disk device of the ca= rd you inserted, say diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo disku= til list
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Unmount the disk images
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil unmountDisk /dev/diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Copy the image - This automatically r= emounts the disk
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo dd if=3Dcubiebo= ard2.img of=3D/dev/rdiskN bs=3D64k
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # = Unmount the image and eject
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo disk= util unmountDisk /dev/diskN

=C2=A0 =C2=A0 =C2=A0 = =C2=A0 # Insert SDcard into Cubieboard, connect the Cubieboard power & = network.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # The cubiebo= ard will obtain an IP address via DHCP and will also
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 # broadcast itself on Bonjour (Zeroconf) under the name
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # 'cubieboard2.local.' (note t= he dot at the end). =C2=A0So you should be able
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 # to connect the cubieboard to your local network with an ethern= et cable
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # and then do

=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ssh mirage@cubieboard2.local.
<= div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # (password is 'mirage&#= 39;) and voila! you're connected.

Step 10: Ins= tall Mirage.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0# W= e follow the instructions at http://openmirage.org/wiki/install,
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0# except that we can skip the first section, 'Requirements= 9;.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam init
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0eval `opam config env`
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam install mirage

<= div>Step 11: Build Hello, World! example, UNIX version.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0git clone https://github.com/mirage/mirage-skeleton<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd mirage-skeleton
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd console
=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0mirage configure --unix
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0make depend
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirage configure --xen
<= div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Fails while compiling = mirage-xen 1.1.1 with the C compiler cc
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0complaining about some unrecognized command line options

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecognized = command line option =E2=80=98-m64=E2=80=99
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0cc: error: unrecognized command line option =E2=80=98-mno-red-= zone=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unreco= gnized command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecognized command lin= e option =E2=80=98-mfancy-math-387=E2=80=99

=C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0The full log is at <https://gist.github.com/nojb/b7972e42= e317160771c5>.

--001a113a78007aa8f80503221656-- --===============5185926119556801605== 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 --===============5185926119556801605==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 22:46:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 22:46:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTf2A-0008EC-Pz; Mon, 15 Sep 2014 22:46:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTf29-0008E5-KV for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 22:46:09 +0000 Received: from [85.158.139.211:41973] by server-2.bemta-5.messagelabs.com id D7/61-31832-03C67145; Mon, 15 Sep 2014 22:46:08 +0000 X-Env-Sender: n.oje.bar@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1410821165!14660870!1 X-Originating-IP: [209.85.192.52] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21133 invoked from network); 15 Sep 2014 22:46:06 -0000 Received: from mail-qg0-f52.google.com (HELO mail-qg0-f52.google.com) (209.85.192.52) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 22:46:06 -0000 Received: by mail-qg0-f52.google.com with SMTP id i50so4773278qgf.11 for ; Mon, 15 Sep 2014 15:46:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=5dc59+wH7tCxYRdnGuSj37Z8GMYwaeFBxsSydYGZ9Yo=; b=wx/cVmxgVi2LGrfX80Eas09hI4Y860lDSivzMhN1M3bgs4JUTcQ737M/HCdIngz6VX fjV/zqi38tmwjcUoZ6KPHy+Vk8N98dN7YybPF3jvoAEsRM1WY/1zEyDCUka/aXN8snMY IgmF5loKBbp9s2QbBCgYuDoNS0DznLjw08kGaD+zPfz5/6njE1Bl5G7c8oMZQQN6WXEJ zNBukfKEMYcB8ioejbtPqurr/MdcLTczmiGfcQea6K7pf+3UAPP7aITnuTfF/4kQJC5M AsOlsL+x8L61UO/KPbacNJAR0VzDDvSlt0g5dQfgVwz+MpAY8+C9s/4vmKmiL9/3fBS6 nQww== MIME-Version: 1.0 X-Received: by 10.140.33.228 with SMTP id j91mr34738026qgj.68.1410819824453; Mon, 15 Sep 2014 15:23:44 -0700 (PDT) Received: by 10.224.15.195 with HTTP; Mon, 15 Sep 2014 15:23:44 -0700 (PDT) Date: Mon, 15 Sep 2014 23:23:44 +0100 X-Google-Sender-Auth: DC4ckBbwST57YaQkZU665j8f-c0 Message-ID: From: Nicolas Ojeda Bar To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5185926119556801605==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5185926119556801605== Content-Type: multipart/alternative; boundary=001a113a78007aa8f80503221656 --001a113a78007aa8f80503221656 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear list, Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to install Xen/Mirage guided by the following sets of instructions: [1]: https://github.com/mirage/xen-arm-builder [2]: http://openmirage.org/wiki/install [3]: http://openmirage.org/wiki/hello-world TL;DR: The link to the pre-built binaries in [1] is broken, but building from source I was able to successfully install mirage on the Cubieboard and run the UNIX version of the Hello, World! unikernel. However, the Xen version did not work because the opam package mirage-xen 1.1.1 did not compile (some comman= d line options were not recognized by cc). The full build log is at . It seems that this problem should be quite easy to solve by someone more knowledgeable than me. I am also sharing the exact steps I took to set up the Cubieboard in case they are of use to someone else. Best wishes, Nicolas How to install Xen/Mirage on a Cubieboard 2 ------------------------------------------- This is a record of what I had to do to install Xen on a Cubieboard 2. I a= m sending it to the list in case it is of use to someone else. Before we start, ingredients: - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. - Cubieboard 2. See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg So, let's get started. Step 1: Go to https://github.com/mirage/xen-arm-builder. Click on the link that advertises a pre-built binary for the cubieboard2 and realize that it is not working. We have to build from source. Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Downloads = > VirtualBox 4.3.16 for OS X hosts). Run the provided installer. Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/server. Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can find it. Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive (this turned out to be extremely tight to build xen-arm-builder, so I recommend making it at least 9GB to give yourself some more room). When prompted for an installation CD, locate the ISO file that you downloaded in Step 3. Step 5: Follow the prompts and install Ubuntu. Make sure to install sshd when prompted (we want to avoid having to use the VirtualBox UI at all costs). Step 6: (Optional?) Fix the Wi-Fi in VirtualBox. For some reason the network speeds in VirtualBox would start up ok and then suddendly slow down to a crawl. After some googling and some blind guessing I could solve it for my setup. Simply go to Settings > Network and change the drop-down menu 'Attached to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart the VM. Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' interface. Step 7: SSH into the VM from your normal (OS X) terminal. Open a terminal and type 'ssh @' where is the addres= s from the previous step. Log in. Step 8: Install git and clone xen-arm-builder from github. sudo apt-get install git git clone https://github.com/mirage/xen-arm-builder cd xen-arm-builder Step 9: Follow the instructions in the xen-arm-builder README. export BOARD=3Dcubieboard2 make clone make build make cubieboard2.img # Exit the ssh session exit # Get the cubieboard2.img file over to the OS X side scp @:xen-arm-builder/cubieboard2.img . # Insert SDcard into your computer and copy the .img file into it # Find the disk device of the card you inserted, say diskN sudo diskutil list # Unmount the disk images sudo diskutil unmountDisk /dev/diskN # Copy the image - This automatically remounts the disk sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k # Unmount the image and eject sudo diskutil unmountDisk /dev/diskN # Insert SDcard into Cubieboard, connect the Cubieboard power & network. # The cubieboard will obtain an IP address via DHCP and will also # broadcast itself on Bonjour (Zeroconf) under the name # 'cubieboard2.local.' (note the dot at the end). So you should be able # to connect the cubieboard to your local network with an ethernet cable # and then do ssh mirage@cubieboard2.local. # (password is 'mirage') and voila! you're connected. Step 10: Install Mirage. # We follow the instructions at http://openmirage.org/wiki/install= , # except that we can skip the first section, 'Requirements'. opam init eval `opam config env` opam install mirage Step 11: Build Hello, World! example, UNIX version. git clone https://github.com/mirage/mirage-skeleton cd mirage-skeleton cd console mirage configure --unix make depend make ./mir-console Step 12: Build Hello, World! example, Xen version [FAILED!]. mirage configure --xen Fails while compiling mirage-xen 1.1.1 with the C compiler cc complaining about some unrecognized command line options cc: error: unrecognized command line option =E2=80=98-m64=E2=80=99 cc: error: unrecognized command line option =E2=80=98-mno-red-zone= =E2=80=99 cc: error: unrecognized command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99 cc: error: unrecognized command line option =E2=80=98-mfancy-math-= 387=E2=80=99 The full log is at < https://gist.github.com/nojb/b7972e42e317160771c5>. --001a113a78007aa8f80503221656 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set= out to
install Xen/Mirage guided by the following sets of instru= ctions:


TL= ;DR: The link to the pre-built binaries in [1] is broken, but building from=
source I was able to successfully install mirage on the Cubieboa= rd and run the
UNIX version of the Hello, World! unikernel. =C2= =A0However, the Xen version did not
work because the opam package= mirage-xen 1.1.1 did not compile (some command
line options were= not recognized by cc). =C2=A0The full build log is at

It seems t= hat this problem should be quite easy to solve by someone more
kn= owledgeable than me.

I am also sharing the exact s= teps I took to set up the Cubieboard in case they
are of use to s= omeone else.

Best wishes,
Nicolas
<= div>
How to install Xen/Mirage on a Cubieboard 2
--= -----------------------------------------

This is = a record of what I had to do to install Xen on a Cubieboard 2. =C2=A0I am
sending it to the list in case it is of use to someone else.
=

Before we start, ingredients:

= =C2=A0 =C2=A0 =C2=A0 =C2=A0 - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM= .
=C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Cubieboar= d 2.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 See pic here: http://s28.postimg.org/xdou7ajv= x/image.jpg

So, let's get started.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Click on the link that advertises a pre= -built binary for the cubieboard2
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and= realize that it is not working. =C2=A0We have to build from source.
<= div>
Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Downloads >
=C2=A0 =C2=A0 =C2=A0 =C2=A0 VirtualBox 4.3.16 for OS X hosts). Run the pr= ovided installer.

Step 3: Get Ubuntu Server 14.04.= 1 LTS from www.ubuntu.com= /download/server.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 = Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
=C2=A0 =C2=A0 =C2=A0 =C2=A0 find it.

Step 4:= In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I assigned 2GB RAM (out of a total of 8= GB) and 8GB Hard drive (this
=C2=A0 =C2=A0 =C2=A0 =C2=A0 turned o= ut to be extremely tight to build xen-arm-builder, so I
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 recommend making it at least 9GB to give yourself some= more room).
=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 When prompted for an installation CD, locate the ISO f= ile that you
=C2=A0 =C2=A0 =C2=A0 =C2=A0 downloaded in Step 3.

Step 5: Follow the prompts and install Ubuntu.
=

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Make sure to install sshd w= hen prompted (we want to avoid having to use
=C2=A0 =C2=A0 =C2=A0= =C2=A0 the VirtualBox UI at all costs).

Step 6: (= Optional?) Fix the Wi-Fi in VirtualBox.

=C2=A0 =C2= =A0 =C2=A0 =C2=A0 For some reason the network speeds in VirtualBox would st= art up ok and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 then suddendly slow dow= n to a crawl. =C2=A0After some googling and some blind
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 guessing I could solve it for my setup.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Simply go to Settings > Network and = change the drop-down menu 'Attached
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK= and restart the VM.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Log in and type = 'ifconfig'. Note the 'inet addr' of the 'eth0' inte= rface.

Step 7: SSH into the VM from your normal (O= S X) terminal.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Open a = terminal and type 'ssh <user>@<ip>' where <ip> is= the address
=C2=A0 =C2=A0 =C2=A0 =C2=A0 from the previous step. = Log in.

Step 8: Install git and clone xen-arm-buil= der from github.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo = apt-get install git
=C2=A0 =C2=A0 =C2=A0 =C2=A0 git clone https://github.com/mirage/xe= n-arm-builder
=C2=A0 =C2=A0 =C2=A0 =C2=A0 cd xen-arm-builder<= /div>

Step 9: Follow the instructions in the xen-arm-bui= lder README.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 export BO= ARD=3Dcubieboard2
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make clone
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make build
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 make cubieboard2.img
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Exit the s= sh session
=C2=A0 =C2=A0 =C2=A0 =C2=A0 exit
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 # Get the cubieboard2.img file over to the OS X side
=C2=A0 =C2=A0 =C2=A0 =C2=A0 scp <user>@<ip>:xen-arm-build= er/cubieboard2.img .

=C2=A0 =C2=A0 =C2=A0 =C2=A0 #= Insert SDcard into your computer and copy the .img file into it
=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Find the disk device of the ca= rd you inserted, say diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo disku= til list
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Unmount the disk images
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil unmountDisk /dev/diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Copy the image - This automatically r= emounts the disk
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo dd if=3Dcubiebo= ard2.img of=3D/dev/rdiskN bs=3D64k
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # = Unmount the image and eject
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo disk= util unmountDisk /dev/diskN

=C2=A0 =C2=A0 =C2=A0 = =C2=A0 # Insert SDcard into Cubieboard, connect the Cubieboard power & = network.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # The cubiebo= ard will obtain an IP address via DHCP and will also
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 # broadcast itself on Bonjour (Zeroconf) under the name
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # 'cubieboard2.local.' (note t= he dot at the end). =C2=A0So you should be able
=C2=A0 =C2=A0 =C2= =A0 =C2=A0 # to connect the cubieboard to your local network with an ethern= et cable
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # and then do

=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ssh mirage@cubieboard2.local.
<= div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # (password is 'mirage&#= 39;) and voila! you're connected.

Step 10: Ins= tall Mirage.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0# W= e follow the instructions at http://openmirage.org/wiki/install,
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0# except that we can skip the first section, 'Requirements= 9;.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam init
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0eval `opam config env`
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam install mirage

<= div>Step 11: Build Hello, World! example, UNIX version.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0git clone https://github.com/mirage/mirage-skeleton<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd mirage-skeleton
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd console
=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0mirage configure --unix
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0make depend
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirage configure --xen
<= div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Fails while compiling = mirage-xen 1.1.1 with the C compiler cc
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0complaining about some unrecognized command line options

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecognized = command line option =E2=80=98-m64=E2=80=99
=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0cc: error: unrecognized command line option =E2=80=98-mno-red-= zone=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unreco= gnized command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecognized command lin= e option =E2=80=98-mfancy-math-387=E2=80=99

=C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0The full log is at <https://gist.github.com/nojb/b7972e42= e317160771c5>.

--001a113a78007aa8f80503221656-- --===============5185926119556801605== 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 --===============5185926119556801605==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 22:57:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 22:57:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTfCs-0000Us-Do; Mon, 15 Sep 2014 22:57:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTfCr-0000Un-Pe for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 22:57:14 +0000 Received: from [85.158.137.68:51305] by server-12.bemta-3.messagelabs.com id 81/AD-01574-9CE67145; Mon, 15 Sep 2014 22:57:13 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-15.tower-31.messagelabs.com!1410821830!14580932!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1650 invoked from network); 15 Sep 2014 22:57:10 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-15.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 22:57:10 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc16-cmbg14-2-0-cust188.5-4.cable.virginm.net ([86.6.156.189]:47739 helo=[192.168.1.123]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:jjl25) (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1XTfCo-0003Br-qB (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 15 Sep 2014 23:57:10 +0100 Message-ID: <54176EC5.2070902@cam.ac.uk> Date: Mon, 15 Sep 2014 23:57:09 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: In-Reply-To: Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4873651727599227253==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============4873651727599227253== Content-Type: multipart/alternative; boundary="------------080509080102000803070603" This is a multi-part message in MIME format. --------------080509080102000803070603 Content-Type: text/plain; charset=windows-1252 Content-Length: 6871 Content-Transfer-Encoding: quoted-printable Hi Nicolas, I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam. Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minios-arm - in particular the 'opam pin' commands. Good luck! Jon On 15/09/14 23:23, Nicolas Ojeda Bar wrote: > Dear list, > > Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and > set out to > install Xen/Mirage guided by the following sets of instructions: > > [1]: https://github.com/mirage/xen-arm-builder > [2]: http://openmirage.org/wiki/install > [3]: http://openmirage.org/wiki/hello-world > > TL;DR: The link to the pre-built binaries in [1] is broken, but > building from > source I was able to successfully install mirage on the Cubieboard and > run the > UNIX version of the Hello, World! unikernel. However, the Xen version > did not > work because the opam package mirage-xen 1.1.1 did not compile (some > command > line options were not recognized by cc). The full build log is at > . > > It seems that this problem should be quite easy to solve by someone more > knowledgeable than me. > > I am also sharing the exact steps I took to set up the Cubieboard in > case they > are of use to someone else. > > Best wishes, > Nicolas > > How to install Xen/Mirage on a Cubieboard 2 > ------------------------------------------- > > This is a record of what I had to do to install Xen on a Cubieboard 2. > I am > sending it to the list in case it is of use to someone else. > > Before we start, ingredients: > > - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. > > - Cubieboard 2. > See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg > > So, let's get started. > > Step 1: Go to https://github.com/mirage/xen-arm-builder. > > Click on the link that advertises a pre-built binary for the > cubieboard2 > and realize that it is not working. We have to build from source. > > Step 2: Get VirtualBox for OS X from https://www.virtualbox.org > (Downloads > > VirtualBox 4.3.16 for OS X hosts). Run the provided installer. > > Step 3: Get Ubuntu Server 14.04.1 LTS from > www.ubuntu.com/download/server . > > Save the image ubuntu-14.04.1-server-amd64.iso somewhere where > you can > find it. > > Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). > > I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive > (this > turned out to be extremely tight to build xen-arm-builder, so I > recommend making it at least 9GB to give yourself some more room). > > When prompted for an installation CD, locate the ISO file that you > downloaded in Step 3. > > Step 5: Follow the prompts and install Ubuntu. > > Make sure to install sshd when prompted (we want to avoid > having to use > the VirtualBox UI at all costs). > > Step 6: (Optional=3F) Fix the Wi-Fi in VirtualBox. > > For some reason the network speeds in VirtualBox would start > up ok and > then suddendly slow down to a crawl. After some googling and > some blind > guessing I could solve it for my setup. > > Simply go to Settings > Network and change the drop-down menu > 'Attached > to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and > restart the VM. > Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' > interface. > > Step 7: SSH into the VM from your normal (OS X) terminal. > > Open a terminal and type 'ssh @' where is the > address > from the previous step. Log in. > > Step 8: Install git and clone xen-arm-builder from github. > > sudo apt-get install git > git clone https://github.com/mirage/xen-arm-builder > cd xen-arm-builder > > Step 9: Follow the instructions in the xen-arm-builder README. > > export BOARD=3Dcubieboard2 > make clone > make build > make cubieboard2.img > # Exit the ssh session > exit > # Get the cubieboard2.img file over to the OS X side > scp @:xen-arm-builder/cubieboard2.img . > > # Insert SDcard into your computer and copy the .img file into it > > # Find the disk device of the card you inserted, say diskN > sudo diskutil list > # Unmount the disk images > sudo diskutil unmountDisk /dev/diskN > # Copy the image - This automatically remounts the disk > sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k > # Unmount the image and eject > sudo diskutil unmountDisk /dev/diskN > > # Insert SDcard into Cubieboard, connect the Cubieboard power > & network. > > # The cubieboard will obtain an IP address via DHCP and will also > # broadcast itself on Bonjour (Zeroconf) under the name > # 'cubieboard2.local.' (note the dot at the end). So you > should be able > # to connect the cubieboard to your local network with an > ethernet cable > # and then do > > ssh mirage@cubieboard2.local. > > # (password is 'mirage') and voila! you're connected. > > Step 10: Install Mirage. > > # We follow the instructions at > http://openmirage.org/wiki/install, > # except that we can skip the first section, 'Requirements'. > > opam init > eval `opam config env` > opam install mirage > > Step 11: Build Hello, World! example, UNIX version. > > git clone https://github.com/mirage/mirage-skeleton > cd mirage-skeleton > cd console > mirage configure --unix > make depend > make > ./mir-console > > Step 12: Build Hello, World! example, Xen version [FAILED!]. > > mirage configure --xen > > Fails while compiling mirage-xen 1.1.1 with the C compiler cc > complaining about some unrecognized command line options > > cc: error: unrecognized command line option =91-m64=92 > cc: error: unrecognized command line option =91-mno-red-zone=92 > cc: error: unrecognized command line option > =91-momit-leaf-frame-pointer=92 > cc: error: unrecognized command line option =91-mfancy-math-387=92 > > The full log is at > . > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --------------080509080102000803070603 Content-Type: text/html; charset=windows-1252 Content-Length: 15917 Content-Transfer-Encoding: quoted-printable
Hi Nicolas,

I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam.

Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minios-arm - in particular the 'opam pin' commands.

Good luck!

Jon


On 15/09/14 23:23, Nicolas Ojeda Bar wrote:
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to
install Xen/Mirage guided by the following sets of instructions:


TL;DR: The link to the pre-built binaries in [1] is broken, but building from
source I was able to successfully install mirage on the Cubieboard and run the
UNIX version of the Hello, World! unikernel. =A0However, the Xen version did not
work because the opam package mirage-xen 1.1.1 did not compile (some command
line options were not recognized by cc). =A0The full build log is at

It seems that this problem should be quite easy to solve by someone more
knowledgeable than me.

I am also sharing the exact steps I took to set up the Cubieboard in case they
are of use to someone else.

Best wishes,
Nicolas

How to install Xen/Mirage on a Cubieboard 2
-------------------------------------------

This is a record of what I had to do to install Xen on a Cubieboard 2. =A0I am
sending it to the list in case it is of use to someone else.

Before we start, ingredients:

=A0 =A0 =A0 =A0 - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM.
=A0 =A0
=A0 =A0 =A0 =A0 - Cubieboard 2.
=A0 =A0 =A0 =A0 =A0 See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg

So, let's get started.


=A0 =A0 =A0 =A0 Click on the link that advertises a pre-built binary for the cubieboard2
=A0 =A0 =A0 =A0 and realize that it is not working. =A0We have to build from source.

Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Downloads >
=A0 =A0 =A0 =A0 VirtualBox 4.3.16 for OS X hosts). Run the provided installer.

Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/server.

=A0 =A0 =A0 =A0 Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
=A0 =A0 =A0 =A0 find it.

Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

=A0 =A0 =A0 =A0 I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive (this
=A0 =A0 =A0 =A0 turned out to be extremely tight to build xen-arm-builder, so I
=A0 =A0 =A0 =A0 recommend making it at least 9GB to give yourself some more room).
=A0 =A0 =A0 =A0=A0
=A0 =A0 =A0 =A0 When prompted for an installation CD, locate the ISO file that you
=A0 =A0 =A0 =A0 downloaded in Step 3.

Step 5: Follow the prompts and install Ubuntu.

=A0 =A0 =A0 =A0 Make sure to install sshd when prompted (we want to avoid having to use
=A0 =A0 =A0 =A0 the VirtualBox UI at all costs).

Step 6: (Optional=3F) Fix the Wi-Fi in VirtualBox.

=A0 =A0 =A0 =A0 For some reason the network speeds in VirtualBox would start up ok and
=A0 =A0 =A0 =A0 then suddendly slow down to a crawl. =A0After some googling and some blind
=A0 =A0 =A0 =A0 guessing I could solve it for my setup.

=A0 =A0 =A0 =A0 Simply go to Settings > Network and change the drop-down menu 'Attached
=A0 =A0 =A0 =A0 to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart the VM.
=A0 =A0 =A0 =A0 Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' interface.

Step 7: SSH into the VM from your normal (OS X) terminal.

=A0 =A0 =A0 =A0 Open a terminal and type 'ssh <user>@<ip>' where <ip> is the address
=A0 =A0 =A0 =A0 from the previous step. Log in.

Step 8: Install git and clone xen-arm-builder from github.

=A0 =A0 =A0 =A0 sudo apt-get install git
=A0 =A0 =A0 =A0 cd xen-arm-builder

Step 9: Follow the instructions in the xen-arm-builder README.

=A0 =A0 =A0 =A0 export BOARD=3Dcubieboard2
=A0 =A0 =A0 =A0 make clone
=A0 =A0 =A0 =A0 make build
=A0 =A0 =A0 =A0 make cubieboard2.img
=A0 =A0 =A0 =A0 # Exit the ssh session
=A0 =A0 =A0 =A0 exit
=A0 =A0 =A0 =A0 # Get the cubieboard2.img file over to the OS X side
=A0 =A0 =A0 =A0 scp <user>@<ip>:xen-arm-builder/cubieboard2.img .

=A0 =A0 =A0 =A0 # Insert SDcard into your computer and copy the .img file into it

=A0 =A0 =A0 =A0 # Find the disk device of the card you inserted, say diskN
=A0 =A0 =A0 =A0 sudo diskutil list
=A0 =A0 =A0 =A0 # Unmount the disk images
=A0 =A0 =A0 =A0 sudo diskutil unmountDisk /dev/diskN
=A0 =A0 =A0 =A0 # Copy the image - This automatically remounts the disk
=A0 =A0 =A0 =A0 sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k
=A0 =A0 =A0 =A0 # Unmount the image and eject
=A0 =A0 =A0 =A0 sudo diskutil unmountDisk /dev/diskN

=A0 =A0 =A0 =A0 # Insert SDcard into Cubieboard, connect the Cubieboard power & network.

=A0 =A0 =A0 =A0 # The cubieboard will obtain an IP address via DHCP and will also
=A0 =A0 =A0 =A0 # broadcast itself on Bonjour (Zeroconf) under the name
=A0 =A0 =A0 =A0 # 'cubieboard2.local.' (note the dot at the end). =A0So you should be able
=A0 =A0 =A0 =A0 # to connect the cubieboard to your local network with an ethernet cable
=A0 =A0 =A0 =A0 # and then do

=A0 =A0 =A0 =A0 ssh mirage@cubieboard2.local.

=A0 =A0 =A0 =A0 # (password is 'mirage') and voila! you're connected.

Step 10: Install Mirage.

=A0 =A0 =A0 =A0 =A0# We follow the instructions at http://openmirage.org/wiki/install,
=A0 =A0 =A0 =A0 =A0# except that we can skip the first section, 'Requirements'.

=A0 =A0 =A0 =A0 =A0opam init
=A0 =A0 =A0 =A0 =A0eval `opam config env`
=A0 =A0 =A0 =A0 =A0opam install mirage

Step 11: Build Hello, World! example, UNIX version.

=A0 =A0 =A0 =A0 =A0git clone https://github.com/mirage/mirage-skeleton
=A0 =A0 =A0 =A0 =A0cd mirage-skeleton
=A0 =A0 =A0 =A0 =A0cd console
=A0 =A0 =A0 =A0 =A0mirage configure --unix
=A0 =A0 =A0 =A0 =A0make depend
=A0 =A0 =A0 =A0 =A0make
=A0 =A0 =A0 =A0 =A0./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].

=A0 =A0 =A0 =A0 =A0mirage configure --xen

=A0 =A0 =A0 =A0 =A0Fails while compiling mirage-xen 1.1.1 with the C compiler cc
=A0 =A0 =A0 =A0 =A0complaining about some unrecognized command line options

=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-m64=92
=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-mno-red-zone=92
=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-momit-leaf-frame-pointer=92
=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-mfancy-math-387=92

=A0 =A0 =A0 =A0 =A0The full log is at <https://gist.github.com/nojb/b7972e42e317160771c5>.



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

--------------080509080102000803070603-- --===============4873651727599227253== 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 --===============4873651727599227253==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 22:57:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 22:57:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTfCs-0000Us-Do; Mon, 15 Sep 2014 22:57:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTfCr-0000Un-Pe for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 22:57:14 +0000 Received: from [85.158.137.68:51305] by server-12.bemta-3.messagelabs.com id 81/AD-01574-9CE67145; Mon, 15 Sep 2014 22:57:13 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-15.tower-31.messagelabs.com!1410821830!14580932!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1650 invoked from network); 15 Sep 2014 22:57:10 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-15.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 22:57:10 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc16-cmbg14-2-0-cust188.5-4.cable.virginm.net ([86.6.156.189]:47739 helo=[192.168.1.123]) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:jjl25) (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1XTfCo-0003Br-qB (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 15 Sep 2014 23:57:10 +0100 Message-ID: <54176EC5.2070902@cam.ac.uk> Date: Mon, 15 Sep 2014 23:57:09 +0100 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: In-Reply-To: Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4873651727599227253==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============4873651727599227253== Content-Type: multipart/alternative; boundary="------------080509080102000803070603" This is a multi-part message in MIME format. --------------080509080102000803070603 Content-Type: text/plain; charset=windows-1252 Content-Length: 6871 Content-Transfer-Encoding: quoted-printable Hi Nicolas, I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam. Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minios-arm - in particular the 'opam pin' commands. Good luck! Jon On 15/09/14 23:23, Nicolas Ojeda Bar wrote: > Dear list, > > Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and > set out to > install Xen/Mirage guided by the following sets of instructions: > > [1]: https://github.com/mirage/xen-arm-builder > [2]: http://openmirage.org/wiki/install > [3]: http://openmirage.org/wiki/hello-world > > TL;DR: The link to the pre-built binaries in [1] is broken, but > building from > source I was able to successfully install mirage on the Cubieboard and > run the > UNIX version of the Hello, World! unikernel. However, the Xen version > did not > work because the opam package mirage-xen 1.1.1 did not compile (some > command > line options were not recognized by cc). The full build log is at > . > > It seems that this problem should be quite easy to solve by someone more > knowledgeable than me. > > I am also sharing the exact steps I took to set up the Cubieboard in > case they > are of use to someone else. > > Best wishes, > Nicolas > > How to install Xen/Mirage on a Cubieboard 2 > ------------------------------------------- > > This is a record of what I had to do to install Xen on a Cubieboard 2. > I am > sending it to the list in case it is of use to someone else. > > Before we start, ingredients: > > - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. > > - Cubieboard 2. > See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg > > So, let's get started. > > Step 1: Go to https://github.com/mirage/xen-arm-builder. > > Click on the link that advertises a pre-built binary for the > cubieboard2 > and realize that it is not working. We have to build from source. > > Step 2: Get VirtualBox for OS X from https://www.virtualbox.org > (Downloads > > VirtualBox 4.3.16 for OS X hosts). Run the provided installer. > > Step 3: Get Ubuntu Server 14.04.1 LTS from > www.ubuntu.com/download/server . > > Save the image ubuntu-14.04.1-server-amd64.iso somewhere where > you can > find it. > > Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). > > I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive > (this > turned out to be extremely tight to build xen-arm-builder, so I > recommend making it at least 9GB to give yourself some more room). > > When prompted for an installation CD, locate the ISO file that you > downloaded in Step 3. > > Step 5: Follow the prompts and install Ubuntu. > > Make sure to install sshd when prompted (we want to avoid > having to use > the VirtualBox UI at all costs). > > Step 6: (Optional=3F) Fix the Wi-Fi in VirtualBox. > > For some reason the network speeds in VirtualBox would start > up ok and > then suddendly slow down to a crawl. After some googling and > some blind > guessing I could solve it for my setup. > > Simply go to Settings > Network and change the drop-down menu > 'Attached > to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and > restart the VM. > Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' > interface. > > Step 7: SSH into the VM from your normal (OS X) terminal. > > Open a terminal and type 'ssh @' where is the > address > from the previous step. Log in. > > Step 8: Install git and clone xen-arm-builder from github. > > sudo apt-get install git > git clone https://github.com/mirage/xen-arm-builder > cd xen-arm-builder > > Step 9: Follow the instructions in the xen-arm-builder README. > > export BOARD=3Dcubieboard2 > make clone > make build > make cubieboard2.img > # Exit the ssh session > exit > # Get the cubieboard2.img file over to the OS X side > scp @:xen-arm-builder/cubieboard2.img . > > # Insert SDcard into your computer and copy the .img file into it > > # Find the disk device of the card you inserted, say diskN > sudo diskutil list > # Unmount the disk images > sudo diskutil unmountDisk /dev/diskN > # Copy the image - This automatically remounts the disk > sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k > # Unmount the image and eject > sudo diskutil unmountDisk /dev/diskN > > # Insert SDcard into Cubieboard, connect the Cubieboard power > & network. > > # The cubieboard will obtain an IP address via DHCP and will also > # broadcast itself on Bonjour (Zeroconf) under the name > # 'cubieboard2.local.' (note the dot at the end). So you > should be able > # to connect the cubieboard to your local network with an > ethernet cable > # and then do > > ssh mirage@cubieboard2.local. > > # (password is 'mirage') and voila! you're connected. > > Step 10: Install Mirage. > > # We follow the instructions at > http://openmirage.org/wiki/install, > # except that we can skip the first section, 'Requirements'. > > opam init > eval `opam config env` > opam install mirage > > Step 11: Build Hello, World! example, UNIX version. > > git clone https://github.com/mirage/mirage-skeleton > cd mirage-skeleton > cd console > mirage configure --unix > make depend > make > ./mir-console > > Step 12: Build Hello, World! example, Xen version [FAILED!]. > > mirage configure --xen > > Fails while compiling mirage-xen 1.1.1 with the C compiler cc > complaining about some unrecognized command line options > > cc: error: unrecognized command line option =91-m64=92 > cc: error: unrecognized command line option =91-mno-red-zone=92 > cc: error: unrecognized command line option > =91-momit-leaf-frame-pointer=92 > cc: error: unrecognized command line option =91-mfancy-math-387=92 > > The full log is at > . > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --------------080509080102000803070603 Content-Type: text/html; charset=windows-1252 Content-Length: 15917 Content-Transfer-Encoding: quoted-printable
Hi Nicolas,

I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam.

Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minios-arm - in particular the 'opam pin' commands.

Good luck!

Jon


On 15/09/14 23:23, Nicolas Ojeda Bar wrote:
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to
install Xen/Mirage guided by the following sets of instructions:


TL;DR: The link to the pre-built binaries in [1] is broken, but building from
source I was able to successfully install mirage on the Cubieboard and run the
UNIX version of the Hello, World! unikernel. =A0However, the Xen version did not
work because the opam package mirage-xen 1.1.1 did not compile (some command
line options were not recognized by cc). =A0The full build log is at

It seems that this problem should be quite easy to solve by someone more
knowledgeable than me.

I am also sharing the exact steps I took to set up the Cubieboard in case they
are of use to someone else.

Best wishes,
Nicolas

How to install Xen/Mirage on a Cubieboard 2
-------------------------------------------

This is a record of what I had to do to install Xen on a Cubieboard 2. =A0I am
sending it to the list in case it is of use to someone else.

Before we start, ingredients:

=A0 =A0 =A0 =A0 - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM.
=A0 =A0
=A0 =A0 =A0 =A0 - Cubieboard 2.
=A0 =A0 =A0 =A0 =A0 See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg

So, let's get started.


=A0 =A0 =A0 =A0 Click on the link that advertises a pre-built binary for the cubieboard2
=A0 =A0 =A0 =A0 and realize that it is not working. =A0We have to build from source.

Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Downloads >
=A0 =A0 =A0 =A0 VirtualBox 4.3.16 for OS X hosts). Run the provided installer.

Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/server.

=A0 =A0 =A0 =A0 Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
=A0 =A0 =A0 =A0 find it.

Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

=A0 =A0 =A0 =A0 I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive (this
=A0 =A0 =A0 =A0 turned out to be extremely tight to build xen-arm-builder, so I
=A0 =A0 =A0 =A0 recommend making it at least 9GB to give yourself some more room).
=A0 =A0 =A0 =A0=A0
=A0 =A0 =A0 =A0 When prompted for an installation CD, locate the ISO file that you
=A0 =A0 =A0 =A0 downloaded in Step 3.

Step 5: Follow the prompts and install Ubuntu.

=A0 =A0 =A0 =A0 Make sure to install sshd when prompted (we want to avoid having to use
=A0 =A0 =A0 =A0 the VirtualBox UI at all costs).

Step 6: (Optional=3F) Fix the Wi-Fi in VirtualBox.

=A0 =A0 =A0 =A0 For some reason the network speeds in VirtualBox would start up ok and
=A0 =A0 =A0 =A0 then suddendly slow down to a crawl. =A0After some googling and some blind
=A0 =A0 =A0 =A0 guessing I could solve it for my setup.

=A0 =A0 =A0 =A0 Simply go to Settings > Network and change the drop-down menu 'Attached
=A0 =A0 =A0 =A0 to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart the VM.
=A0 =A0 =A0 =A0 Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' interface.

Step 7: SSH into the VM from your normal (OS X) terminal.

=A0 =A0 =A0 =A0 Open a terminal and type 'ssh <user>@<ip>' where <ip> is the address
=A0 =A0 =A0 =A0 from the previous step. Log in.

Step 8: Install git and clone xen-arm-builder from github.

=A0 =A0 =A0 =A0 sudo apt-get install git
=A0 =A0 =A0 =A0 cd xen-arm-builder

Step 9: Follow the instructions in the xen-arm-builder README.

=A0 =A0 =A0 =A0 export BOARD=3Dcubieboard2
=A0 =A0 =A0 =A0 make clone
=A0 =A0 =A0 =A0 make build
=A0 =A0 =A0 =A0 make cubieboard2.img
=A0 =A0 =A0 =A0 # Exit the ssh session
=A0 =A0 =A0 =A0 exit
=A0 =A0 =A0 =A0 # Get the cubieboard2.img file over to the OS X side
=A0 =A0 =A0 =A0 scp <user>@<ip>:xen-arm-builder/cubieboard2.img .

=A0 =A0 =A0 =A0 # Insert SDcard into your computer and copy the .img file into it

=A0 =A0 =A0 =A0 # Find the disk device of the card you inserted, say diskN
=A0 =A0 =A0 =A0 sudo diskutil list
=A0 =A0 =A0 =A0 # Unmount the disk images
=A0 =A0 =A0 =A0 sudo diskutil unmountDisk /dev/diskN
=A0 =A0 =A0 =A0 # Copy the image - This automatically remounts the disk
=A0 =A0 =A0 =A0 sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k
=A0 =A0 =A0 =A0 # Unmount the image and eject
=A0 =A0 =A0 =A0 sudo diskutil unmountDisk /dev/diskN

=A0 =A0 =A0 =A0 # Insert SDcard into Cubieboard, connect the Cubieboard power & network.

=A0 =A0 =A0 =A0 # The cubieboard will obtain an IP address via DHCP and will also
=A0 =A0 =A0 =A0 # broadcast itself on Bonjour (Zeroconf) under the name
=A0 =A0 =A0 =A0 # 'cubieboard2.local.' (note the dot at the end). =A0So you should be able
=A0 =A0 =A0 =A0 # to connect the cubieboard to your local network with an ethernet cable
=A0 =A0 =A0 =A0 # and then do

=A0 =A0 =A0 =A0 ssh mirage@cubieboard2.local.

=A0 =A0 =A0 =A0 # (password is 'mirage') and voila! you're connected.

Step 10: Install Mirage.

=A0 =A0 =A0 =A0 =A0# We follow the instructions at http://openmirage.org/wiki/install,
=A0 =A0 =A0 =A0 =A0# except that we can skip the first section, 'Requirements'.

=A0 =A0 =A0 =A0 =A0opam init
=A0 =A0 =A0 =A0 =A0eval `opam config env`
=A0 =A0 =A0 =A0 =A0opam install mirage

Step 11: Build Hello, World! example, UNIX version.

=A0 =A0 =A0 =A0 =A0git clone https://github.com/mirage/mirage-skeleton
=A0 =A0 =A0 =A0 =A0cd mirage-skeleton
=A0 =A0 =A0 =A0 =A0cd console
=A0 =A0 =A0 =A0 =A0mirage configure --unix
=A0 =A0 =A0 =A0 =A0make depend
=A0 =A0 =A0 =A0 =A0make
=A0 =A0 =A0 =A0 =A0./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].

=A0 =A0 =A0 =A0 =A0mirage configure --xen

=A0 =A0 =A0 =A0 =A0Fails while compiling mirage-xen 1.1.1 with the C compiler cc
=A0 =A0 =A0 =A0 =A0complaining about some unrecognized command line options

=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-m64=92
=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-mno-red-zone=92
=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-momit-leaf-frame-pointer=92
=A0 =A0 =A0 =A0 =A0cc: error: unrecognized command line option =91-mfancy-math-387=92

=A0 =A0 =A0 =A0 =A0The full log is at <https://gist.github.com/nojb/b7972e42e317160771c5>.



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

--------------080509080102000803070603-- --===============4873651727599227253== 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 --===============4873651727599227253==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 23:22:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 23:22: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 1XTfay-000146-JV; Mon, 15 Sep 2014 23:22:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTfax-00013x-23 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 23:22:07 +0000 Received: from [193.109.254.147:5640] by server-16.bemta-14.messagelabs.com id F0/37-16990-E9477145; Mon, 15 Sep 2014 23:22:06 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1410823323!15680684!1 X-Originating-IP: [74.125.82.172] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 702 invoked from network); 15 Sep 2014 23:22:03 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 23:22:03 -0000 Received: by mail-we0-f172.google.com with SMTP id k48so4803713wev.31 for ; Mon, 15 Sep 2014 16:22:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nWjXHiZbHs2AXxxgk0YEb6jWkmwIsHCEtry3EnUobdM=; b=DVYsF+MU4RwrOrH5IopwIdzffPzC3owxUAEDhOtXctbAUA6YbH50JZR119feSMYGsy hnHKDRyTPa8ZJYg0Lg8F0SnVQLxfLkYWRZqTEyFGkGJu/xQsZUNhmvM/IJsJPp+tmrTl 3o9SvYRTB6jaYwz9uDugEN3do1NzQZheIdaOgb3jxf9c/cPBokeAGySuGFHi/8R0ffli zFXcR4/Dl3bii7ZJ+6saJqCo7Aj3uG0atutNLF9cEendthm2xOfSnXItS5ny/WTGbDiJ HnxJ0WcG4d3il61l5Ky11UB6G7p6fO1HRL6HdJeocs4SkeOM2mGNO6BKrqN0btYT4LOj Xa2w== MIME-Version: 1.0 X-Received: by 10.180.36.84 with SMTP id o20mr899866wij.9.1410823323291; Mon, 15 Sep 2014 16:22:03 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Mon, 15 Sep 2014 16:22:03 -0700 (PDT) In-Reply-To: <54176EC5.2070902@cam.ac.uk> References: <54176EC5.2070902@cam.ac.uk> Date: Mon, 15 Sep 2014 20:22:03 -0300 Message-ID: From: Stephen Mack To: Jon Ludlam Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7848918559801087028==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7848918559801087028== Content-Type: multipart/alternative; boundary=e89a8f502f88069385050322e79b --e89a8f502f88069385050322e79b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You can download the pre-compiled version here: http://blobs.openmirage.org= / --Stephen On Mon, Sep 15, 2014 at 7:57 PM, Jon Ludlam wrote: > Hi Nicolas, > > I believe you need more recent versions of mirage, mirage-xen and tcpip > than those that are currently available in opam. > > Take a look at Thomas Leonard's blog post here: > http://openmirage.org/blog/introducing-xen-minios-arm - in particular the > 'opam pin' commands. > > Good luck! > > Jon > > > > On 15/09/14 23:23, Nicolas Ojeda Bar wrote: > > Dear list, > > Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set > out to > install Xen/Mirage guided by the following sets of instructions: > > [1]: https://github.com/mirage/xen-arm-builder > [2]: http://openmirage.org/wiki/install > [3]: http://openmirage.org/wiki/hello-world > > TL;DR: The link to the pre-built binaries in [1] is broken, but building > from > source I was able to successfully install mirage on the Cubieboard and ru= n > the > UNIX version of the Hello, World! unikernel. However, the Xen version di= d > not > work because the opam package mirage-xen 1.1.1 did not compile (some > command > line options were not recognized by cc). The full build log is at > . > > It seems that this problem should be quite easy to solve by someone more > knowledgeable than me. > > I am also sharing the exact steps I took to set up the Cubieboard in > case they > are of use to someone else. > > Best wishes, > Nicolas > > How to install Xen/Mirage on a Cubieboard 2 > ------------------------------------------- > > This is a record of what I had to do to install Xen on a Cubieboard 2. > I am > sending it to the list in case it is of use to someone else. > > Before we start, ingredients: > > - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. > > - Cubieboard 2. > See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg > > So, let's get started. > > Step 1: Go to https://github.com/mirage/xen-arm-builder. > > Click on the link that advertises a pre-built binary for the > cubieboard2 > and realize that it is not working. We have to build from source= . > > Step 2: Get VirtualBox for OS X from https://www.virtualbox.org > (Downloads > > VirtualBox 4.3.16 for OS X hosts). Run the provided installer. > > Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/serve= r > . > > Save the image ubuntu-14.04.1-server-amd64.iso somewhere where > you can > find it. > > Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). > > I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive > (this > turned out to be extremely tight to build xen-arm-builder, so I > recommend making it at least 9GB to give yourself some more room)= . > > When prompted for an installation CD, locate the ISO file that yo= u > downloaded in Step 3. > > Step 5: Follow the prompts and install Ubuntu. > > Make sure to install sshd when prompted (we want to avoid having > to use > the VirtualBox UI at all costs). > > Step 6: (Optional?) Fix the Wi-Fi in VirtualBox. > > For some reason the network speeds in VirtualBox would start up > ok and > then suddendly slow down to a crawl. After some googling and som= e > blind > guessing I could solve it for my setup. > > Simply go to Settings > Network and change the drop-down menu > 'Attached > to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart > the VM. > Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' > interface. > > Step 7: SSH into the VM from your normal (OS X) terminal. > > Open a terminal and type 'ssh @' where is the > address > from the previous step. Log in. > > Step 8: Install git and clone xen-arm-builder from github. > > sudo apt-get install git > git clone https://github.com/mirage/xen-arm-builder > cd xen-arm-builder > > Step 9: Follow the instructions in the xen-arm-builder README. > > export BOARD=3Dcubieboard2 > make clone > make build > make cubieboard2.img > # Exit the ssh session > exit > # Get the cubieboard2.img file over to the OS X side > scp @:xen-arm-builder/cubieboard2.img . > > # Insert SDcard into your computer and copy the .img file into i= t > > # Find the disk device of the card you inserted, say diskN > sudo diskutil list > # Unmount the disk images > sudo diskutil unmountDisk /dev/diskN > # Copy the image - This automatically remounts the disk > sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k > # Unmount the image and eject > sudo diskutil unmountDisk /dev/diskN > > # Insert SDcard into Cubieboard, connect the Cubieboard power & > network. > > # The cubieboard will obtain an IP address via DHCP and will als= o > # broadcast itself on Bonjour (Zeroconf) under the name > # 'cubieboard2.local.' (note the dot at the end). So you should > be able > # to connect the cubieboard to your local network with an etherne= t > cable > # and then do > > ssh mirage@cubieboard2.local. > > # (password is 'mirage') and voila! you're connected. > > Step 10: Install Mirage. > > # We follow the instructions at > http://openmirage.org/wiki/install, > # except that we can skip the first section, 'Requirements'. > > opam init > eval `opam config env` > opam install mirage > > Step 11: Build Hello, World! example, UNIX version. > > git clone https://github.com/mirage/mirage-skeleton > cd mirage-skeleton > cd console > mirage configure --unix > make depend > make > ./mir-console > > Step 12: Build Hello, World! example, Xen version [FAILED!]. > > mirage configure --xen > > Fails while compiling mirage-xen 1.1.1 with the C compiler cc > complaining about some unrecognized command line options > > cc: error: unrecognized command line option =E2=80=98-m64=E2=80= =99 > cc: error: unrecognized command line option =E2=80=98-mno-red-zo= ne=E2=80=99 > cc: error: unrecognized command line option > =E2=80=98-momit-leaf-frame-pointer=E2=80=99 > cc: error: unrecognized command line option =E2=80=98-mfancy-mat= h-387=E2=80=99 > > The full log is at < > https://gist.github.com/nojb/b7972e42e317160771c5>. > > > > _______________________________________________ > MirageOS-devel mailing listMirageOS-devel@lists.xenproject.orghttp://list= s.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 > > --e89a8f502f88069385050322e79b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can download the pre-compiled version here:=C2=A0http://blobs.openmirage.org/
--Stephen

On Mon, Sep 15, 2014 at 7:57 PM, Jon Ludlam <jjl25@cam.ac.u= k> wrote:
=20 =20 =20
Hi Nicolas,

I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam.

Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minios-arm - = in particular the 'opam pin' commands.

Good luck!

Jon



On 15/09/14 23:23, Nicolas Ojeda Bar wrote:
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to
install Xen/Mirage guided by the following sets of instructions:


TL;DR: The link to the pre-built binaries in [1] is broken, but building from
source I was able to successfully install mirage on the Cubieboard and run the
UNIX version of the Hello, World! unikernel. =C2=A0However, the Xen version did not
work because the opam package mirage-xen 1.1.1 did not compile (some command
line options were not recognized by cc). =C2=A0The ful= l build log is at

It seems that this problem should be quite easy to solve by someone more
knowledgeable than me.

I am also sharing the exact steps I took to set up the Cubieboard in case they
are of use to someone else.

Best wishes,
Nicolas

How to install Xen/Mirage on a Cubieboard 2
-------------------------------------------

This is a record of what I had to do to install Xen on a Cubieboard 2. =C2=A0I am
sending it to the list in case it is of use to someone else.

Before we start, ingredients:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 - MacBook Pro, Early 2011,= OS X 10.9.4, 8GB RAM.
=C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Cubieboard 2.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 See pic here: http://= s28.postimg.org/xdou7ajvx/image.jpg

So, let's get started.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Click on the link that adv= ertises a pre-built binary for the cubieboard2
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and realize that it is not= working. =C2=A0We have to build from source.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 VirtualBox 4.3.16 for OS X= hosts). Run the provided installer.

Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/dow= nload/server.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
=C2=A0 =C2=A0 =C2=A0 =C2=A0 find it.

Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I assigned 2GB RAM (out of= a total of 8GB) and 8GB Hard drive (this
=C2=A0 =C2=A0 =C2=A0 =C2=A0 turned out to be extremely= tight to build xen-arm-builder, so I
=C2=A0 =C2=A0 =C2=A0 =C2=A0 recommend making it at lea= st 9GB to give yourself some more room).
=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 When prompted for an insta= llation CD, locate the ISO file that you
=C2=A0 =C2=A0 =C2=A0 =C2=A0 downloaded in Step 3.

Step 5: Follow the prompts and install Ubuntu.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Make sure to install sshd = when prompted (we want to avoid having to use
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the VirtualBox UI at all c= osts).

Step 6: (Optional?) Fix the Wi-Fi in VirtualBox.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 For some reason the networ= k speeds in VirtualBox would start up ok and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 then suddendly slow down t= o a crawl. =C2=A0After some googling and some blind
=C2=A0 =C2=A0 =C2=A0 =C2=A0 guessing I could solve it = for my setup.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Simply go to Settings >= Network and change the drop-down menu 'Attached
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to:' from 'NAT'= ; to 'en1: Wi-Fi (AirPort)'. Click OK and restart the VM.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Log in and type 'ifcon= fig'. Note the 'inet addr' of the 'eth0' interface.

Step 7: SSH into the VM from your normal (OS X) terminal.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Open a terminal and type &= #39;ssh <user>@<ip>' where <ip> is the address
=C2=A0 =C2=A0 =C2=A0 =C2=A0 from the previous step. Lo= g in.

Step 8: Install git and clone xen-arm-builder from github.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo apt-get install git
=C2=A0 =C2=A0 =C2=A0 =C2=A0 git clone https://github.com/= mirage/xen-arm-builder
=C2=A0 =C2=A0 =C2=A0 =C2=A0 cd xen-arm-builder

Step 9: Follow the instructions in the xen-arm-builder README.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 export BOARD=3Dcubieboard2=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make clone
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make build
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make cubieboard2.img
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Exit the ssh session
=C2=A0 =C2=A0 =C2=A0 =C2=A0 exit
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Get the cubieboard2.img = file over to the OS X side
=C2=A0 =C2=A0 =C2=A0 =C2=A0 scp <user>@<ip>:xen-arm-builder/cubieboard2.img .

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Insert SDcard into your = computer and copy the .img file into it

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Find the disk device of = the card you inserted, say diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil list
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Unmount the disk images<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil unmountDisk = /dev/diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Copy the image - This au= tomatically remounts the disk
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo dd if=3Dcubieboard2.i= mg of=3D/dev/rdiskN bs=3D64k
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Unmount the image and ej= ect
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil unmountDisk = /dev/diskN

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Insert SDcard into Cubie= board, connect the Cubieboard power & network.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # The cubieboard will obta= in an IP address via DHCP and will also
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # broadcast itself on Bonj= our (Zeroconf) under the name
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # 'cubieboard2.local.&= #39; (note the dot at the end). =C2=A0So you should be able
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # to connect the cubieboar= d to your local network with an ethernet cable
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # and then do

=C2=A0 =C2=A0 =C2=A0 =C2=A0 ssh mirage@cubieboard2.local.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # (password is 'mirage= ') and voila! you're connected.

Step 10: Install Mirage.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0# We follow the inst= ructions at http://openmirage.org/wiki/install,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0# except that we can= skip the first section, 'Requirements'.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam init
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0eval `opam config en= v`
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam install mirage<= /div>

Step 11: Build Hello, World! example, UNIX version.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0git clone https://githu= b.com/mirage/mirage-skeleton
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd mirage-skeleton
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd console
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirage configure --u= nix
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make depend
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirage configure --x= en

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Fails while compilin= g mirage-xen 1.1.1 with the C compiler cc
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0complaining about so= me unrecognized command line options

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-m64=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-mno-red-zone=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-mfancy-math-387=E2=80=99

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The full log is at &= lt;https://gist.github.com/nojb/b7972e42e317160771c5>.



_______________________________________________
MirageOS-devel mailing list
Mi=
rageOS-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


--e89a8f502f88069385050322e79b-- --===============7848918559801087028== 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 --===============7848918559801087028==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 23:22:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 23:22: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 1XTfay-000146-JV; Mon, 15 Sep 2014 23:22:08 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTfax-00013x-23 for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 23:22:07 +0000 Received: from [193.109.254.147:5640] by server-16.bemta-14.messagelabs.com id F0/37-16990-E9477145; Mon, 15 Sep 2014 23:22:06 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1410823323!15680684!1 X-Originating-IP: [74.125.82.172] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_50_60,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 702 invoked from network); 15 Sep 2014 23:22:03 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 15 Sep 2014 23:22:03 -0000 Received: by mail-we0-f172.google.com with SMTP id k48so4803713wev.31 for ; Mon, 15 Sep 2014 16:22:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nWjXHiZbHs2AXxxgk0YEb6jWkmwIsHCEtry3EnUobdM=; b=DVYsF+MU4RwrOrH5IopwIdzffPzC3owxUAEDhOtXctbAUA6YbH50JZR119feSMYGsy hnHKDRyTPa8ZJYg0Lg8F0SnVQLxfLkYWRZqTEyFGkGJu/xQsZUNhmvM/IJsJPp+tmrTl 3o9SvYRTB6jaYwz9uDugEN3do1NzQZheIdaOgb3jxf9c/cPBokeAGySuGFHi/8R0ffli zFXcR4/Dl3bii7ZJ+6saJqCo7Aj3uG0atutNLF9cEendthm2xOfSnXItS5ny/WTGbDiJ HnxJ0WcG4d3il61l5Ky11UB6G7p6fO1HRL6HdJeocs4SkeOM2mGNO6BKrqN0btYT4LOj Xa2w== MIME-Version: 1.0 X-Received: by 10.180.36.84 with SMTP id o20mr899866wij.9.1410823323291; Mon, 15 Sep 2014 16:22:03 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Mon, 15 Sep 2014 16:22:03 -0700 (PDT) In-Reply-To: <54176EC5.2070902@cam.ac.uk> References: <54176EC5.2070902@cam.ac.uk> Date: Mon, 15 Sep 2014 20:22:03 -0300 Message-ID: From: Stephen Mack To: Jon Ludlam Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7848918559801087028==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7848918559801087028== Content-Type: multipart/alternative; boundary=e89a8f502f88069385050322e79b --e89a8f502f88069385050322e79b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You can download the pre-compiled version here: http://blobs.openmirage.org= / --Stephen On Mon, Sep 15, 2014 at 7:57 PM, Jon Ludlam wrote: > Hi Nicolas, > > I believe you need more recent versions of mirage, mirage-xen and tcpip > than those that are currently available in opam. > > Take a look at Thomas Leonard's blog post here: > http://openmirage.org/blog/introducing-xen-minios-arm - in particular the > 'opam pin' commands. > > Good luck! > > Jon > > > > On 15/09/14 23:23, Nicolas Ojeda Bar wrote: > > Dear list, > > Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set > out to > install Xen/Mirage guided by the following sets of instructions: > > [1]: https://github.com/mirage/xen-arm-builder > [2]: http://openmirage.org/wiki/install > [3]: http://openmirage.org/wiki/hello-world > > TL;DR: The link to the pre-built binaries in [1] is broken, but building > from > source I was able to successfully install mirage on the Cubieboard and ru= n > the > UNIX version of the Hello, World! unikernel. However, the Xen version di= d > not > work because the opam package mirage-xen 1.1.1 did not compile (some > command > line options were not recognized by cc). The full build log is at > . > > It seems that this problem should be quite easy to solve by someone more > knowledgeable than me. > > I am also sharing the exact steps I took to set up the Cubieboard in > case they > are of use to someone else. > > Best wishes, > Nicolas > > How to install Xen/Mirage on a Cubieboard 2 > ------------------------------------------- > > This is a record of what I had to do to install Xen on a Cubieboard 2. > I am > sending it to the list in case it is of use to someone else. > > Before we start, ingredients: > > - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. > > - Cubieboard 2. > See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg > > So, let's get started. > > Step 1: Go to https://github.com/mirage/xen-arm-builder. > > Click on the link that advertises a pre-built binary for the > cubieboard2 > and realize that it is not working. We have to build from source= . > > Step 2: Get VirtualBox for OS X from https://www.virtualbox.org > (Downloads > > VirtualBox 4.3.16 for OS X hosts). Run the provided installer. > > Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/serve= r > . > > Save the image ubuntu-14.04.1-server-amd64.iso somewhere where > you can > find it. > > Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). > > I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive > (this > turned out to be extremely tight to build xen-arm-builder, so I > recommend making it at least 9GB to give yourself some more room)= . > > When prompted for an installation CD, locate the ISO file that yo= u > downloaded in Step 3. > > Step 5: Follow the prompts and install Ubuntu. > > Make sure to install sshd when prompted (we want to avoid having > to use > the VirtualBox UI at all costs). > > Step 6: (Optional?) Fix the Wi-Fi in VirtualBox. > > For some reason the network speeds in VirtualBox would start up > ok and > then suddendly slow down to a crawl. After some googling and som= e > blind > guessing I could solve it for my setup. > > Simply go to Settings > Network and change the drop-down menu > 'Attached > to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart > the VM. > Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' > interface. > > Step 7: SSH into the VM from your normal (OS X) terminal. > > Open a terminal and type 'ssh @' where is the > address > from the previous step. Log in. > > Step 8: Install git and clone xen-arm-builder from github. > > sudo apt-get install git > git clone https://github.com/mirage/xen-arm-builder > cd xen-arm-builder > > Step 9: Follow the instructions in the xen-arm-builder README. > > export BOARD=3Dcubieboard2 > make clone > make build > make cubieboard2.img > # Exit the ssh session > exit > # Get the cubieboard2.img file over to the OS X side > scp @:xen-arm-builder/cubieboard2.img . > > # Insert SDcard into your computer and copy the .img file into i= t > > # Find the disk device of the card you inserted, say diskN > sudo diskutil list > # Unmount the disk images > sudo diskutil unmountDisk /dev/diskN > # Copy the image - This automatically remounts the disk > sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k > # Unmount the image and eject > sudo diskutil unmountDisk /dev/diskN > > # Insert SDcard into Cubieboard, connect the Cubieboard power & > network. > > # The cubieboard will obtain an IP address via DHCP and will als= o > # broadcast itself on Bonjour (Zeroconf) under the name > # 'cubieboard2.local.' (note the dot at the end). So you should > be able > # to connect the cubieboard to your local network with an etherne= t > cable > # and then do > > ssh mirage@cubieboard2.local. > > # (password is 'mirage') and voila! you're connected. > > Step 10: Install Mirage. > > # We follow the instructions at > http://openmirage.org/wiki/install, > # except that we can skip the first section, 'Requirements'. > > opam init > eval `opam config env` > opam install mirage > > Step 11: Build Hello, World! example, UNIX version. > > git clone https://github.com/mirage/mirage-skeleton > cd mirage-skeleton > cd console > mirage configure --unix > make depend > make > ./mir-console > > Step 12: Build Hello, World! example, Xen version [FAILED!]. > > mirage configure --xen > > Fails while compiling mirage-xen 1.1.1 with the C compiler cc > complaining about some unrecognized command line options > > cc: error: unrecognized command line option =E2=80=98-m64=E2=80= =99 > cc: error: unrecognized command line option =E2=80=98-mno-red-zo= ne=E2=80=99 > cc: error: unrecognized command line option > =E2=80=98-momit-leaf-frame-pointer=E2=80=99 > cc: error: unrecognized command line option =E2=80=98-mfancy-mat= h-387=E2=80=99 > > The full log is at < > https://gist.github.com/nojb/b7972e42e317160771c5>. > > > > _______________________________________________ > MirageOS-devel mailing listMirageOS-devel@lists.xenproject.orghttp://list= s.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 > > --e89a8f502f88069385050322e79b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can download the pre-compiled version here:=C2=A0http://blobs.openmirage.org/
--Stephen

On Mon, Sep 15, 2014 at 7:57 PM, Jon Ludlam <jjl25@cam.ac.u= k> wrote:
=20 =20 =20
Hi Nicolas,

I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam.

Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minios-arm - = in particular the 'opam pin' commands.

Good luck!

Jon



On 15/09/14 23:23, Nicolas Ojeda Bar wrote:
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to
install Xen/Mirage guided by the following sets of instructions:


TL;DR: The link to the pre-built binaries in [1] is broken, but building from
source I was able to successfully install mirage on the Cubieboard and run the
UNIX version of the Hello, World! unikernel. =C2=A0However, the Xen version did not
work because the opam package mirage-xen 1.1.1 did not compile (some command
line options were not recognized by cc). =C2=A0The ful= l build log is at

It seems that this problem should be quite easy to solve by someone more
knowledgeable than me.

I am also sharing the exact steps I took to set up the Cubieboard in case they
are of use to someone else.

Best wishes,
Nicolas

How to install Xen/Mirage on a Cubieboard 2
-------------------------------------------

This is a record of what I had to do to install Xen on a Cubieboard 2. =C2=A0I am
sending it to the list in case it is of use to someone else.

Before we start, ingredients:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 - MacBook Pro, Early 2011,= OS X 10.9.4, 8GB RAM.
=C2=A0 =C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Cubieboard 2.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 See pic here: http://= s28.postimg.org/xdou7ajvx/image.jpg

So, let's get started.


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Click on the link that adv= ertises a pre-built binary for the cubieboard2
=C2=A0 =C2=A0 =C2=A0 =C2=A0 and realize that it is not= working. =C2=A0We have to build from source.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 VirtualBox 4.3.16 for OS X= hosts). Run the provided installer.

Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/dow= nload/server.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
=C2=A0 =C2=A0 =C2=A0 =C2=A0 find it.

Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

=C2=A0 =C2=A0 =C2=A0 =C2=A0 I assigned 2GB RAM (out of= a total of 8GB) and 8GB Hard drive (this
=C2=A0 =C2=A0 =C2=A0 =C2=A0 turned out to be extremely= tight to build xen-arm-builder, so I
=C2=A0 =C2=A0 =C2=A0 =C2=A0 recommend making it at lea= st 9GB to give yourself some more room).
=C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 When prompted for an insta= llation CD, locate the ISO file that you
=C2=A0 =C2=A0 =C2=A0 =C2=A0 downloaded in Step 3.

Step 5: Follow the prompts and install Ubuntu.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Make sure to install sshd = when prompted (we want to avoid having to use
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the VirtualBox UI at all c= osts).

Step 6: (Optional?) Fix the Wi-Fi in VirtualBox.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 For some reason the networ= k speeds in VirtualBox would start up ok and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 then suddendly slow down t= o a crawl. =C2=A0After some googling and some blind
=C2=A0 =C2=A0 =C2=A0 =C2=A0 guessing I could solve it = for my setup.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Simply go to Settings >= Network and change the drop-down menu 'Attached
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to:' from 'NAT'= ; to 'en1: Wi-Fi (AirPort)'. Click OK and restart the VM.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Log in and type 'ifcon= fig'. Note the 'inet addr' of the 'eth0' interface.

Step 7: SSH into the VM from your normal (OS X) terminal.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Open a terminal and type &= #39;ssh <user>@<ip>' where <ip> is the address
=C2=A0 =C2=A0 =C2=A0 =C2=A0 from the previous step. Lo= g in.

Step 8: Install git and clone xen-arm-builder from github.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo apt-get install git
=C2=A0 =C2=A0 =C2=A0 =C2=A0 git clone https://github.com/= mirage/xen-arm-builder
=C2=A0 =C2=A0 =C2=A0 =C2=A0 cd xen-arm-builder

Step 9: Follow the instructions in the xen-arm-builder README.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 export BOARD=3Dcubieboard2=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make clone
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make build
=C2=A0 =C2=A0 =C2=A0 =C2=A0 make cubieboard2.img
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Exit the ssh session
=C2=A0 =C2=A0 =C2=A0 =C2=A0 exit
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Get the cubieboard2.img = file over to the OS X side
=C2=A0 =C2=A0 =C2=A0 =C2=A0 scp <user>@<ip>:xen-arm-builder/cubieboard2.img .

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Insert SDcard into your = computer and copy the .img file into it

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Find the disk device of = the card you inserted, say diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil list
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Unmount the disk images<= /div>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil unmountDisk = /dev/diskN
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Copy the image - This au= tomatically remounts the disk
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo dd if=3Dcubieboard2.i= mg of=3D/dev/rdiskN bs=3D64k
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Unmount the image and ej= ect
=C2=A0 =C2=A0 =C2=A0 =C2=A0 sudo diskutil unmountDisk = /dev/diskN

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # Insert SDcard into Cubie= board, connect the Cubieboard power & network.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # The cubieboard will obta= in an IP address via DHCP and will also
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # broadcast itself on Bonj= our (Zeroconf) under the name
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # 'cubieboard2.local.&= #39; (note the dot at the end). =C2=A0So you should be able
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # to connect the cubieboar= d to your local network with an ethernet cable
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # and then do

=C2=A0 =C2=A0 =C2=A0 =C2=A0 ssh mirage@cubieboard2.local.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 # (password is 'mirage= ') and voila! you're connected.

Step 10: Install Mirage.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0# We follow the inst= ructions at http://openmirage.org/wiki/install,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0# except that we can= skip the first section, 'Requirements'.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam init
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0eval `opam config en= v`
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0opam install mirage<= /div>

Step 11: Build Hello, World! example, UNIX version.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0git clone https://githu= b.com/mirage/mirage-skeleton
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd mirage-skeleton
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cd console
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirage configure --u= nix
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make depend
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0make
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0mirage configure --x= en

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Fails while compilin= g mirage-xen 1.1.1 with the C compiler cc
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0complaining about so= me unrecognized command line options

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-m64=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-mno-red-zone=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cc: error: unrecogni= zed command line option =E2=80=98-mfancy-math-387=E2=80=99

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The full log is at &= lt;https://gist.github.com/nojb/b7972e42e317160771c5>.



_______________________________________________
MirageOS-devel mailing list
Mi=
rageOS-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


--e89a8f502f88069385050322e79b-- --===============7848918559801087028== 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 --===============7848918559801087028==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 23:27:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 23:27: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 1XTffj-000169-3m; Mon, 15 Sep 2014 23:27:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTffh-000164-OB for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 23:27:02 +0000 Received: from [193.109.254.147:39362] by server-9.bemta-14.messagelabs.com id 78/51-31535-5C577145; Mon, 15 Sep 2014 23:27:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1410823618!15719829!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.0 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2318 invoked from network); 15 Sep 2014 23:26:58 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 23:26:58 -0000 Received: from [192.168.1.100] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id d94bbb5d; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 16 Sep 2014 00:27:39 +0100 (BST) Mime-Version: 1.0 (1.0) From: Anil Madhavapeddy Message-Id: <446FBF1C-1762-499F-9CB4-8BF83C6E86AF@recoil.org> Date: Tue, 16 Sep 2014 00:25:32 +0100 To: Jon Ludlam X-Mailer: iPhone Mail (11D257) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4894966074614386529==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4894966074614386529== Content-Type: multipart/alternative; boundary=Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F Content-Transfer-Encoding: 7bit --Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The very latest pins can be summoned by one command: opam remote add mirage git://github.com/mirage/mirage-dev That will pull in all the arm repos. Need to update the various pin instruc= tions on the website. > On 15 Sep 2014, at 23:57, Jon Ludlam wrote: >=20 > Hi Nicolas, >=20 > I believe you need more recent versions of mirage, mirage-xen and tcpip th= an those that are currently available in opam.=20 >=20 > Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog= /introducing-xen-minios-arm - in particular the 'opam pin' commands.=20 >=20 > Good luck! >=20 > Jon >=20 >=20 >> On 15/09/14 23:23, Nicolas Ojeda Bar wrote: >> Dear list, >>=20 >> Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set o= ut to >> install Xen/Mirage guided by the following sets of instructions: >>=20 >> [1]: https://github.com/mirage/xen-arm-builder >> [2]: http://openmirage.org/wiki/install >> [3]: http://openmirage.org/wiki/hello-world >>=20 >> TL;DR: The link to the pre-built binaries in [1] is broken, but building f= rom >> source I was able to successfully install mirage on the Cubieboard and ru= n the >> UNIX version of the Hello, World! unikernel. However, the Xen version di= d not >> work because the opam package mirage-xen 1.1.1 did not compile (some comm= and >> line options were not recognized by cc). The full build log is at >> . >>=20 >> It seems that this problem should be quite easy to solve by someone more >> knowledgeable than me. >>=20 >> I am also sharing the exact steps I took to set up the Cubieboard in case= they >> are of use to someone else. >>=20 >> Best wishes, >> Nicolas >>=20 >> How to install Xen/Mirage on a Cubieboard 2 >> ------------------------------------------- >>=20 >> This is a record of what I had to do to install Xen on a Cubieboard 2. I= am >> sending it to the list in case it is of use to someone else. >>=20 >> Before we start, ingredients: >>=20 >> - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. >> =20 >> - Cubieboard 2. >> See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg >>=20 >> So, let's get started. >>=20 >> Step 1: Go to https://github.com/mirage/xen-arm-builder. >>=20 >> Click on the link that advertises a pre-built binary for the cubi= eboard2 >> and realize that it is not working. We have to build from source= . >>=20 >> Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Download= s > >> VirtualBox 4.3.16 for OS X hosts). Run the provided installer. >>=20 >> Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/server= . >>=20 >> Save the image ubuntu-14.04.1-server-amd64.iso somewhere where yo= u can >> find it. >>=20 >> Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). >>=20 >> I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive (th= is >> turned out to be extremely tight to build xen-arm-builder, so I >> recommend making it at least 9GB to give yourself some more room)= . >> =20 >> When prompted for an installation CD, locate the ISO file that yo= u >> downloaded in Step 3. >>=20 >> Step 5: Follow the prompts and install Ubuntu. >>=20 >> Make sure to install sshd when prompted (we want to avoid having t= o use >> the VirtualBox UI at all costs). >>=20 >> Step 6: (Optional?) Fix the Wi-Fi in VirtualBox. >>=20 >> For some reason the network speeds in VirtualBox would start up o= k and >> then suddendly slow down to a crawl. After some googling and som= e blind >> guessing I could solve it for my setup. >>=20 >> Simply go to Settings > Network and change the drop-down menu 'At= tached >> to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart t= he VM. >> Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' in= terface. >>=20 >> Step 7: SSH into the VM from your normal (OS X) terminal. >>=20 >> Open a terminal and type 'ssh @' where is the addr= ess >> from the previous step. Log in. >>=20 >> Step 8: Install git and clone xen-arm-builder from github. >>=20 >> sudo apt-get install git >> git clone https://github.com/mirage/xen-arm-builder >> cd xen-arm-builder >>=20 >> Step 9: Follow the instructions in the xen-arm-builder README. >>=20 >> export BOARD=3Dcubieboard2 >> make clone >> make build >> make cubieboard2.img >> # Exit the ssh session >> exit >> # Get the cubieboard2.img file over to the OS X side >> scp @:xen-arm-builder/cubieboard2.img . >>=20 >> # Insert SDcard into your computer and copy the .img file into it= >>=20 >> # Find the disk device of the card you inserted, say diskN >> sudo diskutil list >> # Unmount the disk images >> sudo diskutil unmountDisk /dev/diskN >> # Copy the image - This automatically remounts the disk >> sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k >> # Unmount the image and eject >> sudo diskutil unmountDisk /dev/diskN >>=20 >> # Insert SDcard into Cubieboard, connect the Cubieboard power & n= etwork. >>=20 >> # The cubieboard will obtain an IP address via DHCP and will also= >> # broadcast itself on Bonjour (Zeroconf) under the name >> # 'cubieboard2.local.' (note the dot at the end). So you should b= e able >> # to connect the cubieboard to your local network with an etherne= t cable >> # and then do >>=20 >> ssh mirage@cubieboard2.local. >>=20 >> # (password is 'mirage') and voila! you're connected. >>=20 >> Step 10: Install Mirage. >>=20 >> # We follow the instructions at http://openmirage.org/wiki/insta= ll, >> # except that we can skip the first section, 'Requirements'. >>=20 >> opam init >> eval `opam config env` >> opam install mirage >>=20 >> Step 11: Build Hello, World! example, UNIX version. >>=20 >> git clone https://github.com/mirage/mirage-skeleton >> cd mirage-skeleton >> cd console >> mirage configure --unix >> make depend >> make >> ./mir-console >>=20 >> Step 12: Build Hello, World! example, Xen version [FAILED!]. >>=20 >> mirage configure --xen >>=20 >> Fails while compiling mirage-xen 1.1.1 with the C compiler cc >> complaining about some unrecognized command line options >>=20 >> cc: error: unrecognized command line option =E2=80=98-m64=E2=80=99= >> cc: error: unrecognized command line option =E2=80=98-mno-red-zo= ne=E2=80=99 >> cc: error: unrecognized command line option =E2=80=98-momit-leaf= -frame-pointer=E2=80=99 >> cc: error: unrecognized command line option =E2=80=98-mfancy-mat= h-387=E2=80=99 >>=20 >> The full log is at . >>=20 >>=20 >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
The very latest pins can be summoned b= y one command:

opam remote add mirage git://github.= com/mirage/mirage-dev

That will pull in all the arm= repos.  Need to update the various pin instructions on the website.

On 15 Sep 2014, at 23:57, Jon Ludlam <jjl25@cam.ac.uk> wrote:

=20 =20 =20
Hi Nicolas,

I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam.

Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minio= s-arm - in particular the 'opam pin' commands.

Good luck!

Jon


On 15/09/14 23:23, Nicolas Ojeda Bar wrote:
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to
install Xen/Mirage guided by the following sets of instructions:

[1]: https://github.com/mirage/xen-arm-builder

TL;DR: The link to the pre-built binaries in [1] is broken, but building from
source I was able to successfully install mirage on the Cubieboard and run the
UNIX version of the Hello, World! unikernel.  However, the Xen version did not
work because the opam package mirage-xen 1.1.1 did not compile (some command
line options were not recognized by cc).  The full= build log is at

It seems that this problem should be quite easy to solve by someone more
knowledgeable than me.

I am also sharing the exact steps I took to set up the Cubieboard in case they
are of use to someone else.

Best wishes,
Nicolas

How to install Xen/Mirage on a Cubieboard 2
-------------------------------------------

This is a record of what I had to do to install Xen on a Cubieboard 2.  I am
sending it to the list in case it is of use to someone else.

Before we start, ingredients:

        - MacBook Pro, Early 2011, O= S X 10.9.4, 8GB RAM.
   
        - Cubieboard 2.

So, let's get started.


        Click on the link that adve= rtises a pre-built binary for the cubieboard2
        and realize that it is not w= orking.  We have to build from source.

Step 2: Get VirtualBox for OS X from https://www.virtualbox.org= (Downloads >
        VirtualBox 4.3.16 for OS X h= osts). Run the provided installer.

Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.co= m/download/server.

        Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
        find it.

Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

        I assigned 2GB RAM (out of a= total of 8GB) and 8GB Hard drive (this
        turned out to be extremely t= ight to build xen-arm-builder, so I
        recommend making it at leas= t 9GB to give yourself some more room).
        
        When prompted for an instal= lation CD, locate the ISO file that you
        downloaded in Step 3.
=

Step 5: Follow the prompts and install Ubuntu.

        Make sure to install sshd w= hen prompted (we want to avoid having to use
        the VirtualBox UI at all co= sts).

Step 6: (Optional?) Fix the Wi-Fi in VirtualBox.

        For some reason the network= speeds in VirtualBox would start up ok and
        then suddendly slow down to= a crawl.  After some googling and some blind
        guessing I could solve it f= or my setup.

        Simply go to Settings > N= etwork and change the drop-down menu 'Attached
        to:' from 'NAT' to 'en1: Wi= -Fi (AirPort)'. Click OK and restart the VM.
        Log in and type 'ifconfig'.= Note the 'inet addr' of the 'eth0' interface.

Step 7: SSH into the VM from your normal (OS X) terminal.

        Open a terminal and type 's= sh <user>@<ip>' where <ip> is the address
        from the previous step. Log= in.

Step 8: Install git and clone xen-arm-builder from github.

        sudo apt-get install git
        cd xen-arm-builder

Step 9: Follow the instructions in the xen-arm-builder README.

        export BOARD=3Dcubieboard2<= /div>
        make clone
        make build
        make cubieboard2.img
        # Exit the ssh session
        exit
        # Get the cubieboard2.img f= ile over to the OS X side
        scp <user>@<ip>:xen-arm-builder/cubieboard2.img .

        # Insert SDcard into your c= omputer and copy the .img file into it

        # Find the disk device of t= he card you inserted, say diskN
        sudo diskutil list
        # Unmount the disk images
        sudo diskutil unmountDisk /= dev/diskN
        # Copy the image - This aut= omatically remounts the disk
        sudo dd if=3Dcubieboard2.im= g of=3D/dev/rdiskN bs=3D64k
        # Unmount the image and eje= ct
        sudo diskutil unmountDisk /= dev/diskN

        # Insert SDcard into Cubieb= oard, connect the Cubieboard power & network.

        # The cubieboard will obtai= n an IP address via DHCP and will also
        # broadcast itself on Bonjo= ur (Zeroconf) under the name
        # 'cubieboard2.local.' (not= e the dot at the end).  So you should be able
        # to connect the cubieboard= to your local network with an ethernet cable
        # and then do


        # (password is 'mirage') an= d voila! you're connected.

Step 10: Install Mirage.

         # We follow the instr= uctions at http://openmirage.org/wiki/install,
         # except that we can s= kip the first section, 'Requirements'.

         opam init
         eval `opam config env= `
         opam install mirage

Step 11: Build Hello, World! example, UNIX version.

         cd mirage-skeleton
         cd console
         mirage configure --un= ix
         make depend
         make
         ./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].

         mirage configure --xe= n

         Fails while compiling= mirage-xen 1.1.1 with the C compiler cc
         complaining about som= e unrecognized command line options

         cc: error: unrecogniz= ed command line option =E2=80=98-m64=E2=80=99
         cc: error: unrecogniz= ed command line option =E2=80=98-mno-red-zone=E2=80=99
         cc: error: unrecogniz= ed command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99
         cc: error: unrecogniz= ed command line option =E2=80=98-mfancy-math-387=E2=80=99

         The full log is at &l= t;https://gist.github.com/nojb/b7972e42e317160771c5>. 



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

=20
____________________= ___________________________
MirageOS-devel mailing list
MirageOS-= devel@lists.xenproject.org
http://lists.xenproject.o= rg/cgi-bin/mailman/listinfo/mirageos-devel
= = --Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F-- --===============4894966074614386529== 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 --===============4894966074614386529==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 15 23:27:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 15 Sep 2014 23:27: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 1XTffj-000169-3m; Mon, 15 Sep 2014 23:27:03 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTffh-000164-OB for mirageos-devel@lists.xenproject.org; Mon, 15 Sep 2014 23:27:02 +0000 Received: from [193.109.254.147:39362] by server-9.bemta-14.messagelabs.com id 78/51-31535-5C577145; Mon, 15 Sep 2014 23:27:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1410823618!15719829!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.0 required=7.0 tests=HTML_60_70,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,MIME_QP_LONG_LINE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2318 invoked from network); 15 Sep 2014 23:26:58 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-2.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 15 Sep 2014 23:26:58 -0000 Received: from [192.168.1.100] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id d94bbb5d; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 16 Sep 2014 00:27:39 +0100 (BST) Mime-Version: 1.0 (1.0) From: Anil Madhavapeddy Message-Id: <446FBF1C-1762-499F-9CB4-8BF83C6E86AF@recoil.org> Date: Tue, 16 Sep 2014 00:25:32 +0100 To: Jon Ludlam X-Mailer: iPhone Mail (11D257) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============4894966074614386529==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4894966074614386529== Content-Type: multipart/alternative; boundary=Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F Content-Transfer-Encoding: 7bit --Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The very latest pins can be summoned by one command: opam remote add mirage git://github.com/mirage/mirage-dev That will pull in all the arm repos. Need to update the various pin instruc= tions on the website. > On 15 Sep 2014, at 23:57, Jon Ludlam wrote: >=20 > Hi Nicolas, >=20 > I believe you need more recent versions of mirage, mirage-xen and tcpip th= an those that are currently available in opam.=20 >=20 > Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog= /introducing-xen-minios-arm - in particular the 'opam pin' commands.=20 >=20 > Good luck! >=20 > Jon >=20 >=20 >> On 15/09/14 23:23, Nicolas Ojeda Bar wrote: >> Dear list, >>=20 >> Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set o= ut to >> install Xen/Mirage guided by the following sets of instructions: >>=20 >> [1]: https://github.com/mirage/xen-arm-builder >> [2]: http://openmirage.org/wiki/install >> [3]: http://openmirage.org/wiki/hello-world >>=20 >> TL;DR: The link to the pre-built binaries in [1] is broken, but building f= rom >> source I was able to successfully install mirage on the Cubieboard and ru= n the >> UNIX version of the Hello, World! unikernel. However, the Xen version di= d not >> work because the opam package mirage-xen 1.1.1 did not compile (some comm= and >> line options were not recognized by cc). The full build log is at >> . >>=20 >> It seems that this problem should be quite easy to solve by someone more >> knowledgeable than me. >>=20 >> I am also sharing the exact steps I took to set up the Cubieboard in case= they >> are of use to someone else. >>=20 >> Best wishes, >> Nicolas >>=20 >> How to install Xen/Mirage on a Cubieboard 2 >> ------------------------------------------- >>=20 >> This is a record of what I had to do to install Xen on a Cubieboard 2. I= am >> sending it to the list in case it is of use to someone else. >>=20 >> Before we start, ingredients: >>=20 >> - MacBook Pro, Early 2011, OS X 10.9.4, 8GB RAM. >> =20 >> - Cubieboard 2. >> See pic here: http://s28.postimg.org/xdou7ajvx/image.jpg >>=20 >> So, let's get started. >>=20 >> Step 1: Go to https://github.com/mirage/xen-arm-builder. >>=20 >> Click on the link that advertises a pre-built binary for the cubi= eboard2 >> and realize that it is not working. We have to build from source= . >>=20 >> Step 2: Get VirtualBox for OS X from https://www.virtualbox.org (Download= s > >> VirtualBox 4.3.16 for OS X hosts). Run the provided installer. >>=20 >> Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.com/download/server= . >>=20 >> Save the image ubuntu-14.04.1-server-amd64.iso somewhere where yo= u can >> find it. >>=20 >> Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit). >>=20 >> I assigned 2GB RAM (out of a total of 8GB) and 8GB Hard drive (th= is >> turned out to be extremely tight to build xen-arm-builder, so I >> recommend making it at least 9GB to give yourself some more room)= . >> =20 >> When prompted for an installation CD, locate the ISO file that yo= u >> downloaded in Step 3. >>=20 >> Step 5: Follow the prompts and install Ubuntu. >>=20 >> Make sure to install sshd when prompted (we want to avoid having t= o use >> the VirtualBox UI at all costs). >>=20 >> Step 6: (Optional?) Fix the Wi-Fi in VirtualBox. >>=20 >> For some reason the network speeds in VirtualBox would start up o= k and >> then suddendly slow down to a crawl. After some googling and som= e blind >> guessing I could solve it for my setup. >>=20 >> Simply go to Settings > Network and change the drop-down menu 'At= tached >> to:' from 'NAT' to 'en1: Wi-Fi (AirPort)'. Click OK and restart t= he VM. >> Log in and type 'ifconfig'. Note the 'inet addr' of the 'eth0' in= terface. >>=20 >> Step 7: SSH into the VM from your normal (OS X) terminal. >>=20 >> Open a terminal and type 'ssh @' where is the addr= ess >> from the previous step. Log in. >>=20 >> Step 8: Install git and clone xen-arm-builder from github. >>=20 >> sudo apt-get install git >> git clone https://github.com/mirage/xen-arm-builder >> cd xen-arm-builder >>=20 >> Step 9: Follow the instructions in the xen-arm-builder README. >>=20 >> export BOARD=3Dcubieboard2 >> make clone >> make build >> make cubieboard2.img >> # Exit the ssh session >> exit >> # Get the cubieboard2.img file over to the OS X side >> scp @:xen-arm-builder/cubieboard2.img . >>=20 >> # Insert SDcard into your computer and copy the .img file into it= >>=20 >> # Find the disk device of the card you inserted, say diskN >> sudo diskutil list >> # Unmount the disk images >> sudo diskutil unmountDisk /dev/diskN >> # Copy the image - This automatically remounts the disk >> sudo dd if=3Dcubieboard2.img of=3D/dev/rdiskN bs=3D64k >> # Unmount the image and eject >> sudo diskutil unmountDisk /dev/diskN >>=20 >> # Insert SDcard into Cubieboard, connect the Cubieboard power & n= etwork. >>=20 >> # The cubieboard will obtain an IP address via DHCP and will also= >> # broadcast itself on Bonjour (Zeroconf) under the name >> # 'cubieboard2.local.' (note the dot at the end). So you should b= e able >> # to connect the cubieboard to your local network with an etherne= t cable >> # and then do >>=20 >> ssh mirage@cubieboard2.local. >>=20 >> # (password is 'mirage') and voila! you're connected. >>=20 >> Step 10: Install Mirage. >>=20 >> # We follow the instructions at http://openmirage.org/wiki/insta= ll, >> # except that we can skip the first section, 'Requirements'. >>=20 >> opam init >> eval `opam config env` >> opam install mirage >>=20 >> Step 11: Build Hello, World! example, UNIX version. >>=20 >> git clone https://github.com/mirage/mirage-skeleton >> cd mirage-skeleton >> cd console >> mirage configure --unix >> make depend >> make >> ./mir-console >>=20 >> Step 12: Build Hello, World! example, Xen version [FAILED!]. >>=20 >> mirage configure --xen >>=20 >> Fails while compiling mirage-xen 1.1.1 with the C compiler cc >> complaining about some unrecognized command line options >>=20 >> cc: error: unrecognized command line option =E2=80=98-m64=E2=80=99= >> cc: error: unrecognized command line option =E2=80=98-mno-red-zo= ne=E2=80=99 >> cc: error: unrecognized command line option =E2=80=98-momit-leaf= -frame-pointer=E2=80=99 >> cc: error: unrecognized command line option =E2=80=98-mfancy-mat= h-387=E2=80=99 >>=20 >> The full log is at . >>=20 >>=20 >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
The very latest pins can be summoned b= y one command:

opam remote add mirage git://github.= com/mirage/mirage-dev

That will pull in all the arm= repos.  Need to update the various pin instructions on the website.

On 15 Sep 2014, at 23:57, Jon Ludlam <jjl25@cam.ac.uk> wrote:

=20 =20 =20
Hi Nicolas,

I believe you need more recent versions of mirage, mirage-xen and tcpip than those that are currently available in opam.

Take a look at Thomas Leonard's blog post here: http://openmirage.org/blog/introducing-xen-minio= s-arm - in particular the 'opam pin' commands.

Good luck!

Jon


On 15/09/14 23:23, Nicolas Ojeda Bar wrote:
Dear list,

Recently I came into possession of a Cubieboard 2 (Thanks Anil!) and set out to
install Xen/Mirage guided by the following sets of instructions:

[1]: https://github.com/mirage/xen-arm-builder

TL;DR: The link to the pre-built binaries in [1] is broken, but building from
source I was able to successfully install mirage on the Cubieboard and run the
UNIX version of the Hello, World! unikernel.  However, the Xen version did not
work because the opam package mirage-xen 1.1.1 did not compile (some command
line options were not recognized by cc).  The full= build log is at

It seems that this problem should be quite easy to solve by someone more
knowledgeable than me.

I am also sharing the exact steps I took to set up the Cubieboard in case they
are of use to someone else.

Best wishes,
Nicolas

How to install Xen/Mirage on a Cubieboard 2
-------------------------------------------

This is a record of what I had to do to install Xen on a Cubieboard 2.  I am
sending it to the list in case it is of use to someone else.

Before we start, ingredients:

        - MacBook Pro, Early 2011, O= S X 10.9.4, 8GB RAM.
   
        - Cubieboard 2.

So, let's get started.


        Click on the link that adve= rtises a pre-built binary for the cubieboard2
        and realize that it is not w= orking.  We have to build from source.

Step 2: Get VirtualBox for OS X from https://www.virtualbox.org= (Downloads >
        VirtualBox 4.3.16 for OS X h= osts). Run the provided installer.

Step 3: Get Ubuntu Server 14.04.1 LTS from www.ubuntu.co= m/download/server.

        Save the image ubuntu-14.04.1-server-amd64.iso somewhere where you can
        find it.

Step 4: In VirtualBox, create a new vm (OS Type: Ubuntu 64-bit).

        I assigned 2GB RAM (out of a= total of 8GB) and 8GB Hard drive (this
        turned out to be extremely t= ight to build xen-arm-builder, so I
        recommend making it at leas= t 9GB to give yourself some more room).
        
        When prompted for an instal= lation CD, locate the ISO file that you
        downloaded in Step 3.
=

Step 5: Follow the prompts and install Ubuntu.

        Make sure to install sshd w= hen prompted (we want to avoid having to use
        the VirtualBox UI at all co= sts).

Step 6: (Optional?) Fix the Wi-Fi in VirtualBox.

        For some reason the network= speeds in VirtualBox would start up ok and
        then suddendly slow down to= a crawl.  After some googling and some blind
        guessing I could solve it f= or my setup.

        Simply go to Settings > N= etwork and change the drop-down menu 'Attached
        to:' from 'NAT' to 'en1: Wi= -Fi (AirPort)'. Click OK and restart the VM.
        Log in and type 'ifconfig'.= Note the 'inet addr' of the 'eth0' interface.

Step 7: SSH into the VM from your normal (OS X) terminal.

        Open a terminal and type 's= sh <user>@<ip>' where <ip> is the address
        from the previous step. Log= in.

Step 8: Install git and clone xen-arm-builder from github.

        sudo apt-get install git
        cd xen-arm-builder

Step 9: Follow the instructions in the xen-arm-builder README.

        export BOARD=3Dcubieboard2<= /div>
        make clone
        make build
        make cubieboard2.img
        # Exit the ssh session
        exit
        # Get the cubieboard2.img f= ile over to the OS X side
        scp <user>@<ip>:xen-arm-builder/cubieboard2.img .

        # Insert SDcard into your c= omputer and copy the .img file into it

        # Find the disk device of t= he card you inserted, say diskN
        sudo diskutil list
        # Unmount the disk images
        sudo diskutil unmountDisk /= dev/diskN
        # Copy the image - This aut= omatically remounts the disk
        sudo dd if=3Dcubieboard2.im= g of=3D/dev/rdiskN bs=3D64k
        # Unmount the image and eje= ct
        sudo diskutil unmountDisk /= dev/diskN

        # Insert SDcard into Cubieb= oard, connect the Cubieboard power & network.

        # The cubieboard will obtai= n an IP address via DHCP and will also
        # broadcast itself on Bonjo= ur (Zeroconf) under the name
        # 'cubieboard2.local.' (not= e the dot at the end).  So you should be able
        # to connect the cubieboard= to your local network with an ethernet cable
        # and then do


        # (password is 'mirage') an= d voila! you're connected.

Step 10: Install Mirage.

         # We follow the instr= uctions at http://openmirage.org/wiki/install,
         # except that we can s= kip the first section, 'Requirements'.

         opam init
         eval `opam config env= `
         opam install mirage

Step 11: Build Hello, World! example, UNIX version.

         cd mirage-skeleton
         cd console
         mirage configure --un= ix
         make depend
         make
         ./mir-console

Step 12: Build Hello, World! example, Xen version [FAILED!].

         mirage configure --xe= n

         Fails while compiling= mirage-xen 1.1.1 with the C compiler cc
         complaining about som= e unrecognized command line options

         cc: error: unrecogniz= ed command line option =E2=80=98-m64=E2=80=99
         cc: error: unrecogniz= ed command line option =E2=80=98-mno-red-zone=E2=80=99
         cc: error: unrecogniz= ed command line option =E2=80=98-momit-leaf-frame-pointer=E2=80=99
         cc: error: unrecogniz= ed command line option =E2=80=98-mfancy-math-387=E2=80=99

         The full log is at &l= t;https://gist.github.com/nojb/b7972e42e317160771c5>. 



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

=20
____________________= ___________________________
MirageOS-devel mailing list
MirageOS-= devel@lists.xenproject.org
http://lists.xenproject.o= rg/cgi-bin/mailman/listinfo/mirageos-devel
= = --Apple-Mail-079A9C0F-0F53-403F-A21A-8E4566D9D97F-- --===============4894966074614386529== 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 --===============4894966074614386529==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 09:03:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 09:03: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 1XTofc-0003hY-VG; Tue, 16 Sep 2014 09:03:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTofb-0003hR-VT for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 09:03:32 +0000 Received: from [85.158.139.211:26937] by server-11.bemta-5.messagelabs.com id F7/55-11011-3ECF7145; Tue, 16 Sep 2014 09:03:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1410858196!7153721!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_23, RCVD_ILLEGAL_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7726 invoked from network); 16 Sep 2014 09:03:16 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2014 09:03:16 -0000 Received: from [10.0.0.110] (host81-149-102-120.in-addr.btopenworld.com [81.149.102.120]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 5181e8ea; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 16 Sep 2014 10:03:59 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 16 Sep 2014 10:03:14 +0100 Message-Id: <3D6902D1-510C-4691-B497-B24DA5C9A6D9@recoil.org> References: To: Nicolas Ojeda Bar X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5701256038450775756==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5701256038450775756== Content-Type: multipart/alternative; boundary="Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073" --Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 15 Sep 2014, at 23:23, Nicolas Ojeda Bar = wrote: >=20 > TL;DR: The link to the pre-built binaries in [1] is broken, but = building from > source I was able to successfully install mirage on the Cubieboard and = run the > UNIX version of the Hello, World! unikernel. However, the Xen version = did not > work because the opam package mirage-xen 1.1.1 did not compile (some = command > line options were not recognized by cc). The full build log is at > . >=20 > It seems that this problem should be quite easy to solve by someone = more > knowledgeable than me. I've fixed the links to the prebuilt binaries in the README; you can = grab the latest from http://blobs.openmirage.org/ now (rebuilt daily). To reiterate the previous mail, you need this opam remote to grab the = ARM capable libraries: opam remote add mirage-dev git://github.com/mirage/mirage-dev (releases on their way just as soon as vchan is integrated, and some = load testing complete on cohttp). cheers, Anil= --Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 15 = Sep 2014, at 23:23, Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk> = wrote:

TL;DR: The link to the pre-built = binaries in [1] is broken, but building from
source I was able = to successfully install mirage on the Cubieboard and run = the
UNIX version of the Hello, World! unikernel. =  However, the Xen version did not
work because the opam = package mirage-xen 1.1.1 did not compile (some command
line = options were not recognized by cc).  The full build log is = at

It = seems that this problem should be quite easy to solve by someone = more
knowledgeable than = me.

I've fixed the links to = the prebuilt binaries in the README; you can grab the latest = from
http://blobs.openmirage.org/ = now (rebuilt daily).

To reiterate the previous = mail, you need this opam remote to grab the ARM
capable = libraries:

opam remote add mirage-dev git://github.com/mirage/mirage= -dev

(releases on their way just as soon as = vchan is integrated, and some load testing
complete on = cohttp).

cheers,
Anil
= --Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073-- --===============5701256038450775756== 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 --===============5701256038450775756==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 09:03:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 09:03: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 1XTofc-0003hY-VG; Tue, 16 Sep 2014 09:03:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTofb-0003hR-VT for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 09:03:32 +0000 Received: from [85.158.139.211:26937] by server-11.bemta-5.messagelabs.com id F7/55-11011-3ECF7145; Tue, 16 Sep 2014 09:03:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1410858196!7153721!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR, ML_RADAR_SPEW_LINKS_23, RCVD_ILLEGAL_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7726 invoked from network); 16 Sep 2014 09:03:16 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2014 09:03:16 -0000 Received: from [10.0.0.110] (host81-149-102-120.in-addr.btopenworld.com [81.149.102.120]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 5181e8ea; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Tue, 16 Sep 2014 10:03:59 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 16 Sep 2014 10:03:14 +0100 Message-Id: <3D6902D1-510C-4691-B497-B24DA5C9A6D9@recoil.org> References: To: Nicolas Ojeda Bar X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Xen/Mirage on a Cubieboard 2 [REPORT] X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5701256038450775756==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5701256038450775756== Content-Type: multipart/alternative; boundary="Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073" --Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 15 Sep 2014, at 23:23, Nicolas Ojeda Bar = wrote: >=20 > TL;DR: The link to the pre-built binaries in [1] is broken, but = building from > source I was able to successfully install mirage on the Cubieboard and = run the > UNIX version of the Hello, World! unikernel. However, the Xen version = did not > work because the opam package mirage-xen 1.1.1 did not compile (some = command > line options were not recognized by cc). The full build log is at > . >=20 > It seems that this problem should be quite easy to solve by someone = more > knowledgeable than me. I've fixed the links to the prebuilt binaries in the README; you can = grab the latest from http://blobs.openmirage.org/ now (rebuilt daily). To reiterate the previous mail, you need this opam remote to grab the = ARM capable libraries: opam remote add mirage-dev git://github.com/mirage/mirage-dev (releases on their way just as soon as vchan is integrated, and some = load testing complete on cohttp). cheers, Anil= --Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 15 = Sep 2014, at 23:23, Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk> = wrote:

TL;DR: The link to the pre-built = binaries in [1] is broken, but building from
source I was able = to successfully install mirage on the Cubieboard and run = the
UNIX version of the Hello, World! unikernel. =  However, the Xen version did not
work because the opam = package mirage-xen 1.1.1 did not compile (some command
line = options were not recognized by cc).  The full build log is = at

It = seems that this problem should be quite easy to solve by someone = more
knowledgeable than = me.

I've fixed the links to = the prebuilt binaries in the README; you can grab the latest = from
http://blobs.openmirage.org/ = now (rebuilt daily).

To reiterate the previous = mail, you need this opam remote to grab the ARM
capable = libraries:

opam remote add mirage-dev git://github.com/mirage/mirage= -dev

(releases on their way just as soon as = vchan is integrated, and some load testing
complete on = cohttp).

cheers,
Anil
= --Apple-Mail=_AF49119D-A47D-48A5-A2F2-423FCD670073-- --===============5701256038450775756== 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 --===============5701256038450775756==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 09:36:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 09:36: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 1XTpB1-0004xW-27; Tue, 16 Sep 2014 09:35:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTpB0-0004xR-8w for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 09:35:58 +0000 Received: from [85.158.137.68:36648] by server-9.bemta-3.messagelabs.com id 1F/B4-30790-D7408145; Tue, 16 Sep 2014 09:35:57 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1410860156!14754911!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7113 invoked from network); 16 Sep 2014 09:35:56 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-16.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2014 09:35:56 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:59512 helo=[10.0.0.151]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XTpAy-00069u-DQ (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 16 Sep 2014 10:35:56 +0100 From: Amir Chaudhry Message-Id: <1477596B-78FC-49FE-AD31-2BC2291BA927@cam.ac.uk> Date: Tue, 16 Sep 2014 10:35:55 +0100 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Tuesday 16th at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Folks, = The next Mirage call will take place this afternoon (Tuesday) at 4pm BST. A= s always, calls are open to all, as is the agenda. It's always great to hea= r what people are trying out so please do feel free to get involved! = Since coming back from a trip to Istanbul I now have a bazaar habit of tryi= ng to haggle for everything (that's a pun, not a typo). So I'll make you an= offer -- if you add it to the Agenda, I'll take notes on it. Let me gift-= wrap that before you have a chance to respond. Agenda: https://github.com/mirage/mirage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays with this= , I'll switch to a Google Hangout. If that happens, I'll post the link her= e and also in the IRC channel (#mirage on freenode). Join us at 4pm BST! Access is 100 Lira=85 but, for you effendi, special pr= ice of 80 =85 I'm cutting my finger for you. Ok, ok, 40, then. Deal! (*) 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting (*) Not exactly a transcript, but I really did have conversations like this= . Surreal. -- Also, the Mirage calls are free, just so there's no confusio= n :) Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 09:36:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 09:36: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 1XTpB1-0004xW-27; Tue, 16 Sep 2014 09:35:59 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTpB0-0004xR-8w for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 09:35:58 +0000 Received: from [85.158.137.68:36648] by server-9.bemta-3.messagelabs.com id 1F/B4-30790-D7408145; Tue, 16 Sep 2014 09:35:57 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1410860156!14754911!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7113 invoked from network); 16 Sep 2014 09:35:56 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-16.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2014 09:35:56 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:59512 helo=[10.0.0.151]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XTpAy-00069u-DQ (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 16 Sep 2014 10:35:56 +0100 From: Amir Chaudhry Message-Id: <1477596B-78FC-49FE-AD31-2BC2291BA927@cam.ac.uk> Date: Tue, 16 Sep 2014 10:35:55 +0100 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Tuesday 16th at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Folks, = The next Mirage call will take place this afternoon (Tuesday) at 4pm BST. A= s always, calls are open to all, as is the agenda. It's always great to hea= r what people are trying out so please do feel free to get involved! = Since coming back from a trip to Istanbul I now have a bazaar habit of tryi= ng to haggle for everything (that's a pun, not a typo). So I'll make you an= offer -- if you add it to the Agenda, I'll take notes on it. Let me gift-= wrap that before you have a chance to respond. Agenda: https://github.com/mirage/mirage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays with this= , I'll switch to a Google Hangout. If that happens, I'll post the link her= e and also in the IRC channel (#mirage on freenode). Join us at 4pm BST! Access is 100 Lira=85 but, for you effendi, special pr= ice of 80 =85 I'm cutting my finger for you. Ok, ok, 40, then. Deal! (*) 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting (*) Not exactly a transcript, but I really did have conversations like this= . Surreal. -- Also, the Mirage calls are free, just so there's no confusio= n :) Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 15:05:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 15:05:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTuJN-0001M5-Kk; Tue, 16 Sep 2014 15:04:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTuJM-0001M0-Tj for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 15:04:57 +0000 Received: from [85.158.139.211:14920] by server-3.bemta-5.messagelabs.com id AA/93-13873-89158145; Tue, 16 Sep 2014 15:04:56 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1410879895!11450519!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8974 invoked from network); 16 Sep 2014 15:04:55 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2014 15:04:55 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-183-204.eduroam.wireless.private.cam.ac.uk ([172.17.183.204]:62064) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XTuJK-0007fK-sR (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 16 Sep 2014 16:04:54 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <1477596B-78FC-49FE-AD31-2BC2291BA927@cam.ac.uk> Date: Tue, 16 Sep 2014 16:04:54 +0100 Message-Id: <3B950A43-C3E4-4729-A1BA-1DED9B7AB42B@cam.ac.uk> References: <1477596B-78FC-49FE-AD31-2BC2291BA927@cam.ac.uk> To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - Tuesday 16th at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org 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 It appears we're having issues with GTM so we're switching to Hangouts. Th= e URL is https://plus.google.com/hangouts/_/gsrp6h24wdpnctx5rfkjaonjc4a On 16 Sep 2014, at 10:35, Amir Chaudhry wrote: > Hi Folks, = > = > The next Mirage call will take place this afternoon (Tuesday) at 4pm BST.= As always, calls are open to all, as is the agenda. It's always great to h= ear what people are trying out so please do feel free to get involved! = > = > Since coming back from a trip to Istanbul I now have a bazaar habit of tr= ying to haggle for everything (that's a pun, not a typo). So I'll make you = an offer -- if you add it to the Agenda, I'll take notes on it. Let me gif= t-wrap that before you have a chance to respond. > = > Agenda: https://github.com/mirage/mirage-www/wiki/Call-Agenda > = > GoToMeeting details are below but if there are any hiccups/delays with th= is, I'll switch to a Google Hangout. If that happens, I'll post the link h= ere and also in the IRC channel (#mirage on freenode). > = > Join us at 4pm BST! Access is 100 Lira=85 but, for you effendi, special = price of 80 =85 I'm cutting my finger for you. Ok, ok, 40, then. Deal! (*) > = > = > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > = > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > = > = > (*) Not exactly a transcript, but I really did have conversations like th= is. Surreal. -- Also, the Mirage calls are free, just so there's no confus= ion :) > = > Best wishes, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 15:05:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 15:05:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTuJN-0001M5-Kk; Tue, 16 Sep 2014 15:04:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTuJM-0001M0-Tj for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 15:04:57 +0000 Received: from [85.158.139.211:14920] by server-3.bemta-5.messagelabs.com id AA/93-13873-89158145; Tue, 16 Sep 2014 15:04:56 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1410879895!11450519!1 X-Originating-IP: [131.111.8.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MCA9PiAxNDk0MDU=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8974 invoked from network); 16 Sep 2014 15:04:55 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Sep 2014 15:04:55 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-183-204.eduroam.wireless.private.cam.ac.uk ([172.17.183.204]:62064) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XTuJK-0007fK-sR (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 16 Sep 2014 16:04:54 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <1477596B-78FC-49FE-AD31-2BC2291BA927@cam.ac.uk> Date: Tue, 16 Sep 2014 16:04:54 +0100 Message-Id: <3B950A43-C3E4-4729-A1BA-1DED9B7AB42B@cam.ac.uk> References: <1477596B-78FC-49FE-AD31-2BC2291BA927@cam.ac.uk> To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call - Tuesday 16th at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org 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 It appears we're having issues with GTM so we're switching to Hangouts. Th= e URL is https://plus.google.com/hangouts/_/gsrp6h24wdpnctx5rfkjaonjc4a On 16 Sep 2014, at 10:35, Amir Chaudhry wrote: > Hi Folks, = > = > The next Mirage call will take place this afternoon (Tuesday) at 4pm BST.= As always, calls are open to all, as is the agenda. It's always great to h= ear what people are trying out so please do feel free to get involved! = > = > Since coming back from a trip to Istanbul I now have a bazaar habit of tr= ying to haggle for everything (that's a pun, not a typo). So I'll make you = an offer -- if you add it to the Agenda, I'll take notes on it. Let me gif= t-wrap that before you have a chance to respond. > = > Agenda: https://github.com/mirage/mirage-www/wiki/Call-Agenda > = > GoToMeeting details are below but if there are any hiccups/delays with th= is, I'll switch to a Google Hangout. If that happens, I'll post the link h= ere and also in the IRC channel (#mirage on freenode). > = > Join us at 4pm BST! Access is 100 Lira=85 but, for you effendi, special = price of 80 =85 I'm cutting my finger for you. Ok, ok, 40, then. Deal! (*) > = > = > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > = > Dial in numbers (ask if you need a specific country): > United Kingdom: +44 (0) 20 3657 6778 > United States: +1 (213) 493-0014 > Access Code: 591-890-401 > Audio PIN: Shown after joining the meeting > = > = > (*) Not exactly a transcript, but I really did have conversations like th= is. Surreal. -- Also, the Mirage calls are free, just so there's no confus= ion :) > = > Best wishes, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 17:41:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 17:41: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 1XTwkO-0001b1-1R; Tue, 16 Sep 2014 17:41:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTwkM-0001aw-DF for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 17:40:58 +0000 Received: from [85.158.137.68:33351] by server-11.bemta-3.messagelabs.com id 4B/39-01568-92678145; Tue, 16 Sep 2014 17:40:57 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1410889256!14888760!1 X-Originating-IP: [209.85.212.172] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10099 invoked from network); 16 Sep 2014 17:40:57 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2014 17:40:57 -0000 Received: by mail-wi0-f172.google.com with SMTP id e4so6750525wiv.11 for ; Tue, 16 Sep 2014 10:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cTrR5F+WLMtiKpI7ktFiRerdLWWcsD3i5oz8lt4cp/0=; b=TgDf1N6IzUhpoPKSuIx3b2VCwpnVo+yIXTpMfv+8iB2YwGn9RBoNUSbgXmNsNfLzeJ afNTSxpA/Z3dDwx2QYv68NV/wNsBoGbSCTiPpQXNo3wT8Y/oYuDMBPXYW59KBwIohRPQ ucmDtOhXzUWZe8eewXzQqC1eVVFDMNRPpDbkFvwQYPAaCrhWhSGlX87/RICS8vJ5ENmZ GtMLqq/d5xEpda8DPlSr2b5MICmcIIl82jUnV6OUCYGm90dqZXGSg1Hpo3Ofj0e+JvYu b6RMNQ5sy3PFyD2OBDgtOLSx+QU+d2Mhl1CIELNMq+drHPeKlpaQiRN+a1wWbLnoNAoY 4jfg== MIME-Version: 1.0 X-Received: by 10.180.14.74 with SMTP id n10mr35234051wic.50.1410889256529; Tue, 16 Sep 2014 10:40:56 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Tue, 16 Sep 2014 10:40:56 -0700 (PDT) Date: Tue, 16 Sep 2014 14:40:56 -0300 Message-ID: From: Stephen Mack To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] How much of Xen will be migrated to 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: multipart/mixed; boundary="===============2278561363351548938==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2278561363351548938== Content-Type: multipart/alternative; boundary=f46d04138a57f3f44605033240f8 --f46d04138a57f3f44605033240f8 Content-Type: text/plain; charset=UTF-8 Hello everyone, In my attempt to get my mind around xen/mirage I see that some xen modules have adopted mirage as their development platform. XenStore is an example. Is there any strategic direction to migrate more of xen to run in mirage unikernals? --Stephen --f46d04138a57f3f44605033240f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone,

In my attempt to get my= mind around xen/mirage I see that some xen modules have adopted mirage as = their development platform.

XenStore is an example= .

Is there any strategic direction to migrate more= of xen to run in mirage unikernals?

--Stephen
--f46d04138a57f3f44605033240f8-- --===============2278561363351548938== 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 --===============2278561363351548938==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 16 17:41:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 16 Sep 2014 17:41: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 1XTwkO-0001b1-1R; Tue, 16 Sep 2014 17:41:00 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XTwkM-0001aw-DF for mirageos-devel@lists.xenproject.org; Tue, 16 Sep 2014 17:40:58 +0000 Received: from [85.158.137.68:33351] by server-11.bemta-3.messagelabs.com id 4B/39-01568-92678145; Tue, 16 Sep 2014 17:40:57 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1410889256!14888760!1 X-Originating-IP: [209.85.212.172] 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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10099 invoked from network); 16 Sep 2014 17:40:57 -0000 Received: from mail-wi0-f172.google.com (HELO mail-wi0-f172.google.com) (209.85.212.172) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 16 Sep 2014 17:40:57 -0000 Received: by mail-wi0-f172.google.com with SMTP id e4so6750525wiv.11 for ; Tue, 16 Sep 2014 10:40:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=cTrR5F+WLMtiKpI7ktFiRerdLWWcsD3i5oz8lt4cp/0=; b=TgDf1N6IzUhpoPKSuIx3b2VCwpnVo+yIXTpMfv+8iB2YwGn9RBoNUSbgXmNsNfLzeJ afNTSxpA/Z3dDwx2QYv68NV/wNsBoGbSCTiPpQXNo3wT8Y/oYuDMBPXYW59KBwIohRPQ ucmDtOhXzUWZe8eewXzQqC1eVVFDMNRPpDbkFvwQYPAaCrhWhSGlX87/RICS8vJ5ENmZ GtMLqq/d5xEpda8DPlSr2b5MICmcIIl82jUnV6OUCYGm90dqZXGSg1Hpo3Ofj0e+JvYu b6RMNQ5sy3PFyD2OBDgtOLSx+QU+d2Mhl1CIELNMq+drHPeKlpaQiRN+a1wWbLnoNAoY 4jfg== MIME-Version: 1.0 X-Received: by 10.180.14.74 with SMTP id n10mr35234051wic.50.1410889256529; Tue, 16 Sep 2014 10:40:56 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Tue, 16 Sep 2014 10:40:56 -0700 (PDT) Date: Tue, 16 Sep 2014 14:40:56 -0300 Message-ID: From: Stephen Mack To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] How much of Xen will be migrated to 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: multipart/mixed; boundary="===============2278561363351548938==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2278561363351548938== Content-Type: multipart/alternative; boundary=f46d04138a57f3f44605033240f8 --f46d04138a57f3f44605033240f8 Content-Type: text/plain; charset=UTF-8 Hello everyone, In my attempt to get my mind around xen/mirage I see that some xen modules have adopted mirage as their development platform. XenStore is an example. Is there any strategic direction to migrate more of xen to run in mirage unikernals? --Stephen --f46d04138a57f3f44605033240f8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello everyone,

In my attempt to get my= mind around xen/mirage I see that some xen modules have adopted mirage as = their development platform.

XenStore is an example= .

Is there any strategic direction to migrate more= of xen to run in mirage unikernals?

--Stephen
--f46d04138a57f3f44605033240f8-- --===============2278561363351548938== 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 --===============2278561363351548938==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 08:11:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 08:11:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUAKX-00076i-8T; Wed, 17 Sep 2014 08:11:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUAKV-00076c-Ob for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 08:11:11 +0000 Received: from [85.158.143.35:31104] by server-3.bemta-4.messagelabs.com id 7E/E3-06192-F1249145; Wed, 17 Sep 2014 08:11:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1410941470!14310356!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28469 invoked from network); 17 Sep 2014 08:11:10 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 08:11:10 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 731a0e64; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 17 Sep 2014 09:11:55 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 17 Sep 2014 09:11:06 +0100 Message-Id: <349CF8D4-9989-4DE1-AE00-016E660E41BD@recoil.org> References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] How much of Xen will be migrated to 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: multipart/mixed; boundary="===============3472606939480066758==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3472606939480066758== Content-Type: multipart/alternative; boundary="Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1" --Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16 Sep 2014, at 18:40, Stephen Mack wrote: > Hello everyone, >=20 > In my attempt to get my mind around xen/mirage I see that some xen = modules have adopted mirage as their development platform. >=20 > XenStore is an example. >=20 > Is there any strategic direction to migrate more of xen to run in = mirage unikernals? Xen consists of a number of components, but Xenstore and the Xenconsoled = are the main obvious candidates to replace first. After that, there is = the management toolstack itself. This is a slightly old talk, but should give you a sense of what is = involved: = http://www.xenproject.org/component/allvideoshare/video/latest/windsor-dom= ain-0-disaggregation-for-xenserver-and-xcp.html -anil --Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 16 = Sep 2014, at 18:40, Stephen Mack <smack815@gmail.com> = wrote:

Hello everyone,

In my = attempt to get my mind around xen/mirage I see that some xen modules = have adopted mirage as their development = platform.

XenStore is an = example.

Is there any strategic direction to = migrate more of xen to run in mirage = unikernals?

Xen = consists of a number of components, but Xenstore and the Xenconsoled are = the main obvious candidates to replace first.  After that, there is = the management toolstack itself.

This is a = slightly old talk, but should give you a sense of what is = involved:

-anil
= --Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1-- --===============3472606939480066758== 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 --===============3472606939480066758==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 08:11:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 08:11:20 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUAKX-00076i-8T; Wed, 17 Sep 2014 08:11:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUAKV-00076c-Ob for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 08:11:11 +0000 Received: from [85.158.143.35:31104] by server-3.bemta-4.messagelabs.com id 7E/E3-06192-F1249145; Wed, 17 Sep 2014 08:11:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1410941470!14310356!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28469 invoked from network); 17 Sep 2014 08:11:10 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 08:11:10 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 731a0e64; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 17 Sep 2014 09:11:55 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 17 Sep 2014 09:11:06 +0100 Message-Id: <349CF8D4-9989-4DE1-AE00-016E660E41BD@recoil.org> References: To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] How much of Xen will be migrated to 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: multipart/mixed; boundary="===============3472606939480066758==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3472606939480066758== Content-Type: multipart/alternative; boundary="Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1" --Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 16 Sep 2014, at 18:40, Stephen Mack wrote: > Hello everyone, >=20 > In my attempt to get my mind around xen/mirage I see that some xen = modules have adopted mirage as their development platform. >=20 > XenStore is an example. >=20 > Is there any strategic direction to migrate more of xen to run in = mirage unikernals? Xen consists of a number of components, but Xenstore and the Xenconsoled = are the main obvious candidates to replace first. After that, there is = the management toolstack itself. This is a slightly old talk, but should give you a sense of what is = involved: = http://www.xenproject.org/component/allvideoshare/video/latest/windsor-dom= ain-0-disaggregation-for-xenserver-and-xcp.html -anil --Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 16 = Sep 2014, at 18:40, Stephen Mack <smack815@gmail.com> = wrote:

Hello everyone,

In my = attempt to get my mind around xen/mirage I see that some xen modules = have adopted mirage as their development = platform.

XenStore is an = example.

Is there any strategic direction to = migrate more of xen to run in mirage = unikernals?

Xen = consists of a number of components, but Xenstore and the Xenconsoled are = the main obvious candidates to replace first.  After that, there is = the management toolstack itself.

This is a = slightly old talk, but should give you a sense of what is = involved:

-anil
= --Apple-Mail=_3F8557BD-C17B-406B-B362-0DBB3EE5E8A1-- --===============3472606939480066758== 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 --===============3472606939480066758==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 08:20:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 08:20: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 1XUATT-0007RR-LB; Wed, 17 Sep 2014 08:20:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUATR-0007RJ-Ut for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 08:20:26 +0000 Received: from [85.158.143.35:7043] by server-2.bemta-4.messagelabs.com id 59/7C-04525-94449145; Wed, 17 Sep 2014 08:20:25 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1410942023!13633680!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19035 invoked from network); 17 Sep 2014 08:20:23 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2014 08:20:23 -0000 Received: by mail-wg0-f43.google.com with SMTP id x12so987084wgg.2 for ; Wed, 17 Sep 2014 01:20:23 -0700 (PDT) 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=dezw+1/FoRuAcUuacUQQ+y9R66c89kzoedsD50rDqLc=; b=LlirdftiHOFiIyvWKSgGry8p297/VbB2tHPBzqLEkQnyS2Kmkplm4NKdtHkxA+0/e5 2YYl1BpBnv7vAK1QpsA0L1otih4a19HzbRn/RlYaXTyW8+gaPvSizK0YdPi7ctwuXj4c elzEaKkbgI2EyPf76uE6LS2PguB6EqrXbIipUqnIwsmPEAVqPLDtIugudrmPlYY5lKZ2 FCNmXWhmD2GK9j8h3n4Zjivhtb01Ca8PlaEAtQDMZXOVpY5LgNfBc/AteNfIa77Mch7U gAoRioirfW5eO2g8PDBES3R70Y4cp39hW4TNFSvZqQIKmstoDjiE+522A84QCt7ItR33 S5Vw== X-Received: by 10.180.89.243 with SMTP id br19mr37457357wib.41.1410942023484; Wed, 17 Sep 2014 01:20:23 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id wp7sm2115127wjc.12.2014.09.17.01.20.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Sep 2014 01:20:22 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 17 Sep 2014 09:20:24 +0100 Message-Id: References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> To: Jon Crowcroft X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6234053116871481188==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6234053116871481188== Content-Type: multipart/alternative; boundary="Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396" --Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii very interesting reads, thanks! that's pretty cool to see that everyone = seems to work on the same structures (Merkle graphs) but using a = complete different vocabulary ... Thomas On 15 Sep 2014, at 15:52, Jon Crowcroft = wrote: > esp. use of (sparse, very big) merkle trees, gossip for consistency, = etc >=20 > reminded me should also re-view work from MPI on dealing with = adversaries (e.g. peer review etc > http://www.mpi-sws.org/~druschel/publications/peerreview-sosp07.pdf >=20 > On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = wrote: > v cool >=20 > here's a (another) possible use case for irmin: > http://queue.acm.org/detail.cfm?id=3D2668154 >=20 > In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, = Thomas Gazagn > aire typed: >=20 > >>Hi all, > >> > >>Lots of people starting asked me about the status of Irmin. As you = might have notice, I'vent had much time to spend on Irmin last month, = but I plan to fix that. My current priorities are: > >> > >>1/ make Irmin compiles on the Xen backend of Mirage. = https://github.com/mirage/irmin/issues/81 > >>This means dropping the dependency to core_kernel (for now on). The = external API will not change. > >> > >>2/ improve the high-level JSON API. This is related to = https://github.com/mirage/irmin/issues/80 > >>Currently, we only have a JSON API for the low-level stores, and = the very partial implementation of the higher-level calls. Needs to = complete and document that. > >> > >>3/ implement a pure-ocaml Git server to be able to at least `git = pull` from it. https://github.com/mirage/ocaml-git/issues/15 > >>Together with 1/ this will make possible to query the state of a = running Mirage unikernel with a simple `git pull ` > >> > >>4/ implement a simple distributed log server = .https://github.com/mirage/irmin/issues/82 > >>Could use Benjamin's rope implementation, that I first need to = release properly. > >> > >>5/ try to come up with a solution to the "unlimited" memory/storage = usage issues https://github.com/mirage/irmin/issues/83 > >>This is the most uncertain part of the short-term roadmap. I'll = need to check again what are the limitation of Git shallow copies and = see how we can use them to limit the history size to remember. > >> > >>There are also few open embarrassing bugs that I want to fix as = well (regarding fd leaks ...). > >> > >>If anyone is interested to help me on any of these topics, please = feel free to comment on the related issues on Github -- I'll gladly = share the workload. Also, feel free to reply to that email if you think = there is any important Imrin features that you think are missing now. > >> > >>Best, > >>Thomas > >>_______________________________________________ > >>MirageOS-devel mailing list > >>MirageOS-devel@lists.xenproject.org > >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > cheers >=20 > jon >=20 >=20 --Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii very = interesting reads, thanks! that's pretty cool to see that everyone seems = to work on the same structures (Merkle graphs) but using a complete = different vocabulary = ...

Thomas

On 15 Sep 2014, at = 15:52, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk&= gt; wrote:

esp. use of (sparse, very big) merkle = trees, gossip for consistency, etc

reminded me should = also re-view work from MPI on dealing with adversaries (e.g. peer review = etc

On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = <Jon.Crowcroft@cl.cam.ac.uk> = wrote:
v cool

here's a (another) possible use case for irmin:
http://queue.acm.org/detail.cfm?id=3D2668154

In missive <69D665= AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas Gazagn
aire typed:

 >>Hi all,
 >>
 >>Lots of people starting asked me about the status of = Irmin. As you might have notice, I'vent had much time to spend on Irmin = last month, but I plan to fix that. My current priorities are:
 >>
 >>1/ make Irmin compiles on the Xen backend of Mirage.  = https://github.com/mirage/irmin/issues/81
 >>This means dropping the dependency to core_kernel (for now = on). The external API will not change.
 >>
 >>2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80
 >>Currently, we only have a JSON API for the low-level = stores, and the very partial implementation of the higher-level calls. = Needs to complete and document that.
 >>
 >>3/ implement a pure-ocaml Git server to be able to at = least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15
 >>Together with 1/ this will make possible to query the = state of a running Mirage unikernel with a simple `git pull = <vm-address>`
 >>
 >>4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82
 >>Could use Benjamin's rope implementation, that I first = need to release properly.
 >>
 >>5/ try to come up with a solution to the "unlimited" = memory/storage usage issues https://github.com/mirage/irmin/issues/83
 >>This is the most uncertain part of the short-term roadmap. = I'll need to check again what are the limitation of Git shallow copies = and see how we can use them to limit the history size to remember.
 >>
 >>There are also few open embarrassing bugs that I want to = fix as well (regarding fd leaks ...).
 >>
 >>If anyone is interested to help me on any of these topics, = please feel free to comment on the related issues on Github -- I'll = gladly share the workload. Also, feel free to reply to that email if you = think there is any important Imrin features that you think are missing = now.
 >>
 >>Best,
 >>Thomas
 >>_______________________________________________
 >>MirageOS-devel mailing list
 >>MirageOS-devel@lists.x= enproject.org
 >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel

 cheers

   jon



= --Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396-- --===============6234053116871481188== 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 --===============6234053116871481188==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 08:20:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 08:20: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 1XUATT-0007RR-LB; Wed, 17 Sep 2014 08:20:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUATR-0007RJ-Ut for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 08:20:26 +0000 Received: from [85.158.143.35:7043] by server-2.bemta-4.messagelabs.com id 59/7C-04525-94449145; Wed, 17 Sep 2014 08:20:25 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1410942023!13633680!1 X-Originating-IP: [74.125.82.43] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19035 invoked from network); 17 Sep 2014 08:20:23 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Sep 2014 08:20:23 -0000 Received: by mail-wg0-f43.google.com with SMTP id x12so987084wgg.2 for ; Wed, 17 Sep 2014 01:20:23 -0700 (PDT) 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=dezw+1/FoRuAcUuacUQQ+y9R66c89kzoedsD50rDqLc=; b=LlirdftiHOFiIyvWKSgGry8p297/VbB2tHPBzqLEkQnyS2Kmkplm4NKdtHkxA+0/e5 2YYl1BpBnv7vAK1QpsA0L1otih4a19HzbRn/RlYaXTyW8+gaPvSizK0YdPi7ctwuXj4c elzEaKkbgI2EyPf76uE6LS2PguB6EqrXbIipUqnIwsmPEAVqPLDtIugudrmPlYY5lKZ2 FCNmXWhmD2GK9j8h3n4Zjivhtb01Ca8PlaEAtQDMZXOVpY5LgNfBc/AteNfIa77Mch7U gAoRioirfW5eO2g8PDBES3R70Y4cp39hW4TNFSvZqQIKmstoDjiE+522A84QCt7ItR33 S5Vw== X-Received: by 10.180.89.243 with SMTP id br19mr37457357wib.41.1410942023484; Wed, 17 Sep 2014 01:20:23 -0700 (PDT) Received: from [192.168.0.2] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id wp7sm2115127wjc.12.2014.09.17.01.20.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Sep 2014 01:20:22 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 17 Sep 2014 09:20:24 +0100 Message-Id: References: <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org> To: Jon Crowcroft X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] Irmin roadmap X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6234053116871481188==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6234053116871481188== Content-Type: multipart/alternative; boundary="Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396" --Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii very interesting reads, thanks! that's pretty cool to see that everyone = seems to work on the same structures (Merkle graphs) but using a = complete different vocabulary ... Thomas On 15 Sep 2014, at 15:52, Jon Crowcroft = wrote: > esp. use of (sparse, very big) merkle trees, gossip for consistency, = etc >=20 > reminded me should also re-view work from MPI on dealing with = adversaries (e.g. peer review etc > http://www.mpi-sws.org/~druschel/publications/peerreview-sosp07.pdf >=20 > On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = wrote: > v cool >=20 > here's a (another) possible use case for irmin: > http://queue.acm.org/detail.cfm?id=3D2668154 >=20 > In missive <69D665AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, = Thomas Gazagn > aire typed: >=20 > >>Hi all, > >> > >>Lots of people starting asked me about the status of Irmin. As you = might have notice, I'vent had much time to spend on Irmin last month, = but I plan to fix that. My current priorities are: > >> > >>1/ make Irmin compiles on the Xen backend of Mirage. = https://github.com/mirage/irmin/issues/81 > >>This means dropping the dependency to core_kernel (for now on). The = external API will not change. > >> > >>2/ improve the high-level JSON API. This is related to = https://github.com/mirage/irmin/issues/80 > >>Currently, we only have a JSON API for the low-level stores, and = the very partial implementation of the higher-level calls. Needs to = complete and document that. > >> > >>3/ implement a pure-ocaml Git server to be able to at least `git = pull` from it. https://github.com/mirage/ocaml-git/issues/15 > >>Together with 1/ this will make possible to query the state of a = running Mirage unikernel with a simple `git pull ` > >> > >>4/ implement a simple distributed log server = .https://github.com/mirage/irmin/issues/82 > >>Could use Benjamin's rope implementation, that I first need to = release properly. > >> > >>5/ try to come up with a solution to the "unlimited" memory/storage = usage issues https://github.com/mirage/irmin/issues/83 > >>This is the most uncertain part of the short-term roadmap. I'll = need to check again what are the limitation of Git shallow copies and = see how we can use them to limit the history size to remember. > >> > >>There are also few open embarrassing bugs that I want to fix as = well (regarding fd leaks ...). > >> > >>If anyone is interested to help me on any of these topics, please = feel free to comment on the related issues on Github -- I'll gladly = share the workload. Also, feel free to reply to that email if you think = there is any important Imrin features that you think are missing now. > >> > >>Best, > >>Thomas > >>_______________________________________________ > >>MirageOS-devel mailing list > >>MirageOS-devel@lists.xenproject.org > >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > cheers >=20 > jon >=20 >=20 --Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii very = interesting reads, thanks! that's pretty cool to see that everyone seems = to work on the same structures (Merkle graphs) but using a complete = different vocabulary = ...

Thomas

On 15 Sep 2014, at = 15:52, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk&= gt; wrote:

esp. use of (sparse, very big) merkle = trees, gossip for consistency, etc

reminded me should = also re-view work from MPI on dealing with adversaries (e.g. peer review = etc

On Sat, Sep 13, 2014 at 1:08 PM, Jon Crowcroft = <Jon.Crowcroft@cl.cam.ac.uk> = wrote:
v cool

here's a (another) possible use case for irmin:
http://queue.acm.org/detail.cfm?id=3D2668154

In missive <69D665= AD-E191-40B2-8E41-0111697C2E7F@gazagnaire.org>, Thomas Gazagn
aire typed:

 >>Hi all,
 >>
 >>Lots of people starting asked me about the status of = Irmin. As you might have notice, I'vent had much time to spend on Irmin = last month, but I plan to fix that. My current priorities are:
 >>
 >>1/ make Irmin compiles on the Xen backend of Mirage.  = https://github.com/mirage/irmin/issues/81
 >>This means dropping the dependency to core_kernel (for now = on). The external API will not change.
 >>
 >>2/ improve the high-level JSON API. This is related to https://github.com/mirage/irmin/issues/80
 >>Currently, we only have a JSON API for the low-level = stores, and the very partial implementation of the higher-level calls. = Needs to complete and document that.
 >>
 >>3/ implement a pure-ocaml Git server to be able to at = least `git pull` from it. https://github.com/mirage/ocaml-git/issues/15
 >>Together with 1/ this will make possible to query the = state of a running Mirage unikernel with a simple `git pull = <vm-address>`
 >>
 >>4/ implement a simple distributed log server .https://github.com/mirage/irmin/issues/82
 >>Could use Benjamin's rope implementation, that I first = need to release properly.
 >>
 >>5/ try to come up with a solution to the "unlimited" = memory/storage usage issues https://github.com/mirage/irmin/issues/83
 >>This is the most uncertain part of the short-term roadmap. = I'll need to check again what are the limitation of Git shallow copies = and see how we can use them to limit the history size to remember.
 >>
 >>There are also few open embarrassing bugs that I want to = fix as well (regarding fd leaks ...).
 >>
 >>If anyone is interested to help me on any of these topics, = please feel free to comment on the related issues on Github -- I'll = gladly share the workload. Also, feel free to reply to that email if you = think there is any important Imrin features that you think are missing = now.
 >>
 >>Best,
 >>Thomas
 >>_______________________________________________
 >>MirageOS-devel mailing list
 >>MirageOS-devel@lists.x= enproject.org
 >>http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel

 cheers

   jon



= --Apple-Mail=_A43483CE-1186-41D3-8345-2564FB577396-- --===============6234053116871481188== 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 --===============6234053116871481188==-- From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 08:33:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 08: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 1XUAgE-0008Ly-Bn; Wed, 17 Sep 2014 08:33:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUAgD-0008Lr-OT for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 08:33:37 +0000 Received: from [85.158.137.68:27593] by server-7.bemta-3.messagelabs.com id 79/75-01084-16749145; Wed, 17 Sep 2014 08:33:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1410942815!15059088!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, RCVD_ILLEGAL_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7059 invoked from network); 17 Sep 2014 08:33:36 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 08:33:36 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 6f0a7b2b; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 17 Sep 2014 09:34:21 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 17 Sep 2014 09:33:32 +0100 Message-Id: <64599DB6-D372-4D2D-A1C3-8F65FF882585@recoil.org> References: <53242E73-6AD5-4CDD-8F6C-EC8F2FDD0D28@recoil.org> <8115D7D9-B3EA-4957-9249-AE3BFE3FFB83@me.com> <264C3D63-DEA4-4718-84BA-3AD7A6D1272C@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Struggling a bit with the Hello World applications X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 May 2014, at 12:01, Dave Scott wrote: > On 6 May 2014, at 11:35, Anil Madhavapeddy wrote: >> On 5 May 2014, at 21:34, Andr=E9 N=E6ss wrote: >>> = >>> On Mon, May 5, 2014 at 7:26 PM, Anil Madhavapeddy wro= te: >>>> Below is what happened: >>>> = >>>> On 14.04 I got this while running opam init: >>>> = >>>> ERROR] The compilation of base-bigarray.base failed. >>>> [ERROR] The compilation of base-threads.base failed. >>>> [ERROR] The compilation of base-unix.base failed. >>>> = >>>> =3D=3D=3D=3D=3D ERROR while installing base-bigarray.base =3D=3D=3D=3D= =3D >>>> Internal error: >>>> Sys_error("rm -rf /home/vagrant/.opam/system/lib/base-bigarray: Cannot= allocate memory") >>>> = >>>> =3D=3D=3D=3D=3D ERROR while installing base-threads.base =3D=3D=3D=3D= =3D >>>> Internal error: >>>> Sys_error("rm -rf /home/vagrant/.opam/system/lib/base-threads: Cannot = allocate memory") >>>> = >>>> =3D=3D=3D=3D=3D ERROR while installing base-unix.base =3D=3D=3D=3D=3D >>>> Internal error: >>>> Sys_error("rm -rf /home/vagrant/.opam/system/lib/base-unix: Cannot all= ocate memory") >>> = >>> To ask the obvious question: how much memory does this VM have? >>> = >>> I just tried reproducing this on a fresh Ubuntu 14.04 VMWare Fusion: >>> = >>> = >>> Ok, I'm slightly embarrassed now. I bumped the memory on the VM to 1024= . The Vagrant default is pretty low. It works fine now. >> = >> Thanks for confirming it works (phew). This does touch on the important= point of us distributed tested Vagrant boxes. >> = >> I just signed up for the Vagrant cloud that's in beta at the moment, and= will look into publishing an OPAM-friendly image with all the bits'n'bobs = installed. > = > I=92ve hit this problem a few times myself. I=92m also not happy with the= provenance of the vagrant boxes I=92m currently using: I really want somet= hing which can be built reproducibly from trusted pieces. Hosting my own bo= x is also a bit of a pain since they often are 500MiB-1GiB. (I believe the = vagrant cloud will host a link but not the artefact itself?) > = > So I started with Mort=92s mirage-vagrant-vms repo and switched from veew= ee to packer[1][2]. I found packer to be easier to install than veewee but = otherwise much the same. My box development cycle is now: > = > packer build template.json > vagrant box remove foo > vagrant box add new.box =97name foo > = > My goal is to build all my boxes from: > 1. the definitions (the .json plus scripts) stored in .git > 2. the distro install CD (cached, with md5 checked) > 3. (hopefully small) repo of binary packages hosted by people I trust (e.= g. me). Hopefully this is <100MiB and therefore easier to host somewhere > = > [1] http://packer.io/ > [2] https://github.com/djs55/mirage-vagrant-vms/tree/packer Could you send a pull request for this to reconcile it with mirage/mirage-v= agrant-vms? Now that we have blobs.openmirage.org, I'd like to start building these reg= ularly too. 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 Wed Sep 17 08:33:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 08: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 1XUAgE-0008Ly-Bn; Wed, 17 Sep 2014 08:33:38 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUAgD-0008Lr-OT for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 08:33:37 +0000 Received: from [85.158.137.68:27593] by server-7.bemta-3.messagelabs.com id 79/75-01084-16749145; Wed, 17 Sep 2014 08:33:37 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1410942815!15059088!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, RCVD_ILLEGAL_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7059 invoked from network); 17 Sep 2014 08:33:36 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-5.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 08:33:36 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 6f0a7b2b; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 17 Sep 2014 09:34:21 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 17 Sep 2014 09:33:32 +0100 Message-Id: <64599DB6-D372-4D2D-A1C3-8F65FF882585@recoil.org> References: <53242E73-6AD5-4CDD-8F6C-EC8F2FDD0D28@recoil.org> <8115D7D9-B3EA-4957-9249-AE3BFE3FFB83@me.com> <264C3D63-DEA4-4718-84BA-3AD7A6D1272C@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Struggling a bit with the Hello World applications X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 May 2014, at 12:01, Dave Scott wrote: > On 6 May 2014, at 11:35, Anil Madhavapeddy wrote: >> On 5 May 2014, at 21:34, Andr=E9 N=E6ss wrote: >>> = >>> On Mon, May 5, 2014 at 7:26 PM, Anil Madhavapeddy wro= te: >>>> Below is what happened: >>>> = >>>> On 14.04 I got this while running opam init: >>>> = >>>> ERROR] The compilation of base-bigarray.base failed. >>>> [ERROR] The compilation of base-threads.base failed. >>>> [ERROR] The compilation of base-unix.base failed. >>>> = >>>> =3D=3D=3D=3D=3D ERROR while installing base-bigarray.base =3D=3D=3D=3D= =3D >>>> Internal error: >>>> Sys_error("rm -rf /home/vagrant/.opam/system/lib/base-bigarray: Cannot= allocate memory") >>>> = >>>> =3D=3D=3D=3D=3D ERROR while installing base-threads.base =3D=3D=3D=3D= =3D >>>> Internal error: >>>> Sys_error("rm -rf /home/vagrant/.opam/system/lib/base-threads: Cannot = allocate memory") >>>> = >>>> =3D=3D=3D=3D=3D ERROR while installing base-unix.base =3D=3D=3D=3D=3D >>>> Internal error: >>>> Sys_error("rm -rf /home/vagrant/.opam/system/lib/base-unix: Cannot all= ocate memory") >>> = >>> To ask the obvious question: how much memory does this VM have? >>> = >>> I just tried reproducing this on a fresh Ubuntu 14.04 VMWare Fusion: >>> = >>> = >>> Ok, I'm slightly embarrassed now. I bumped the memory on the VM to 1024= . The Vagrant default is pretty low. It works fine now. >> = >> Thanks for confirming it works (phew). This does touch on the important= point of us distributed tested Vagrant boxes. >> = >> I just signed up for the Vagrant cloud that's in beta at the moment, and= will look into publishing an OPAM-friendly image with all the bits'n'bobs = installed. > = > I=92ve hit this problem a few times myself. I=92m also not happy with the= provenance of the vagrant boxes I=92m currently using: I really want somet= hing which can be built reproducibly from trusted pieces. Hosting my own bo= x is also a bit of a pain since they often are 500MiB-1GiB. (I believe the = vagrant cloud will host a link but not the artefact itself?) > = > So I started with Mort=92s mirage-vagrant-vms repo and switched from veew= ee to packer[1][2]. I found packer to be easier to install than veewee but = otherwise much the same. My box development cycle is now: > = > packer build template.json > vagrant box remove foo > vagrant box add new.box =97name foo > = > My goal is to build all my boxes from: > 1. the definitions (the .json plus scripts) stored in .git > 2. the distro install CD (cached, with md5 checked) > 3. (hopefully small) repo of binary packages hosted by people I trust (e.= g. me). Hopefully this is <100MiB and therefore easier to host somewhere > = > [1] http://packer.io/ > [2] https://github.com/djs55/mirage-vagrant-vms/tree/packer Could you send a pull request for this to reconcile it with mirage/mirage-v= agrant-vms? Now that we have blobs.openmirage.org, I'd like to start building these reg= ularly too. 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 Wed Sep 17 10:53:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 10:53:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUCrQ-0005Rl-QU; Wed, 17 Sep 2014 10:53:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUCrP-0005Rb-5R for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 10:53:19 +0000 Received: from [193.109.254.147:60648] by server-14.bemta-14.messagelabs.com id 4C/D3-18345-E1869145; Wed, 17 Sep 2014 10:53:18 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1410951197!12764721!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11573 invoked from network); 17 Sep 2014 10:53:17 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 10:53:17 -0000 Received: from [192.168.178.21] (pD9576E4F.dip0.t-ipconnect.de [217.87.110.79]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 641811CDD; Wed, 17 Sep 2014 12:53:15 +0200 (CEST) Message-ID: <54196812.5080701@mehnert.org> Date: Wed, 17 Sep 2014 12:53:06 +0200 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Cc: david Subject: [MirageOS-devel] OCaml-TLS directly on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hey, I demonstrated that OCaml-TLS runs directly on Xen at the OCaml workshop. The port is still a bit hackish, thus I hope to get some feedback (esp. regarding what features (such as FORTIFY_SOURCE stack protection, and/or assert (should minios provide an assert_fail symbol?)) we want to compile our C code with, and how to upstream these changes properly). I develop on a cubieboard2, where I pinned mirage (44bd28f862549aa1f149421c1e515bb3703e40d7), mirage-xen (0251870f14030315b00ffdd0cd0112d8788270a1) and tcpip (05148f900352eabaa615b60d5b2fb518f5518edd) to git HEAD (as well as x509/asn1-combinators/nocrypto/tls). Several libraries needed to be modified to run in the Xen environment: minios - ------ https://github.com/hannesm/xen/tree/tls-fixes some symbols are required for the various C libraries below, namely: abort (calling do_exit) __stack_chk_guard (being NULL) fprintf/printf/stdout/stderr/fflush (for gmp and zarith) gmp (the GNU multi-precision arithmetic library) - ------------------------------------------------ Configure (esp. config.guess) gets confused by an arm dualcore: http://berlin.ccc.de/~hannes/gmp-6a.diff fixes this. I used the following CFLAGS: export CFLAGS="-marm -O2 -pedantic -fomit-frame-pointer -fno-builtin - -D_FORTIFY_SOURCE=0" ./configure make zarith - ------ Due to subtle differences of GNU libm and openlibm (esp isinf/isnan is rewritten in the GNU version to __isinf/__isnan), I modified caml_z.c to #include instead of (should openlibm instead install its header file as math.h!?) Patch at http://berlin.ccc.de/~hannes/zarith.diff I additionally pointed zarith to my custom gmp library: export CPPFLAGS="-I/home/mirage/gmp-6.0.0.orig - -I/home/mirage/.opam/system/include" export LDFLAGS="-L/home/mirage/gmp-6.0.0.orig/.libs" (the previously mentioned CFLAGS are also still active!) ctypes (0.3.3) - -------------- nocrypto (from git) depends on ctypes, which needed some CFLAGS (to avoid assert_fail being called (-DNDEBUG), sscanf being translated to __isoc99_sscanf (-D_GNU_SOURCE)), patch http://berlin.ccc.de/~hannes/ctypes.diff nocrypto - -------- https://github.com/mirleft/ocaml-nocrypto/tree/xen-fixes (adds -DNDEBUG) tls - --- https://github.com/mirleft/ocaml-tls/tree/xen-fixes (use Io_page aligned cstructs before transmitting) Once these libraries are patched, the minimum TLS server https://github.com/mirleft/tls-mvp-server/tree/fixes works (with export NET="direct" and s/-unix/-xen/ (mirage-clock-xen, mirage-entropy-xen) in config.ml), and some minor modifications to the Makefile to link in the right gmp/minios/... Cheers, hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJUGWgSAAoJELyJZYjffCjuEmwP/1jKJH4tZeHLB4LG1+Yotg5b YDS/VttiH8xCstlOSx+rq9VefJlzzmCaXTC1C9+yJZciyPhRM4P9J1NVaJmh4OcK qoVEJFe7zrnlCHj+348ZSOJ5mInRVzS/idMRuu+vtvAObpQVNS8/AAq0mgrQfjXS 7cjmb9JF7HJN7IKm3A9Zxx047RwIn/dzBjFhr36D9H0Crf1scN46hzWpVSciYuVF coNqbePjz1vq4bYjAYqjsKtNDQ5wo4sCHREKlon9YwzKxsuwovrwSgDYQIG0NSgL srKdDPmT9Lwi4i4HBba65nf7X4PgyiwbzjCmq7fTbYnDyQ/az5C2kE5Gqow1UEpB B0xgawkak2Ta9fSegNErykaZhL4OPUf0ug9T8hRGheDm8dkQvAG/jf7Z8kfh7lBk GggrYK4Fw1t05QRMQLGQ9Wem89r4r5+p2udxMAbm8NoiFn0xG2cMQj3Tjx6Py/Ao Cd6+YsKSgRMI0pgRb/vT5YbArZpuXJ112PryMyzkAwAs/bK0fyR6mDG+61gE3mvV /EXbvHWhWor1jfR3RXl2g15pbdY5TnJMvkrjqs1Ie5gvDybfcdwfS+NHClm/iIzP GKOykdscjfEw99Fzw10lwBZdcRTH8Kd8MCRQY+73uA776lIb+6EbrwahIxOW2O0l UGpbvb00yu8Fg+b+wikQ =TPqs -----END PGP SIGNATURE----- _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 10:53:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 10:53:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUCrQ-0005Rl-QU; Wed, 17 Sep 2014 10:53:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUCrP-0005Rb-5R for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 10:53:19 +0000 Received: from [193.109.254.147:60648] by server-14.bemta-14.messagelabs.com id 4C/D3-18345-E1869145; Wed, 17 Sep 2014 10:53:18 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1410951197!12764721!1 X-Originating-IP: [213.73.89.200] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11573 invoked from network); 17 Sep 2014 10:53:17 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-11.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 10:53:17 -0000 Received: from [192.168.178.21] (pD9576E4F.dip0.t-ipconnect.de [217.87.110.79]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "hannes@mehnert.org", Issuer "mehnert root CA" (verified OK)) by mail.mehnert.org (Postfix) with ESMTPS id 641811CDD; Wed, 17 Sep 2014 12:53:15 +0200 (CEST) Message-ID: <54196812.5080701@mehnert.org> Date: Wed, 17 Sep 2014 12:53:06 +0200 From: Hannes Mehnert User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: "mirageos-devel@lists.xenproject.org" Cc: david Subject: [MirageOS-devel] OCaml-TLS directly on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hey, I demonstrated that OCaml-TLS runs directly on Xen at the OCaml workshop. The port is still a bit hackish, thus I hope to get some feedback (esp. regarding what features (such as FORTIFY_SOURCE stack protection, and/or assert (should minios provide an assert_fail symbol?)) we want to compile our C code with, and how to upstream these changes properly). I develop on a cubieboard2, where I pinned mirage (44bd28f862549aa1f149421c1e515bb3703e40d7), mirage-xen (0251870f14030315b00ffdd0cd0112d8788270a1) and tcpip (05148f900352eabaa615b60d5b2fb518f5518edd) to git HEAD (as well as x509/asn1-combinators/nocrypto/tls). Several libraries needed to be modified to run in the Xen environment: minios - ------ https://github.com/hannesm/xen/tree/tls-fixes some symbols are required for the various C libraries below, namely: abort (calling do_exit) __stack_chk_guard (being NULL) fprintf/printf/stdout/stderr/fflush (for gmp and zarith) gmp (the GNU multi-precision arithmetic library) - ------------------------------------------------ Configure (esp. config.guess) gets confused by an arm dualcore: http://berlin.ccc.de/~hannes/gmp-6a.diff fixes this. I used the following CFLAGS: export CFLAGS="-marm -O2 -pedantic -fomit-frame-pointer -fno-builtin - -D_FORTIFY_SOURCE=0" ./configure make zarith - ------ Due to subtle differences of GNU libm and openlibm (esp isinf/isnan is rewritten in the GNU version to __isinf/__isnan), I modified caml_z.c to #include instead of (should openlibm instead install its header file as math.h!?) Patch at http://berlin.ccc.de/~hannes/zarith.diff I additionally pointed zarith to my custom gmp library: export CPPFLAGS="-I/home/mirage/gmp-6.0.0.orig - -I/home/mirage/.opam/system/include" export LDFLAGS="-L/home/mirage/gmp-6.0.0.orig/.libs" (the previously mentioned CFLAGS are also still active!) ctypes (0.3.3) - -------------- nocrypto (from git) depends on ctypes, which needed some CFLAGS (to avoid assert_fail being called (-DNDEBUG), sscanf being translated to __isoc99_sscanf (-D_GNU_SOURCE)), patch http://berlin.ccc.de/~hannes/ctypes.diff nocrypto - -------- https://github.com/mirleft/ocaml-nocrypto/tree/xen-fixes (adds -DNDEBUG) tls - --- https://github.com/mirleft/ocaml-tls/tree/xen-fixes (use Io_page aligned cstructs before transmitting) Once these libraries are patched, the minimum TLS server https://github.com/mirleft/tls-mvp-server/tree/fixes works (with export NET="direct" and s/-unix/-xen/ (mirage-clock-xen, mirage-entropy-xen) in config.ml), and some minor modifications to the Makefile to link in the right gmp/minios/... Cheers, hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJUGWgSAAoJELyJZYjffCjuEmwP/1jKJH4tZeHLB4LG1+Yotg5b YDS/VttiH8xCstlOSx+rq9VefJlzzmCaXTC1C9+yJZciyPhRM4P9J1NVaJmh4OcK qoVEJFe7zrnlCHj+348ZSOJ5mInRVzS/idMRuu+vtvAObpQVNS8/AAq0mgrQfjXS 7cjmb9JF7HJN7IKm3A9Zxx047RwIn/dzBjFhr36D9H0Crf1scN46hzWpVSciYuVF coNqbePjz1vq4bYjAYqjsKtNDQ5wo4sCHREKlon9YwzKxsuwovrwSgDYQIG0NSgL srKdDPmT9Lwi4i4HBba65nf7X4PgyiwbzjCmq7fTbYnDyQ/az5C2kE5Gqow1UEpB B0xgawkak2Ta9fSegNErykaZhL4OPUf0ug9T8hRGheDm8dkQvAG/jf7Z8kfh7lBk GggrYK4Fw1t05QRMQLGQ9Wem89r4r5+p2udxMAbm8NoiFn0xG2cMQj3Tjx6Py/Ao Cd6+YsKSgRMI0pgRb/vT5YbArZpuXJ112PryMyzkAwAs/bK0fyR6mDG+61gE3mvV /EXbvHWhWor1jfR3RXl2g15pbdY5TnJMvkrjqs1Ie5gvDybfcdwfS+NHClm/iIzP GKOykdscjfEw99Fzw10lwBZdcRTH8Kd8MCRQY+73uA776lIb+6EbrwahIxOW2O0l UGpbvb00yu8Fg+b+wikQ =TPqs -----END PGP SIGNATURE----- _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Sep 17 14:20:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 14:20:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUG5k-00046D-GU; Wed, 17 Sep 2014 14:20:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUG5j-000465-4T for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 14:20:19 +0000 Received: from [85.158.143.35:8103] by server-1.bemta-4.messagelabs.com id 8B/BF-05872-2A899145; Wed, 17 Sep 2014 14:20:18 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1410963617!13667976!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5685 invoked from network); 17 Sep 2014 14:20:17 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 14:20:17 -0000 Received: from [192.168.14.104] (no-dns-yet.demon.co.uk [62.49.66.12]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id e69a2e5c; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 17 Sep 2014 15:21:03 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <54196812.5080701@mehnert.org> Date: Wed, 17 Sep 2014 15:20:12 +0100 Message-Id: References: <54196812.5080701@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1878.6) Cc: david , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OCaml-TLS directly on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 Sep 2014, at 11:53, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hey, > > I demonstrated that OCaml-TLS runs directly on Xen at the OCaml > workshop. The port is still a bit hackish, thus I hope to get some > feedback (esp. regarding what features (such as FORTIFY_SOURCE stack > protection, and/or assert (should minios provide an assert_fail > symbol?)) we want to compile our C code with, and how to upstream > these changes properly). > > I develop on a cubieboard2, where I pinned mirage > (44bd28f862549aa1f149421c1e515bb3703e40d7), mirage-xen > (0251870f14030315b00ffdd0cd0112d8788270a1) and tcpip > (05148f900352eabaa615b60d5b2fb518f5518edd) to git HEAD (as well as > x509/asn1-combinators/nocrypto/tls). > Very nice indeed! > Several libraries needed to be modified to run in the Xen environment: > > minios > - ------ > > https://github.com/hannesm/xen/tree/tls-fixes > some symbols are required for the various C libraries below, namely: > abort (calling do_exit) Adding this to MiniOS should be fine (waiting for Thomas Leonard to return from vacation). > __stack_chk_guard (being NULL) Is this really essential -- it's inserted by the gcc stack smash checker isn't it? Should be no harm in putting it into MiniOS, but I'd prefer understanding if it'll cause problems if (e.g.) clang is used to build the toolchain as well. > fprintf/printf/stdout/stderr/fflush (for gmp and zarith) I'd definitely prefer to have these in a separate 'nanolibc' separate from MiniOS itself. I believe James Bielman could also use such a shim library to compile libselinux as well. > > gmp (the GNU multi-precision arithmetic library) > - ------------------------------------------------ > > Configure (esp. config.guess) gets confused by an arm dualcore: > http://berlin.ccc.de/~hannes/gmp-6a.diff fixes this. > > I used the following CFLAGS: > export CFLAGS="-marm -O2 -pedantic -fomit-frame-pointer -fno-builtin > - -D_FORTIFY_SOURCE=0" > ./configure > make This is possibly worth folding in to be compiled statically (as a separate library) in the mirage-minios-xen repository (which is turning into our aggregation-of-libraries-repo). > > zarith > - ------ > > Due to subtle differences of GNU libm and openlibm (esp isinf/isnan is > rewritten in the GNU version to __isinf/__isnan), I modified caml_z.c > to #include instead of (should openlibm instead > install its header file as math.h!?) > > Patch at http://berlin.ccc.de/~hannes/zarith.diff > > I additionally pointed zarith to my custom gmp library: > export CPPFLAGS="-I/home/mirage/gmp-6.0.0.orig > - -I/home/mirage/.opam/system/include" > export LDFLAGS="-L/home/mirage/gmp-6.0.0.orig/.libs" > > (the previously mentioned CFLAGS are also still active!) Deferring to Thomas on this one... > > ctypes (0.3.3) > - -------------- > > nocrypto (from git) depends on ctypes, which needed some CFLAGS (to > avoid assert_fail being called (-DNDEBUG), sscanf being translated to > __isoc99_sscanf (-D_GNU_SOURCE)), patch > http://berlin.ccc.de/~hannes/ctypes.diff > This definition of GNU_SOURCE worries me -- is it happening because of a mismatch of header files somewhere in the compilation of the C library? It shouldn't be necessary to define it in the normal course of operation of ctypes. > nocrypto > - -------- > > https://github.com/mirleft/ocaml-nocrypto/tree/xen-fixes (adds -DNDEBUG) Likewise, we should be able to define assert_fail in MiniOS I think, as this is a fairly widely used header defined in SUS. > tls > - --- > > https://github.com/mirleft/ocaml-tls/tree/xen-fixes (use Io_page > aligned cstructs before transmitting) Misaligned Cstructs strike again... :-) > > > Once these libraries are patched, the minimum TLS server > https://github.com/mirleft/tls-mvp-server/tree/fixes works (with > export NET="direct" and s/-unix/-xen/ (mirage-clock-xen, > mirage-entropy-xen) in config.ml), and some minor modifications to the > Makefile to link in the right gmp/minios/... Awesome! Thomas Gazagnaire is looking at the Conduit patches right now, which should provide the right place to hook the TLS stack into Cohttp and friends. -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 Sep 17 14:20:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 17 Sep 2014 14:20:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUG5k-00046D-GU; Wed, 17 Sep 2014 14:20:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUG5j-000465-4T for mirageos-devel@lists.xenproject.org; Wed, 17 Sep 2014 14:20:19 +0000 Received: from [85.158.143.35:8103] by server-1.bemta-4.messagelabs.com id 8B/BF-05872-2A899145; Wed, 17 Sep 2014 14:20:18 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-21.messagelabs.com!1410963617!13667976!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5685 invoked from network); 17 Sep 2014 14:20:17 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-6.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Sep 2014 14:20:17 -0000 Received: from [192.168.14.104] (no-dns-yet.demon.co.uk [62.49.66.12]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id e69a2e5c; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Wed, 17 Sep 2014 15:21:03 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <54196812.5080701@mehnert.org> Date: Wed, 17 Sep 2014 15:20:12 +0100 Message-Id: References: <54196812.5080701@mehnert.org> To: Hannes Mehnert X-Mailer: Apple Mail (2.1878.6) Cc: david , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OCaml-TLS directly on Xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 Sep 2014, at 11:53, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hey, > > I demonstrated that OCaml-TLS runs directly on Xen at the OCaml > workshop. The port is still a bit hackish, thus I hope to get some > feedback (esp. regarding what features (such as FORTIFY_SOURCE stack > protection, and/or assert (should minios provide an assert_fail > symbol?)) we want to compile our C code with, and how to upstream > these changes properly). > > I develop on a cubieboard2, where I pinned mirage > (44bd28f862549aa1f149421c1e515bb3703e40d7), mirage-xen > (0251870f14030315b00ffdd0cd0112d8788270a1) and tcpip > (05148f900352eabaa615b60d5b2fb518f5518edd) to git HEAD (as well as > x509/asn1-combinators/nocrypto/tls). > Very nice indeed! > Several libraries needed to be modified to run in the Xen environment: > > minios > - ------ > > https://github.com/hannesm/xen/tree/tls-fixes > some symbols are required for the various C libraries below, namely: > abort (calling do_exit) Adding this to MiniOS should be fine (waiting for Thomas Leonard to return from vacation). > __stack_chk_guard (being NULL) Is this really essential -- it's inserted by the gcc stack smash checker isn't it? Should be no harm in putting it into MiniOS, but I'd prefer understanding if it'll cause problems if (e.g.) clang is used to build the toolchain as well. > fprintf/printf/stdout/stderr/fflush (for gmp and zarith) I'd definitely prefer to have these in a separate 'nanolibc' separate from MiniOS itself. I believe James Bielman could also use such a shim library to compile libselinux as well. > > gmp (the GNU multi-precision arithmetic library) > - ------------------------------------------------ > > Configure (esp. config.guess) gets confused by an arm dualcore: > http://berlin.ccc.de/~hannes/gmp-6a.diff fixes this. > > I used the following CFLAGS: > export CFLAGS="-marm -O2 -pedantic -fomit-frame-pointer -fno-builtin > - -D_FORTIFY_SOURCE=0" > ./configure > make This is possibly worth folding in to be compiled statically (as a separate library) in the mirage-minios-xen repository (which is turning into our aggregation-of-libraries-repo). > > zarith > - ------ > > Due to subtle differences of GNU libm and openlibm (esp isinf/isnan is > rewritten in the GNU version to __isinf/__isnan), I modified caml_z.c > to #include instead of (should openlibm instead > install its header file as math.h!?) > > Patch at http://berlin.ccc.de/~hannes/zarith.diff > > I additionally pointed zarith to my custom gmp library: > export CPPFLAGS="-I/home/mirage/gmp-6.0.0.orig > - -I/home/mirage/.opam/system/include" > export LDFLAGS="-L/home/mirage/gmp-6.0.0.orig/.libs" > > (the previously mentioned CFLAGS are also still active!) Deferring to Thomas on this one... > > ctypes (0.3.3) > - -------------- > > nocrypto (from git) depends on ctypes, which needed some CFLAGS (to > avoid assert_fail being called (-DNDEBUG), sscanf being translated to > __isoc99_sscanf (-D_GNU_SOURCE)), patch > http://berlin.ccc.de/~hannes/ctypes.diff > This definition of GNU_SOURCE worries me -- is it happening because of a mismatch of header files somewhere in the compilation of the C library? It shouldn't be necessary to define it in the normal course of operation of ctypes. > nocrypto > - -------- > > https://github.com/mirleft/ocaml-nocrypto/tree/xen-fixes (adds -DNDEBUG) Likewise, we should be able to define assert_fail in MiniOS I think, as this is a fairly widely used header defined in SUS. > tls > - --- > > https://github.com/mirleft/ocaml-tls/tree/xen-fixes (use Io_page > aligned cstructs before transmitting) Misaligned Cstructs strike again... :-) > > > Once these libraries are patched, the minimum TLS server > https://github.com/mirleft/tls-mvp-server/tree/fixes works (with > export NET="direct" and s/-unix/-xen/ (mirage-clock-xen, > mirage-entropy-xen) in config.ml), and some minor modifications to the > Makefile to link in the right gmp/minios/... Awesome! Thomas Gazagnaire is looking at the Conduit patches right now, which should provide the right place to hook the TLS stack into Cohttp and friends. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 01:15:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 01:15: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 1XUQJJ-00051B-Bw; Thu, 18 Sep 2014 01:15:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUQJH-000516-Pu for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 01:14:59 +0000 Received: from [85.158.143.35:59656] by server-2.bemta-4.messagelabs.com id A4/CC-04525-3123A145; Thu, 18 Sep 2014 01:14:59 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1411002896!10124756!1 X-Originating-IP: [209.85.220.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8258 invoked from network); 18 Sep 2014 01:14:58 -0000 Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2014 01:14:58 -0000 Received: by mail-pa0-f48.google.com with SMTP id hz1so273557pad.21 for ; Wed, 17 Sep 2014 18:14:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=9A+sjYY2OBlKjCCr/bjFkIVPeRotFZxLVXxZ0toAC4Y=; b=jUbzAH2SBxoW4cKZT5nXLDkyVC68f5BOb9qYmi7bFYVem3mLWYOMPrWAz/MPazYSRU Cb/DpmvXF5dxZ5CsWvpD3nIAEROj/0m+kASABLDmUhFRfNWw4KzO6QiSMJcCrofivtF8 ozTL3Y/KQnEjgX6QgCscudyV/TC29X/hziFDdZ6KbPdZZDFmQY56TYyqsLpUJI5hPngO OZIR/qTJMhunwa3uXQwO3VXUkcHaZkFxc7SRwc63TC1DWTRkHiCdH+9cGhp7G+94a6r/ j2+8leXzvzRM4yjSwm202K8kW6TVOBrpyj39yM50V08Zlc5U/8oT/u7RrA9rwMyV+O6j 9Wpw== X-Received: by 10.66.152.109 with SMTP id ux13mr1125636pab.122.1411002894997; Wed, 17 Sep 2014 18:14:54 -0700 (PDT) Received: from [10.10.4.194] ([64.196.190.2]) by mx.google.com with ESMTPSA id yh3sm18045463pbb.38.2014.09.17.18.14.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Sep 2014 18:14:54 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <0A5E6666-E532-4C0B-A72E-ECD4AB1113EA@gmail.com> Date: Wed, 17 Sep 2014 18:14:48 -0700 Message-Id: <543FD593-E1C5-4782-AC7C-7C3B5A3CCD6B@gmail.com> References: <0A5E6666-E532-4C0B-A72E-ECD4AB1113EA@gmail.com> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] Location of next Xen Project Developer Summit / User Summit (please respond by end of September) X-BeenThere: mirageos-devel@lists.xenproject.org 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 Resending On 17 Sep 2014, at 17:30, Lars Kurth wrote: > Hi all, > = > I am CC=92ing all the subprojects (and project leads of sub projects who = are not yet fully operational in terms of infrastructure) to get feedback o= n next years events. I know we all agreed that we would alternate between E= urope and the US, but this may be challenging next year, because there may = not be enough space. So I wanted to get your feed and will need to make a d= ecision before the next Advisory Board meeting in October. Ideally well bef= ore. > = > Let me lay out what I know. > * LinuxCon US will be in Seattle Aug 17-19 > * Linux Plumbers will be in Seattle Aug 19, with mini summits Aug 20 & 21= st > * There will also be a new Container Con Aug 20 & 21st > * KVM Forum is thinking but have not decided to be in Seattle also someti= mes between Aug 19 - 21st > * There is just enough space for a Xen Project Summit from Aug 19 - 21st = > * LinuxCon EU is most likely in Brussels end of September, but it is like= ly that there is not enough space > = > I also want to move back to a model where we don=92t have a separate user= and developer summit. It is to expensive and too hard to organise. What we= would do is have these semi-separate (e.g. User Summit before the Dev Summ= it) and we allow users to stay on and attend the Dev Summit using some disc= ounted tickets if they want. The main rationale is to save cost and get max= imum impact from sponsorships to subsidise the event(s). > = > But we need to make a decision pretty soon. My thinking was the following: > * Developer Summit on 20 & 21st > * Developer Meeting, Board Meetings, Hackspace and Working Group would be= held on the 19th. = > * We could also have a User Focussed Day on the 19th - the limitation is = that on the 19th we cannot get rooms holding more than 60 people > * Try to do something together with KVM Forum (E.g. a joint social event = or something - assuming they buy into it and decide for Seattle, or a joint= Hackathon) > * The problem is that this would be a very intensive week and that some p= eople may have to juggle schedules as they may have to attend several event= s. > = > On the other hand, there is likely not enough space to co-locate with Lin= uxCon EU. And we always also have a very big presence at FOSDEM in Brussels= . So co-locating seems not quite right, as we are almost competing with our= selves in the same location that year. > = > Please let me know what your preferences are. I can then get back to the = Advisory Board and get this closed. And I need to know before the end of th= e month as otherwise we will run out of options. > = > Best Regards > Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 01:15:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 01:15: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 1XUQJJ-00051B-Bw; Thu, 18 Sep 2014 01:15:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUQJH-000516-Pu for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 01:14:59 +0000 Received: from [85.158.143.35:59656] by server-2.bemta-4.messagelabs.com id A4/CC-04525-3123A145; Thu, 18 Sep 2014 01:14:59 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1411002896!10124756!1 X-Originating-IP: [209.85.220.48] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8258 invoked from network); 18 Sep 2014 01:14:58 -0000 Received: from mail-pa0-f48.google.com (HELO mail-pa0-f48.google.com) (209.85.220.48) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Sep 2014 01:14:58 -0000 Received: by mail-pa0-f48.google.com with SMTP id hz1so273557pad.21 for ; Wed, 17 Sep 2014 18:14:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=9A+sjYY2OBlKjCCr/bjFkIVPeRotFZxLVXxZ0toAC4Y=; b=jUbzAH2SBxoW4cKZT5nXLDkyVC68f5BOb9qYmi7bFYVem3mLWYOMPrWAz/MPazYSRU Cb/DpmvXF5dxZ5CsWvpD3nIAEROj/0m+kASABLDmUhFRfNWw4KzO6QiSMJcCrofivtF8 ozTL3Y/KQnEjgX6QgCscudyV/TC29X/hziFDdZ6KbPdZZDFmQY56TYyqsLpUJI5hPngO OZIR/qTJMhunwa3uXQwO3VXUkcHaZkFxc7SRwc63TC1DWTRkHiCdH+9cGhp7G+94a6r/ j2+8leXzvzRM4yjSwm202K8kW6TVOBrpyj39yM50V08Zlc5U/8oT/u7RrA9rwMyV+O6j 9Wpw== X-Received: by 10.66.152.109 with SMTP id ux13mr1125636pab.122.1411002894997; Wed, 17 Sep 2014 18:14:54 -0700 (PDT) Received: from [10.10.4.194] ([64.196.190.2]) by mx.google.com with ESMTPSA id yh3sm18045463pbb.38.2014.09.17.18.14.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Sep 2014 18:14:54 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Lars Kurth In-Reply-To: <0A5E6666-E532-4C0B-A72E-ECD4AB1113EA@gmail.com> Date: Wed, 17 Sep 2014 18:14:48 -0700 Message-Id: <543FD593-E1C5-4782-AC7C-7C3B5A3CCD6B@gmail.com> References: <0A5E6666-E532-4C0B-A72E-ECD4AB1113EA@gmail.com> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] Location of next Xen Project Developer Summit / User Summit (please respond by end of September) X-BeenThere: mirageos-devel@lists.xenproject.org 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 Resending On 17 Sep 2014, at 17:30, Lars Kurth wrote: > Hi all, > = > I am CC=92ing all the subprojects (and project leads of sub projects who = are not yet fully operational in terms of infrastructure) to get feedback o= n next years events. I know we all agreed that we would alternate between E= urope and the US, but this may be challenging next year, because there may = not be enough space. So I wanted to get your feed and will need to make a d= ecision before the next Advisory Board meeting in October. Ideally well bef= ore. > = > Let me lay out what I know. > * LinuxCon US will be in Seattle Aug 17-19 > * Linux Plumbers will be in Seattle Aug 19, with mini summits Aug 20 & 21= st > * There will also be a new Container Con Aug 20 & 21st > * KVM Forum is thinking but have not decided to be in Seattle also someti= mes between Aug 19 - 21st > * There is just enough space for a Xen Project Summit from Aug 19 - 21st = > * LinuxCon EU is most likely in Brussels end of September, but it is like= ly that there is not enough space > = > I also want to move back to a model where we don=92t have a separate user= and developer summit. It is to expensive and too hard to organise. What we= would do is have these semi-separate (e.g. User Summit before the Dev Summ= it) and we allow users to stay on and attend the Dev Summit using some disc= ounted tickets if they want. The main rationale is to save cost and get max= imum impact from sponsorships to subsidise the event(s). > = > But we need to make a decision pretty soon. My thinking was the following: > * Developer Summit on 20 & 21st > * Developer Meeting, Board Meetings, Hackspace and Working Group would be= held on the 19th. = > * We could also have a User Focussed Day on the 19th - the limitation is = that on the 19th we cannot get rooms holding more than 60 people > * Try to do something together with KVM Forum (E.g. a joint social event = or something - assuming they buy into it and decide for Seattle, or a joint= Hackathon) > * The problem is that this would be a very intensive week and that some p= eople may have to juggle schedules as they may have to attend several event= s. > = > On the other hand, there is likely not enough space to co-locate with Lin= uxCon EU. And we always also have a very big presence at FOSDEM in Brussels= . So co-locating seems not quite right, as we are almost competing with our= selves in the same location that year. > = > Please let me know what your preferences are. I can then get back to the = Advisory Board and get this closed. And I need to know before the end of th= e month as otherwise we will run out of options. > = > Best Regards > Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 08:29:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 08:29: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 1XUX5d-0004Ia-UT; Thu, 18 Sep 2014 08:29:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUX5c-0004IR-PJ for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 08:29:21 +0000 Received: from [85.158.137.68:61203] by server-3.bemta-3.messagelabs.com id C5/4F-22751-FD79A145; Thu, 18 Sep 2014 08:29:19 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-6.tower-31.messagelabs.com!1411028958!10776164!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5885 invoked from network); 18 Sep 2014 08:29:18 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-6.tower-31.messagelabs.com with SMTP; 18 Sep 2014 08:29:18 -0000 Received: (qmail 19696 invoked from network); 18 Sep 2014 08:28:08 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 18 Sep 2014 08:28:08 -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 18804-03 for ; Thu, 18 Sep 2014 09:28:01 +0100 (BST) Received: (qmail 19571 invoked by uid 599); 18 Sep 2014 08:28:01 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 09:28:01 +0100 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 1XUX4K-0003V3-Bp; Thu, 18 Sep 2014 09:28:00 +0100 From: Richard Mortier To: Lars Kurth Date: Thu, 18 Sep 2014 09:27:58 +0100 Thread-Topic: [MirageOS-devel] Location of next Xen Project Developer Summit / User Summit (please respond by end of September) Thread-Index: Ac/TGnRWnj2Xk1naSxiHQkQMaXmYtw== Message-ID: <264F5E6A-84E4-45FC-B2B0-DFECB2ED9BEC@nottingham.ac.uk> References: <0A5E6666-E532-4C0B-A72E-ECD4AB1113EA@gmail.com> <543FD593-E1C5-4782-AC7C-7C3B5A3CCD6B@gmail.com> In-Reply-To: <543FD593-E1C5-4782-AC7C-7C3B5A3CCD6B@gmail.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Location of next Xen Project Developer Summit / User Summit (please respond by end of September) X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7054907674064616390==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7054907674064616390== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 i'm coming into this late, i don't know how relevant the experience is, = and i don't really have a feel for the scale or intent of these events = so apologies if this is noise but fwiw: many (most?) "large" (300-700 attendees) academic cs conferences now run = to ~5 days rather than the more traditional ~2.5. this allows for = collocated co-sponsored workshops to be tacked on at the start and/or = end. some of the larger conferences (around, say, 3000 attendees) go = multi-track with workshops spread over the entire timetable. both = approaches seem fairly successful-- though some attendees are very = selective about what they register for, numbers generally seem to hold = up well across the entire week (much better than at, eg., oscon, where = we've observed dramatically fewer people there on the last day). ticket = prices are usually discounted based on some combination of registering = early, having ACM/IEEE membership, and (sometimes) number of events = attended. so i guess i'd say +1 to something like having several related events = consecutively with some affiliation between them. amortising travel time = is good. i think this is roughly what you're suggesting. re fosdem (or colocation generally)-- what would you want to do there? = would it make sense to have a session or a track or a = pre-/post-main-event? would being cosponsored (vs just collocating) = with fosdem be something that would be useful? On 18 Sep 2014, at 02:14, Lars Kurth wrote: > Resending >=20 > On 17 Sep 2014, at 17:30, Lars Kurth wrote: >=20 >> Hi all, >>=20 >> I am CC=92ing all the subprojects (and project leads of sub projects = who are not yet fully operational in terms of infrastructure) to get = feedback on next years events. I know we all agreed that we would = alternate between Europe and the US, but this may be challenging next = year, because there may not be enough space. So I wanted to get your = feed and will need to make a decision before the next Advisory Board = meeting in October. Ideally well before. >>=20 >> Let me lay out what I know. >> * LinuxCon US will be in Seattle Aug 17-19 >> * Linux Plumbers will be in Seattle Aug 19, with mini summits Aug 20 = & 21st >> * There will also be a new Container Con Aug 20 & 21st >> * KVM Forum is thinking but have not decided to be in Seattle also = sometimes between Aug 19 - 21st >> * There is just enough space for a Xen Project Summit from Aug 19 - = 21st=20 >> * LinuxCon EU is most likely in Brussels end of September, but it is = likely that there is not enough space >>=20 >> I also want to move back to a model where we don=92t have a separate = user and developer summit. It is to expensive and too hard to organise. = What we would do is have these semi-separate (e.g. User Summit before = the Dev Summit) and we allow users to stay on and attend the Dev Summit = using some discounted tickets if they want. The main rationale is to = save cost and get maximum impact from sponsorships to subsidise the = event(s). >>=20 >> But we need to make a decision pretty soon. My thinking was the = following: >> * Developer Summit on 20 & 21st >> * Developer Meeting, Board Meetings, Hackspace and Working Group = would be held on the 19th.=20 >> * We could also have a User Focussed Day on the 19th - the limitation = is that on the 19th we cannot get rooms holding more than 60 people >> * Try to do something together with KVM Forum (E.g. a joint social = event or something - assuming they buy into it and decide for Seattle, = or a joint Hackathon) >> * The problem is that this would be a very intensive week and that = some people may have to juggle schedules as they may have to attend = several events. >>=20 >> On the other hand, there is likely not enough space to co-locate with = LinuxCon EU. And we always also have a very big presence at FOSDEM in = Brussels. So co-locating seems not quite right, as we are almost = competing with ourselves in the same location that year. >>=20 >> Please let me know what your preferences are. I can then get back to = the Advisory Board and get this closed. And I need to know before the = end of the month as otherwise we will run out of options. >>=20 >> Best Regards >> Lars >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --=20 Cheers, R. --Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUGpeOAAoJEOLF27JWwSg3HNQP/jFW4v/7SYFng0+zW/ocoZDg KktYTkxSeKnkxr3mJ2XcLOe+nTDjvy0roN+K6UJG+lh9Jue04Z1f/Fl+bh+fkXhf UKVHmwoSDhp9wtIzq5HjNBlO0GOyFlx/vDYWO3iqAAP3zEWnboFrnF3vbNDE5257 cSfDaYPLf/JVqcPrxftI1RH6nQUR9Tf8ykK56pt/7gkTmI2E1qwKTwIyIiRHejvy 8xs5KD1dOkD3/QYWyYp+DH8rdqLkReJhRBCp8lL8Qt9D+8hBYiBMstHQWWFKuYLB dkzD2P0wlZ6HqNu+7MTMkwCoYFG6B2asnub5WU/AvTGuPWMVwLcwrL/DSwuzfLI6 ql2Ujxlm0HcksaRWwoe+p153nbGTOWmFpyngU1ntdsrpBWF+GJu9n8d/z79FKQ7A CeA9kSIF7m6c0rDuG+ZGgALZADciz/nWRoSC355IOTWChiw6gWLZHUSagsdg4nNn iBHrzwCjRIHr9v+lbvBJgggXV7G1gR7PsmkPaEWcXEq6zbY3Y2ur2KVY2SfOIrX3 3FHFt2mgQpzBCngKGCB3oFemqrzmNA/P3Z6ZfjGxRBOoaCyDFTPK4njckk6Xo+ZS Db8toehW8UeqLqg2eJtVmEoymRZLDOtxHqXwG3cp2NYM2ExgXYPyY5DOYJadRvJT ZlHQ9AIJiR0y8dlOm0a6 =e6nk -----END PGP SIGNATURE----- --Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE-- --===============7054907674064616390== 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 --===============7054907674064616390==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 08:29:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 08:29: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 1XUX5d-0004Ia-UT; Thu, 18 Sep 2014 08:29:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUX5c-0004IR-PJ for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 08:29:21 +0000 Received: from [85.158.137.68:61203] by server-3.bemta-3.messagelabs.com id C5/4F-22751-FD79A145; Thu, 18 Sep 2014 08:29:19 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-6.tower-31.messagelabs.com!1411028958!10776164!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5885 invoked from network); 18 Sep 2014 08:29:18 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-6.tower-31.messagelabs.com with SMTP; 18 Sep 2014 08:29:18 -0000 Received: (qmail 19696 invoked from network); 18 Sep 2014 08:28:08 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 18 Sep 2014 08:28:08 -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 18804-03 for ; Thu, 18 Sep 2014 09:28:01 +0100 (BST) Received: (qmail 19571 invoked by uid 599); 18 Sep 2014 08:28:01 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 09:28:01 +0100 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 1XUX4K-0003V3-Bp; Thu, 18 Sep 2014 09:28:00 +0100 From: Richard Mortier To: Lars Kurth Date: Thu, 18 Sep 2014 09:27:58 +0100 Thread-Topic: [MirageOS-devel] Location of next Xen Project Developer Summit / User Summit (please respond by end of September) Thread-Index: Ac/TGnRWnj2Xk1naSxiHQkQMaXmYtw== Message-ID: <264F5E6A-84E4-45FC-B2B0-DFECB2ED9BEC@nottingham.ac.uk> References: <0A5E6666-E532-4C0B-A72E-ECD4AB1113EA@gmail.com> <543FD593-E1C5-4782-AC7C-7C3B5A3CCD6B@gmail.com> In-Reply-To: <543FD593-E1C5-4782-AC7C-7C3B5A3CCD6B@gmail.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Location of next Xen Project Developer Summit / User Summit (please respond by end of September) X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7054907674064616390==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7054907674064616390== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 i'm coming into this late, i don't know how relevant the experience is, = and i don't really have a feel for the scale or intent of these events = so apologies if this is noise but fwiw: many (most?) "large" (300-700 attendees) academic cs conferences now run = to ~5 days rather than the more traditional ~2.5. this allows for = collocated co-sponsored workshops to be tacked on at the start and/or = end. some of the larger conferences (around, say, 3000 attendees) go = multi-track with workshops spread over the entire timetable. both = approaches seem fairly successful-- though some attendees are very = selective about what they register for, numbers generally seem to hold = up well across the entire week (much better than at, eg., oscon, where = we've observed dramatically fewer people there on the last day). ticket = prices are usually discounted based on some combination of registering = early, having ACM/IEEE membership, and (sometimes) number of events = attended. so i guess i'd say +1 to something like having several related events = consecutively with some affiliation between them. amortising travel time = is good. i think this is roughly what you're suggesting. re fosdem (or colocation generally)-- what would you want to do there? = would it make sense to have a session or a track or a = pre-/post-main-event? would being cosponsored (vs just collocating) = with fosdem be something that would be useful? On 18 Sep 2014, at 02:14, Lars Kurth wrote: > Resending >=20 > On 17 Sep 2014, at 17:30, Lars Kurth wrote: >=20 >> Hi all, >>=20 >> I am CC=92ing all the subprojects (and project leads of sub projects = who are not yet fully operational in terms of infrastructure) to get = feedback on next years events. I know we all agreed that we would = alternate between Europe and the US, but this may be challenging next = year, because there may not be enough space. So I wanted to get your = feed and will need to make a decision before the next Advisory Board = meeting in October. Ideally well before. >>=20 >> Let me lay out what I know. >> * LinuxCon US will be in Seattle Aug 17-19 >> * Linux Plumbers will be in Seattle Aug 19, with mini summits Aug 20 = & 21st >> * There will also be a new Container Con Aug 20 & 21st >> * KVM Forum is thinking but have not decided to be in Seattle also = sometimes between Aug 19 - 21st >> * There is just enough space for a Xen Project Summit from Aug 19 - = 21st=20 >> * LinuxCon EU is most likely in Brussels end of September, but it is = likely that there is not enough space >>=20 >> I also want to move back to a model where we don=92t have a separate = user and developer summit. It is to expensive and too hard to organise. = What we would do is have these semi-separate (e.g. User Summit before = the Dev Summit) and we allow users to stay on and attend the Dev Summit = using some discounted tickets if they want. The main rationale is to = save cost and get maximum impact from sponsorships to subsidise the = event(s). >>=20 >> But we need to make a decision pretty soon. My thinking was the = following: >> * Developer Summit on 20 & 21st >> * Developer Meeting, Board Meetings, Hackspace and Working Group = would be held on the 19th.=20 >> * We could also have a User Focussed Day on the 19th - the limitation = is that on the 19th we cannot get rooms holding more than 60 people >> * Try to do something together with KVM Forum (E.g. a joint social = event or something - assuming they buy into it and decide for Seattle, = or a joint Hackathon) >> * The problem is that this would be a very intensive week and that = some people may have to juggle schedules as they may have to attend = several events. >>=20 >> On the other hand, there is likely not enough space to co-locate with = LinuxCon EU. And we always also have a very big presence at FOSDEM in = Brussels. So co-locating seems not quite right, as we are almost = competing with ourselves in the same location that year. >>=20 >> Please let me know what your preferences are. I can then get back to = the Advisory Board and get this closed. And I need to know before the = end of the month as otherwise we will run out of options. >>=20 >> Best Regards >> Lars >=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --=20 Cheers, R. --Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUGpeOAAoJEOLF27JWwSg3HNQP/jFW4v/7SYFng0+zW/ocoZDg KktYTkxSeKnkxr3mJ2XcLOe+nTDjvy0roN+K6UJG+lh9Jue04Z1f/Fl+bh+fkXhf UKVHmwoSDhp9wtIzq5HjNBlO0GOyFlx/vDYWO3iqAAP3zEWnboFrnF3vbNDE5257 cSfDaYPLf/JVqcPrxftI1RH6nQUR9Tf8ykK56pt/7gkTmI2E1qwKTwIyIiRHejvy 8xs5KD1dOkD3/QYWyYp+DH8rdqLkReJhRBCp8lL8Qt9D+8hBYiBMstHQWWFKuYLB dkzD2P0wlZ6HqNu+7MTMkwCoYFG6B2asnub5WU/AvTGuPWMVwLcwrL/DSwuzfLI6 ql2Ujxlm0HcksaRWwoe+p153nbGTOWmFpyngU1ntdsrpBWF+GJu9n8d/z79FKQ7A CeA9kSIF7m6c0rDuG+ZGgALZADciz/nWRoSC355IOTWChiw6gWLZHUSagsdg4nNn iBHrzwCjRIHr9v+lbvBJgggXV7G1gR7PsmkPaEWcXEq6zbY3Y2ur2KVY2SfOIrX3 3FHFt2mgQpzBCngKGCB3oFemqrzmNA/P3Z6ZfjGxRBOoaCyDFTPK4njckk6Xo+ZS Db8toehW8UeqLqg2eJtVmEoymRZLDOtxHqXwG3cp2NYM2ExgXYPyY5DOYJadRvJT ZlHQ9AIJiR0y8dlOm0a6 =e6nk -----END PGP SIGNATURE----- --Apple-Mail=_0F342706-6A44-4876-91DC-FA3D64214EBE-- --===============7054907674064616390== 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 --===============7054907674064616390==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 21:38:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 21:38: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 1XUjP3-00034v-6G; Thu, 18 Sep 2014 21:38:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUjP1-00034q-RT for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 21:38:11 +0000 Received: from [193.109.254.147:23934] by server-10.bemta-14.messagelabs.com id 42/26-01463-2C05B145; Thu, 18 Sep 2014 21:38:10 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1411076290!16503993!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20167 invoked from network); 18 Sep 2014 21:38:10 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2014 21:38:10 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id d8dfddf6; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; for ; Thu, 18 Sep 2014 22:39:00 +0100 (BST) From: Anil Madhavapeddy Message-Id: Date: Thu, 18 Sep 2014 22:38:06 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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 ported the trunks of mirage-skeleton and mirage-www to use the Mirage 2 development repositories, since most of us are using the latest libraries in order to test them for release anyway. To build mirage-skeleton/mirage-www, you will now need to: opam remote add mirage git://github.com/mirage/mirage-dev opam update -u This will get you the latest and great libraries from the git master branches of the respective packages. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 21:38:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 21:38: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 1XUjP3-00034v-6G; Thu, 18 Sep 2014 21:38:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUjP1-00034q-RT for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 21:38:11 +0000 Received: from [193.109.254.147:23934] by server-10.bemta-14.messagelabs.com id 42/26-01463-2C05B145; Thu, 18 Sep 2014 21:38:10 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1411076290!16503993!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20167 invoked from network); 18 Sep 2014 21:38:10 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2014 21:38:10 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id d8dfddf6; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; for ; Thu, 18 Sep 2014 22:39:00 +0100 (BST) From: Anil Madhavapeddy Message-Id: Date: Thu, 18 Sep 2014 22:38:06 +0100 To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Subject: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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 ported the trunks of mirage-skeleton and mirage-www to use the Mirage 2 development repositories, since most of us are using the latest libraries in order to test them for release anyway. To build mirage-skeleton/mirage-www, you will now need to: opam remote add mirage git://github.com/mirage/mirage-dev opam update -u This will get you the latest and great libraries from the git master branches of the respective packages. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:21:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:21:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUk4b-000536-UT; Thu, 18 Sep 2014 22:21:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUk4a-000530-Qz for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:21:08 +0000 Received: from [85.158.137.68:40382] by server-11.bemta-3.messagelabs.com id 86/30-01568-3DA5B145; Thu, 18 Sep 2014 22:21:07 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1411078866!12600472!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3116 invoked from network); 18 Sep 2014 22:21:07 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-10.tower-31.messagelabs.com with SMTP; 18 Sep 2014 22:21:07 -0000 Received: (qmail 9857 invoked from network); 18 Sep 2014 22:21:04 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 18 Sep 2014 22:21:04 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 04258-05 for ; Thu, 18 Sep 2014 23:20:57 +0100 (BST) Received: (qmail 9788 invoked by uid 599); 18 Sep 2014 22:20:57 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 23:20:57 +0100 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 1XUk4Q-0006nr-Cv; Thu, 18 Sep 2014 23:20:58 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 18 Sep 2014 23:20:56 +0100 Thread-Topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos Thread-Index: Ac/TjtF7RHJYrPY5RdqdmskZagZZLA== Message-ID: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7039686314138284078==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7039686314138284078== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Sep 2014, at 22:38, Anil Madhavapeddy wrote: > I've ported the trunks of mirage-skeleton and mirage-www to use the = Mirage 2 development repositories, since most of us are using the latest = libraries in order to test them for release anyway. >=20 > To build mirage-skeleton/mirage-www, you will now need to: >=20 > opam remote add mirage git://github.com/mirage/mirage-dev > opam update -u fwiw just tried that and ended up at=20 ... mirage-www.1.2.0 Fetching git://github.com/mirage/mirage-www The following DEV package needs to be upgraded: - mirage-www.1.2.0 Updating the cache of metadata (~/.opam/state.cache) ... 0 to install | 103 to reinstall | 14 to upgrade | 1 to downgrade | 0 to = remove You can now run 'opam upgrade' to upgrade your system. [WARNING] External solver failed with inconsistent return value. Request = saved to "/Users/mort/.opam/log/solver-error-33616-1.cudf" Falling back to the internal heuristic. ...at which point i killed it. is this expected, or worth filing an opam = issue? --=20 Cheers, R. --Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUG1rIAAoJEOLF27JWwSg3m4QP+wW8M4kl8OS2yzPhi0TRPy9+ WSI2VRi34NW6HV27nvp8SewHV9787U4rm5jKbQaoVUN1ittv/JwT/YdDF2JyNfhj UccTrKF4z03/+zUpKUAQ9wwFKHd1OwNMYX7gj7RJpHTDqZpvI52BPhjSh8oXkhLr qHDcG8eOIQOOdvOYjBqXd4Qw5Q/JM8rrPHryiTBX/Uukgd4vR8eP6B0s0BG72sky sJawJtRvp+VYhAabHKm20LvmVTANYZTdKXgYJu784zWF45hzMvbIJRM74o4NSLkB kVpOgFrCrUoeuLItkxxWqwIZC0EDoyWhJx4S1aXkLV0blGrj/PEl+e/xvmXZc5z4 rYZ6zJoO18QcmVqHNXwXPJRFI/+wEt2/56zfSMHYkbckEN8RXQhIEkoH2rBsMVDE bb1yz+fC3yKNJik6sEHVNSyJ/Zyscsf6ABDrncEgOh9RiqIyznz7SxVxQMnrau7D HC5rztQ0MTxvCbpopIkY1/9ZGkcEHsqBc0cw65kKE+goOrMe/tMOA9Bi7CGZ/JiW u7gb9VhqkHjEtN1VgG0D157G6yyFk9pVI58sDov63fcMsnbR+DUQ36ODtVjYNpm/ fUgArVAyuj+XA7ELw/xronHO3A5Cpd3MHxA1O0S+joRoN8JoU4j5sEh/VifJGIFA 3OKvo/O+0NXE+edqPfhd =SsAo -----END PGP SIGNATURE----- --Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862-- --===============7039686314138284078== 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 --===============7039686314138284078==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:21:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:21:11 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUk4b-000536-UT; Thu, 18 Sep 2014 22:21:09 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUk4a-000530-Qz for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:21:08 +0000 Received: from [85.158.137.68:40382] by server-11.bemta-3.messagelabs.com id 86/30-01568-3DA5B145; Thu, 18 Sep 2014 22:21:07 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1411078866!12600472!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3116 invoked from network); 18 Sep 2014 22:21:07 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-10.tower-31.messagelabs.com with SMTP; 18 Sep 2014 22:21:07 -0000 Received: (qmail 9857 invoked from network); 18 Sep 2014 22:21:04 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 18 Sep 2014 22:21:04 -0000 Received: from engine03-20433-10.icritical.com ([127.0.0.1]) by localhost (engine03-20433-10.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 04258-05 for ; Thu, 18 Sep 2014 23:20:57 +0100 (BST) Received: (qmail 9788 invoked by uid 599); 18 Sep 2014 22:20:57 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 23:20:57 +0100 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 1XUk4Q-0006nr-Cv; Thu, 18 Sep 2014 23:20:58 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 18 Sep 2014 23:20:56 +0100 Thread-Topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos Thread-Index: Ac/TjtF7RHJYrPY5RdqdmskZagZZLA== Message-ID: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7039686314138284078==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7039686314138284078== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Sep 2014, at 22:38, Anil Madhavapeddy wrote: > I've ported the trunks of mirage-skeleton and mirage-www to use the = Mirage 2 development repositories, since most of us are using the latest = libraries in order to test them for release anyway. >=20 > To build mirage-skeleton/mirage-www, you will now need to: >=20 > opam remote add mirage git://github.com/mirage/mirage-dev > opam update -u fwiw just tried that and ended up at=20 ... mirage-www.1.2.0 Fetching git://github.com/mirage/mirage-www The following DEV package needs to be upgraded: - mirage-www.1.2.0 Updating the cache of metadata (~/.opam/state.cache) ... 0 to install | 103 to reinstall | 14 to upgrade | 1 to downgrade | 0 to = remove You can now run 'opam upgrade' to upgrade your system. [WARNING] External solver failed with inconsistent return value. Request = saved to "/Users/mort/.opam/log/solver-error-33616-1.cudf" Falling back to the internal heuristic. ...at which point i killed it. is this expected, or worth filing an opam = issue? --=20 Cheers, R. --Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUG1rIAAoJEOLF27JWwSg3m4QP+wW8M4kl8OS2yzPhi0TRPy9+ WSI2VRi34NW6HV27nvp8SewHV9787U4rm5jKbQaoVUN1ittv/JwT/YdDF2JyNfhj UccTrKF4z03/+zUpKUAQ9wwFKHd1OwNMYX7gj7RJpHTDqZpvI52BPhjSh8oXkhLr qHDcG8eOIQOOdvOYjBqXd4Qw5Q/JM8rrPHryiTBX/Uukgd4vR8eP6B0s0BG72sky sJawJtRvp+VYhAabHKm20LvmVTANYZTdKXgYJu784zWF45hzMvbIJRM74o4NSLkB kVpOgFrCrUoeuLItkxxWqwIZC0EDoyWhJx4S1aXkLV0blGrj/PEl+e/xvmXZc5z4 rYZ6zJoO18QcmVqHNXwXPJRFI/+wEt2/56zfSMHYkbckEN8RXQhIEkoH2rBsMVDE bb1yz+fC3yKNJik6sEHVNSyJ/Zyscsf6ABDrncEgOh9RiqIyznz7SxVxQMnrau7D HC5rztQ0MTxvCbpopIkY1/9ZGkcEHsqBc0cw65kKE+goOrMe/tMOA9Bi7CGZ/JiW u7gb9VhqkHjEtN1VgG0D157G6yyFk9pVI58sDov63fcMsnbR+DUQ36ODtVjYNpm/ fUgArVAyuj+XA7ELw/xronHO3A5Cpd3MHxA1O0S+joRoN8JoU4j5sEh/VifJGIFA 3OKvo/O+0NXE+edqPfhd =SsAo -----END PGP SIGNATURE----- --Apple-Mail=_129BC023-FC6F-4B7B-A993-A38110B9B862-- --===============7039686314138284078== 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 --===============7039686314138284078==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:28:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:28: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 1XUkBv-00059u-OF; Thu, 18 Sep 2014 22:28:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkBu-00059n-1e for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:28:42 +0000 Received: from [193.109.254.147:36500] by server-1.bemta-14.messagelabs.com id 46/BB-24760-99C5B145; Thu, 18 Sep 2014 22:28:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1411079317!16507987!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10224 invoked from network); 18 Sep 2014 22:28:37 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2014 22:28:37 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 8e264197; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 18 Sep 2014 23:29:28 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> Date: Thu, 18 Sep 2014 23:28:34 +0100 Message-Id: References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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 Sep 2014, at 23:20, Richard Mortier wrote: > > On 18 Sep 2014, at 22:38, Anil Madhavapeddy wrote: > >> I've ported the trunks of mirage-skeleton and mirage-www to use the Mirage 2 development repositories, since most of us are using the latest libraries in order to test them for release anyway. >> >> To build mirage-skeleton/mirage-www, you will now need to: >> >> opam remote add mirage git://github.com/mirage/mirage-dev >> opam update -u > > fwiw just tried that and ended up at > > ... > mirage-www.1.2.0 Fetching git://github.com/mirage/mirage-www > The following DEV package needs to be upgraded: > - mirage-www.1.2.0 > Updating the cache of metadata (~/.opam/state.cache) ... > 0 to install | 103 to reinstall | 14 to upgrade | 1 to downgrade | 0 to remove > You can now run 'opam upgrade' to upgrade your system. > [WARNING] External solver failed with inconsistent return value. Request saved to "/Users/mort/.opam/log/solver-error-33616-1.cudf" > Falling back to the internal heuristic. > > ...at which point i killed it. is this expected, or worth filing an opam issue? If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade to OPAM 1.2.0 :-) ('brew install opam --HEAD' should do 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 Thu Sep 18 22:28:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:28: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 1XUkBv-00059u-OF; Thu, 18 Sep 2014 22:28:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkBu-00059n-1e for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:28:42 +0000 Received: from [193.109.254.147:36500] by server-1.bemta-14.messagelabs.com id 46/BB-24760-99C5B145; Thu, 18 Sep 2014 22:28:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1411079317!16507987!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10224 invoked from network); 18 Sep 2014 22:28:37 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2014 22:28:37 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 8e264197; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 18 Sep 2014 23:29:28 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> Date: Thu, 18 Sep 2014 23:28:34 +0100 Message-Id: References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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 Sep 2014, at 23:20, Richard Mortier wrote: > > On 18 Sep 2014, at 22:38, Anil Madhavapeddy wrote: > >> I've ported the trunks of mirage-skeleton and mirage-www to use the Mirage 2 development repositories, since most of us are using the latest libraries in order to test them for release anyway. >> >> To build mirage-skeleton/mirage-www, you will now need to: >> >> opam remote add mirage git://github.com/mirage/mirage-dev >> opam update -u > > fwiw just tried that and ended up at > > ... > mirage-www.1.2.0 Fetching git://github.com/mirage/mirage-www > The following DEV package needs to be upgraded: > - mirage-www.1.2.0 > Updating the cache of metadata (~/.opam/state.cache) ... > 0 to install | 103 to reinstall | 14 to upgrade | 1 to downgrade | 0 to remove > You can now run 'opam upgrade' to upgrade your system. > [WARNING] External solver failed with inconsistent return value. Request saved to "/Users/mort/.opam/log/solver-error-33616-1.cudf" > Falling back to the internal heuristic. > > ...at which point i killed it. is this expected, or worth filing an opam issue? If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade to OPAM 1.2.0 :-) ('brew install opam --HEAD' should do 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 Thu Sep 18 22:37:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:37: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 1XUkK2-0005X3-Hq; Thu, 18 Sep 2014 22:37:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkK0-0005Wy-R5 for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:37:04 +0000 Received: from [193.109.254.147:38606] by server-1.bemta-14.messagelabs.com id BA/AE-24760-09E5B145; Thu, 18 Sep 2014 22:37:04 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1411079823!16498133!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13904 invoked from network); 18 Sep 2014 22:37:03 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-13.tower-27.messagelabs.com with SMTP; 18 Sep 2014 22:37:03 -0000 Received: (qmail 7040 invoked from network); 18 Sep 2014 22:36:58 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 18 Sep 2014 22:36:58 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 06600-09 for ; Thu, 18 Sep 2014 23:36:51 +0100 (BST) Received: (qmail 6967 invoked by uid 599); 18 Sep 2014 22:36:51 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 23:36:51 +0100 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 1XUkJo-00077R-H1; Thu, 18 Sep 2014 23:36:54 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 18 Sep 2014 23:36:49 +0100 Thread-Topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos Thread-Index: Ac/TkQpenyl0YC1oRkm1YEHeuvNQUw== Message-ID: <6667F35F-6647-460B-95F1-88768B3C092E@nottingham.ac.uk> References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6118393411733481634==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6118393411733481634== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Sep 2014, at 23:28, Anil Madhavapeddy wrote: > On 18 Sep 2014, at 23:20, Richard Mortier = wrote: >=20 >> ...at which point i killed it. is this expected, or worth filing an = opam issue? >=20 > If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade = to OPAM 1.2.0 :-) > ('brew install opam --HEAD' should do it). ah-- am on 1.1.2 still. will upgrade. (when is opam 1.2.0 due to hit = distros?) --=20 Cheers, R. --Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUG16BAAoJEOLF27JWwSg3OccP/RwQmO6VwsuBpUYU+ccdq3Wi JfgByNtzXIi+l/AsA8Af36d9UmbiMjIFrD6GTXzftRc6cNJDBX2nIVjfZO+rw4BN X99R6oqePANQSOWGwcvhNWZkscjmdHmQWjGoC9QTaCCNrkmiHj41hZn8GeZ0WaYF gfdke0dcuO5zv3HbYNkEVNFw8QoYVA7duokfUUEaBLpf89rwPiw6ZTQ6oHNnD2la OOBI3Ic7Pmh+SOBoobETbfNlvcG3HSyDWTjaS2eBe/0I4WrGWbVRXTAvqm9DHxGN QzMqEqWlX8tFxwjs8Foj3MZlb2g3wWIrML9Pm+TSVU97XSC+/pmC2UwrAGjb1b1G eWmLzy9rNOrdJxgQm7NIfTczPZ0SXotShWNj8w9VtzBSnq7dg8EgPFWRhgM5W2xL WegJqsv5oowsUvMz+40Bj62cdQp5qJF07qP3HM5NjI9zxDaAJ2GjnMT9wKNkaBBu s/1Bjsg6GdEC4KmBQxAdaRPXbGt+rUyF3vKPetkrakbEO2jpaxdXOuYQS7Cr3r44 DjinmKbUd8d52vgd635ftLLMwgS9Q5LDH3EDneeH1K3RwW6Jvj9xCkR5omhCkwRy 46dtGVZMBiAKg1D400nHKkY1RgsKLLqJRSDYcR0VsNg9Vv6uBmzX1LlzAe7Ow3Yg 9dBzcOaZh6NUvBnRnHf1 =UjGd -----END PGP SIGNATURE----- --Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3-- --===============6118393411733481634== 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 --===============6118393411733481634==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:37:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:37: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 1XUkK2-0005X3-Hq; Thu, 18 Sep 2014 22:37:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkK0-0005Wy-R5 for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:37:04 +0000 Received: from [193.109.254.147:38606] by server-1.bemta-14.messagelabs.com id BA/AE-24760-09E5B145; Thu, 18 Sep 2014 22:37:04 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-27.messagelabs.com!1411079823!16498133!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13904 invoked from network); 18 Sep 2014 22:37:03 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-13.tower-27.messagelabs.com with SMTP; 18 Sep 2014 22:37:03 -0000 Received: (qmail 7040 invoked from network); 18 Sep 2014 22:36:58 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 18 Sep 2014 22:36:58 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 06600-09 for ; Thu, 18 Sep 2014 23:36:51 +0100 (BST) Received: (qmail 6967 invoked by uid 599); 18 Sep 2014 22:36:51 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 23:36:51 +0100 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 1XUkJo-00077R-H1; Thu, 18 Sep 2014 23:36:54 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 18 Sep 2014 23:36:49 +0100 Thread-Topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos Thread-Index: Ac/TkQpenyl0YC1oRkm1YEHeuvNQUw== Message-ID: <6667F35F-6647-460B-95F1-88768B3C092E@nottingham.ac.uk> References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6118393411733481634==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6118393411733481634== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Sep 2014, at 23:28, Anil Madhavapeddy wrote: > On 18 Sep 2014, at 23:20, Richard Mortier = wrote: >=20 >> ...at which point i killed it. is this expected, or worth filing an = opam issue? >=20 > If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade = to OPAM 1.2.0 :-) > ('brew install opam --HEAD' should do it). ah-- am on 1.1.2 still. will upgrade. (when is opam 1.2.0 due to hit = distros?) --=20 Cheers, R. --Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUG16BAAoJEOLF27JWwSg3OccP/RwQmO6VwsuBpUYU+ccdq3Wi JfgByNtzXIi+l/AsA8Af36d9UmbiMjIFrD6GTXzftRc6cNJDBX2nIVjfZO+rw4BN X99R6oqePANQSOWGwcvhNWZkscjmdHmQWjGoC9QTaCCNrkmiHj41hZn8GeZ0WaYF gfdke0dcuO5zv3HbYNkEVNFw8QoYVA7duokfUUEaBLpf89rwPiw6ZTQ6oHNnD2la OOBI3Ic7Pmh+SOBoobETbfNlvcG3HSyDWTjaS2eBe/0I4WrGWbVRXTAvqm9DHxGN QzMqEqWlX8tFxwjs8Foj3MZlb2g3wWIrML9Pm+TSVU97XSC+/pmC2UwrAGjb1b1G eWmLzy9rNOrdJxgQm7NIfTczPZ0SXotShWNj8w9VtzBSnq7dg8EgPFWRhgM5W2xL WegJqsv5oowsUvMz+40Bj62cdQp5qJF07qP3HM5NjI9zxDaAJ2GjnMT9wKNkaBBu s/1Bjsg6GdEC4KmBQxAdaRPXbGt+rUyF3vKPetkrakbEO2jpaxdXOuYQS7Cr3r44 DjinmKbUd8d52vgd635ftLLMwgS9Q5LDH3EDneeH1K3RwW6Jvj9xCkR5omhCkwRy 46dtGVZMBiAKg1D400nHKkY1RgsKLLqJRSDYcR0VsNg9Vv6uBmzX1LlzAe7Ow3Yg 9dBzcOaZh6NUvBnRnHf1 =UjGd -----END PGP SIGNATURE----- --Apple-Mail=_D23DEF78-062A-472A-BD43-8EE7FB2648D3-- --===============6118393411733481634== 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 --===============6118393411733481634==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:38:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:38: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 1XUkLD-0005Ye-N3; Thu, 18 Sep 2014 22:38:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkLC-0005YZ-IY for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:38:18 +0000 Received: from [85.158.143.35:8543] by server-2.bemta-4.messagelabs.com id 08/EC-04525-9DE5B145; Thu, 18 Sep 2014 22:38:17 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1411079897!7536701!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23708 invoked from network); 18 Sep 2014 22:38:17 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-13.tower-21.messagelabs.com with SMTP; 18 Sep 2014 22:38:17 -0000 Received: (qmail 9944 invoked from network); 18 Sep 2014 22:38:16 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 18 Sep 2014 22:38:16 -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 08488-03 for ; Thu, 18 Sep 2014 23:38:09 +0100 (BST) Received: (qmail 9884 invoked by uid 599); 18 Sep 2014 22:38:09 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 23:38:09 +0100 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 1XUkL3-0006z0-Jc; Thu, 18 Sep 2014 23:38:09 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 18 Sep 2014 23:38:08 +0100 Thread-Topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos Thread-Index: Ac/TkTiXrnzDWBpFS3utVXrQY+7tsA== Message-ID: References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5136524080571072770==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5136524080571072770== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Sep 2014, at 23:28, Anil Madhavapeddy wrote: > On 18 Sep 2014, at 23:20, Richard Mortier = wrote: >=20 >> ...at which point i killed it. is this expected, or worth filing an = opam issue? >=20 > If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade = to OPAM 1.2.0 :-) > ('brew install opam --HEAD' should do it). ...in case anyone else is watching, need to precede that by "brew unlink = opam". --=20 Cheers, R. --Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUG17QAAoJEOLF27JWwSg3NqYP/i/1i/MciXNh/gK7Rskx3lqx RwfIEHI/iyGUZFVLUZfJz2QcOMHILmuhZriVelxk8FaNJvCaxl+u0xMtVbMm9l2F M3UMfe+MUoGbCDhgNUqZcma86A/3mUhADkr/JSLQf6Z+ZttMhNX/OxoRSTAmRiZB JX2sVgxjROsCA5yHmnbw3+BFwEBYm3WfIthuxIm+Bloc/SPoSYl5gRYgVlwBBOnG wgk3+UzxqsUChEX+fMYR6994YK7mIaf/dBoWsofuAhm6zUpDZJ2GskiFuJxgarxH 73x2UkOdgmMoSNhFAEVuJzNkr43GVUBSMUbXwGe/oNjyN9+kQGm8VkXTIIKWmkWG ls+tNlnU0O9Q89PnhROEX8sRo+Y2bgA4RODIB4iBoeNYTtIdVdoobbAda98ba/Tf j9+2DkZDmhs4eoFRySQ19UYJKye9bLFV47nJVstzVK2YPgKS34ifyjgsDNKImipg KAlVOGG+L2cdwxWksM7l4XwEQuMtl5WPVyH5lJUblRflX38sQRP7i9p7Mmpi8Wto CGw9yRmPZALFuBvdof2dGNWNki4y7npfkwNHTkNHi6+WO73yhpjtop0pUs9KnSDs El5Utb3dSZ9J3VG1PQLKAM48oshGd6S1e5v1BgfQHMcQfxIJGRc6x/OuIitbnGiM R7Oy7EoK5t6OtM/kz0NU =SR52 -----END PGP SIGNATURE----- --Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC-- --===============5136524080571072770== 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 --===============5136524080571072770==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:38:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:38: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 1XUkLD-0005Ye-N3; Thu, 18 Sep 2014 22:38:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkLC-0005YZ-IY for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:38:18 +0000 Received: from [85.158.143.35:8543] by server-2.bemta-4.messagelabs.com id 08/EC-04525-9DE5B145; Thu, 18 Sep 2014 22:38:17 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-13.tower-21.messagelabs.com!1411079897!7536701!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23708 invoked from network); 18 Sep 2014 22:38:17 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-13.tower-21.messagelabs.com with SMTP; 18 Sep 2014 22:38:17 -0000 Received: (qmail 9944 invoked from network); 18 Sep 2014 22:38:16 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 18 Sep 2014 22:38:16 -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 08488-03 for ; Thu, 18 Sep 2014 23:38:09 +0100 (BST) Received: (qmail 9884 invoked by uid 599); 18 Sep 2014 22:38:09 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 18 Sep 2014 23:38:09 +0100 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 1XUkL3-0006z0-Jc; Thu, 18 Sep 2014 23:38:09 +0100 From: Richard Mortier To: Anil Madhavapeddy Date: Thu, 18 Sep 2014 23:38:08 +0100 Thread-Topic: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos Thread-Index: Ac/TkTiXrnzDWBpFS3utVXrQY+7tsA== Message-ID: References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5136524080571072770==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5136524080571072770== Content-Language: en-US Content-Type: multipart/signed; boundary="Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC"; protocol="application/pgp-signature"; micalg=pgp-sha512 --Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Sep 2014, at 23:28, Anil Madhavapeddy wrote: > On 18 Sep 2014, at 23:20, Richard Mortier = wrote: >=20 >> ...at which point i killed it. is this expected, or worth filing an = opam issue? >=20 > If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade = to OPAM 1.2.0 :-) > ('brew install opam --HEAD' should do it). ...in case anyone else is watching, need to precede that by "brew unlink = opam". --=20 Cheers, R. --Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUG17QAAoJEOLF27JWwSg3NqYP/i/1i/MciXNh/gK7Rskx3lqx RwfIEHI/iyGUZFVLUZfJz2QcOMHILmuhZriVelxk8FaNJvCaxl+u0xMtVbMm9l2F M3UMfe+MUoGbCDhgNUqZcma86A/3mUhADkr/JSLQf6Z+ZttMhNX/OxoRSTAmRiZB JX2sVgxjROsCA5yHmnbw3+BFwEBYm3WfIthuxIm+Bloc/SPoSYl5gRYgVlwBBOnG wgk3+UzxqsUChEX+fMYR6994YK7mIaf/dBoWsofuAhm6zUpDZJ2GskiFuJxgarxH 73x2UkOdgmMoSNhFAEVuJzNkr43GVUBSMUbXwGe/oNjyN9+kQGm8VkXTIIKWmkWG ls+tNlnU0O9Q89PnhROEX8sRo+Y2bgA4RODIB4iBoeNYTtIdVdoobbAda98ba/Tf j9+2DkZDmhs4eoFRySQ19UYJKye9bLFV47nJVstzVK2YPgKS34ifyjgsDNKImipg KAlVOGG+L2cdwxWksM7l4XwEQuMtl5WPVyH5lJUblRflX38sQRP7i9p7Mmpi8Wto CGw9yRmPZALFuBvdof2dGNWNki4y7npfkwNHTkNHi6+WO73yhpjtop0pUs9KnSDs El5Utb3dSZ9J3VG1PQLKAM48oshGd6S1e5v1BgfQHMcQfxIJGRc6x/OuIitbnGiM R7Oy7EoK5t6OtM/kz0NU =SR52 -----END PGP SIGNATURE----- --Apple-Mail=_F114129F-7C05-42F5-9EF4-6DF4535EBEFC-- --===============5136524080571072770== 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 --===============5136524080571072770==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:39:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:39: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 1XUkMb-0005us-Tw; Thu, 18 Sep 2014 22:39:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkMa-0005un-Uh for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:39:45 +0000 Received: from [193.109.254.147:50261] by server-2.bemta-14.messagelabs.com id 21/88-07861-03F5B145; Thu, 18 Sep 2014 22:39:44 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1411079983!16520029!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31813 invoked from network); 18 Sep 2014 22:39:43 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2014 22:39:43 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 9fabb2b4; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 18 Sep 2014 23:40:34 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <6667F35F-6647-460B-95F1-88768B3C092E@nottingham.ac.uk> Date: Thu, 18 Sep 2014 23:39:40 +0100 Message-Id: <5DA8790A-2077-4690-87B9-839637DE25FA@recoil.org> References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> <6667F35F-6647-460B-95F1-88768B3C092E@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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 Sep 2014, at 23:36, Richard Mortier wrote: > > On 18 Sep 2014, at 23:28, Anil Madhavapeddy wrote: > >> On 18 Sep 2014, at 23:20, Richard Mortier wrote: >> >>> ...at which point i killed it. is this expected, or worth filing an opam issue? >> >> If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade to OPAM 1.2.0 :-) >> ('brew install opam --HEAD' should do it). > > ah-- am on 1.1.2 still. will upgrade. (when is opam 1.2.0 due to hit distros?) OPAM 1.2.0 is still going through a few release candidates, so the final release is still a few weeks away while the bug tail gets ironed out. Btw, the error you got is usually due to upstream packages being deleted. OPAM 1.1.x didn't handle that too well with the external solver, hence that error. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 18 22:39:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 18 Sep 2014 22:39: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 1XUkMb-0005us-Tw; Thu, 18 Sep 2014 22:39:45 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XUkMa-0005un-Uh for mirageos-devel@lists.xenproject.org; Thu, 18 Sep 2014 22:39:45 +0000 Received: from [193.109.254.147:50261] by server-2.bemta-14.messagelabs.com id 21/88-07861-03F5B145; Thu, 18 Sep 2014 22:39:44 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1411079983!16520029!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31813 invoked from network); 18 Sep 2014 22:39:43 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Sep 2014 22:39:43 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 9fabb2b4; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Thu, 18 Sep 2014 23:40:34 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <6667F35F-6647-460B-95F1-88768B3C092E@nottingham.ac.uk> Date: Thu, 18 Sep 2014 23:39:40 +0100 Message-Id: <5DA8790A-2077-4690-87B9-839637DE25FA@recoil.org> References: <50AB4D14-79CF-4546-A199-C39B5CBE992E@nottingham.ac.uk> <6667F35F-6647-460B-95F1-88768B3C092E@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel Subject: Re: [MirageOS-devel] headsup: mirage-skeleton and mirage-www now using dev repos X-BeenThere: mirageos-devel@lists.xenproject.org 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 Sep 2014, at 23:36, Richard Mortier wrote: > > On 18 Sep 2014, at 23:28, Anil Madhavapeddy wrote: > >> On 18 Sep 2014, at 23:20, Richard Mortier wrote: >> >>> ...at which point i killed it. is this expected, or worth filing an opam issue? >> >> If you're running OPAM 1.2.0, then report a bug. Otherwise, upgrade to OPAM 1.2.0 :-) >> ('brew install opam --HEAD' should do it). > > ah-- am on 1.1.2 still. will upgrade. (when is opam 1.2.0 due to hit distros?) OPAM 1.2.0 is still going through a few release candidates, so the final release is still a few weeks away while the bug tail gets ironed out. Btw, the error you got is usually due to upstream packages being deleted. OPAM 1.1.x didn't handle that too well with the external solver, hence that error. -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 Sep 19 21:41:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 19 Sep 2014 21:41: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 1XV5vx-00066F-CT; Fri, 19 Sep 2014 21:41:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XV5vv-00066A-HQ for mirageos-devel@lists.xenproject.org; Fri, 19 Sep 2014 21:41:39 +0000 Received: from [85.158.143.35:24739] by server-3.bemta-4.messagelabs.com id 7C/51-06192-213AC145; Fri, 19 Sep 2014 21:41:38 +0000 X-Env-Sender: b.gianfo@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1411162897!12027705!1 X-Originating-IP: [209.85.217.178] X-SpamReason: No, hits=2.0 required=7.0 tests=BODY_RANDOM_LONG, HTML_00_10, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15088 invoked from network); 19 Sep 2014 21:41:37 -0000 Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2014 21:41:37 -0000 Received: by mail-lb0-f178.google.com with SMTP id z12so1399822lbi.9 for ; Fri, 19 Sep 2014 14:41:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=EC8E4hnA/c/9c3JBWUKSWzUpX+xd/D5R83Vy8gVHLss=; b=E4Blz47NXSHT7kodx3zZ1qs4K9l370iWMGvW1f0yES+nuaS4aC+juw+6kQUKk9BY/Q 2DLslUySJAOrmBaI+7/Ybge0veRTO+NPIw0XT9NspdYbalMLJUpHa16gc723ESuHYl5B niMCsAe+0d6fhxWw+NGptx0HXzHLpaE6sUCwYC9FJY1Fm5Iv2xaeoInEu6loMcz3+NHw 0+P/PHCdThzin6EVhbDtw08nnsHgnUoOgyGBLE8NHaSijiPzUWgEg29TTzAYOCkvOKqT pYeSjkX5Ufpq2AmIaBIv3DnxbADodJxEFGLQPOYAUckCQY6SsYWfklzL5xYBdwZUPOj/ 07Ow== X-Received: by 10.152.5.9 with SMTP id o9mr6250314lao.95.1411162896845; Fri, 19 Sep 2014 14:41:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.109.72 with HTTP; Fri, 19 Sep 2014 14:41:15 -0700 (PDT) From: Brian Gianforcaro Date: Fri, 19 Sep 2014 14:41:15 -0700 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3845783289905611836==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3845783289905611836== Content-Type: multipart/alternative; boundary=089e013d17ce2fd0de050371f74c --089e013d17ce2fd0de050371f74c Content-Type: text/plain; charset=UTF-8 Hello All, I'm interested in working on adding support for Windows and eventually Hyper-V deployment of MirageOS unikernels. My end goal is getting MirageOS unikernels running on Windows Azure, as it would seem having ubiquitous cloud hosting support would be very valuable to the project. For now it seems like having just plain Windows process support would be a great stepping stone to this eventual goal. I've been poking around the code, and see that everything seems to be partitioned cleanly into separate packages for xen and unix support. This gives me at least a little hope that windows / hyper-v support could be added piecemeal overtime without being a merging nightmare as development continues to occur. Very impressed with the clean isolation :) As far as I can tell it seems like I would have to implement the following opam packages to get windows process support working: 1) mirage-win Mirage OS library for Windows compilation 2) mirage-console-win A Mirage-compatible Console library for Windows 3) mirage-clock-win A Mirage-compatible Clock library for Windows 4) mirage-entropy-win Mirage entropy device for Windows 5) mirage-block-win Mirage block driver for Windows 6) mirage-fs-win Mirage file system pass through driver for Windows 7) mirage-net-win Ethernet network driver for Mirage (seems like this might be optional?) 8) mirage-tcpip-win Userlevel TCP/IP stack 9) mirage-http-win Mirage HTTP client and server driver for Windows The root mirage package 'mirage' would also have to be modified to support a --win option, and other plumbing. Conceptually this all seems fine and dandy, be it a reasonably large chunk of work. I'm not intimately familiar with the ocaml ecosystem on windows, I've only ever dabbled in the language on unix machines. This leads be to wonder if Windows support for MirageOS is dead on arrival, given the current windows support the tooling MirageOS fundamentally uses. For instance it seems like currently even opam doesn't support running on windows? (I read that it is coming..) I imagine there are many other such cases, that I simply won't know about until I hit them. Am I mistaken, or is windows support for the tooling going to be a big blocker to getting anything working? Any feedback on the idea itself, approach, big blockers, anyone doing similar work would be greatly appreciated. Thanks! - Brian --089e013d17ce2fd0de050371f74c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello All,

I'm interested in working on adding= support for Windows and eventually Hyper-V deployment of MirageOS unikerne= ls.

My end goal is getting MirageOS unikernels running on Windows A= zure, as it would seem having ubiquitous
cloud hosting support would be= very valuable to the project. For now it seems like having just plain Wind= ows process
support would be a great stepping stone to this eventual goa= l.

I've been poking around the code, and see that everything se= ems to be partitioned cleanly into separate packages for
xen and unix s= upport. This gives me at least a little hope that windows / hyper-v support= could be added piecemeal=C2=A0
overtime without being a merging = nightmare as development continues to occur.

Very impressed with the= clean isolation :)

As far as I can tell it seems like I would have= to implement the following opam packages to get windows process support wo= rking:

=C2=A0 1) mirage-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0Mirage OS library for Windows compilation
=C2=A0 2) mir= age-console-win =C2=A0 A Mirage-compatible Console library for Windows
= =C2=A0 3) mirage-clock-win =C2=A0 =C2=A0 =C2=A0 A Mirage-compatible Clock l= ibrary for Windows
=C2=A0 4) mirage-entropy-win =C2=A0 Mirage entropy de= vice for Windows
=C2=A0 5) mirage-block-win =C2=A0 =C2=A0 =C2=A0 Mirage = block driver for Windows
=C2=A0 6) mirage-fs-win =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0Mirage file system pass through driver for Windows
= =C2=A0 7) mirage-net-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ethernet network= driver for Mirage (seems like this might be optional?)
=C2=A0 8) mirage= -tcpip-win =C2=A0 =C2=A0 =C2=A0 Userlevel TCP/IP stack
=C2=A0 9) mirage-= http-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mirage HTTP client and server driver f= or Windows

The root mirage package 'mirage' would also have = to be modified to support a --win option, and other plumbing.=C2=A0

= Conceptually this all seems fine and dandy, be it a reasonably large chunk = of work.

I'm not intimately familiar with the ocaml ecosystem o= n windows, I've only ever dabbled in the language
on unix machines. = This leads be to wonder if Windows support for MirageOS is dead on arrival,= given the
current windows support the tooling MirageOS fundamentally us= es. For instance it seems like currently
even opam doesn't support = running on windows? (I read that it is coming..) I imagine there are many <= br>other such cases, that I simply won't know about until I hit them.
Am I mistaken, or is windows support for the tooling going to be a bi= g blocker to getting anything working?
=C2=A0
Any feedback on the ide= a itself, approach, big blockers, anyone doing similar work would be greatl= y appreciated.

Thanks!
- Brian
--089e013d17ce2fd0de050371f74c-- --===============3845783289905611836== 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 --===============3845783289905611836==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 19 21:41:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 19 Sep 2014 21:41: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 1XV5vx-00066F-CT; Fri, 19 Sep 2014 21:41:41 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XV5vv-00066A-HQ for mirageos-devel@lists.xenproject.org; Fri, 19 Sep 2014 21:41:39 +0000 Received: from [85.158.143.35:24739] by server-3.bemta-4.messagelabs.com id 7C/51-06192-213AC145; Fri, 19 Sep 2014 21:41:38 +0000 X-Env-Sender: b.gianfo@gmail.com X-Msg-Ref: server-9.tower-21.messagelabs.com!1411162897!12027705!1 X-Originating-IP: [209.85.217.178] X-SpamReason: No, hits=2.0 required=7.0 tests=BODY_RANDOM_LONG, HTML_00_10, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15088 invoked from network); 19 Sep 2014 21:41:37 -0000 Received: from mail-lb0-f178.google.com (HELO mail-lb0-f178.google.com) (209.85.217.178) by server-9.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Sep 2014 21:41:37 -0000 Received: by mail-lb0-f178.google.com with SMTP id z12so1399822lbi.9 for ; Fri, 19 Sep 2014 14:41:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=EC8E4hnA/c/9c3JBWUKSWzUpX+xd/D5R83Vy8gVHLss=; b=E4Blz47NXSHT7kodx3zZ1qs4K9l370iWMGvW1f0yES+nuaS4aC+juw+6kQUKk9BY/Q 2DLslUySJAOrmBaI+7/Ybge0veRTO+NPIw0XT9NspdYbalMLJUpHa16gc723ESuHYl5B niMCsAe+0d6fhxWw+NGptx0HXzHLpaE6sUCwYC9FJY1Fm5Iv2xaeoInEu6loMcz3+NHw 0+P/PHCdThzin6EVhbDtw08nnsHgnUoOgyGBLE8NHaSijiPzUWgEg29TTzAYOCkvOKqT pYeSjkX5Ufpq2AmIaBIv3DnxbADodJxEFGLQPOYAUckCQY6SsYWfklzL5xYBdwZUPOj/ 07Ow== X-Received: by 10.152.5.9 with SMTP id o9mr6250314lao.95.1411162896845; Fri, 19 Sep 2014 14:41:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.109.72 with HTTP; Fri, 19 Sep 2014 14:41:15 -0700 (PDT) From: Brian Gianforcaro Date: Fri, 19 Sep 2014 14:41:15 -0700 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3845783289905611836==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3845783289905611836== Content-Type: multipart/alternative; boundary=089e013d17ce2fd0de050371f74c --089e013d17ce2fd0de050371f74c Content-Type: text/plain; charset=UTF-8 Hello All, I'm interested in working on adding support for Windows and eventually Hyper-V deployment of MirageOS unikernels. My end goal is getting MirageOS unikernels running on Windows Azure, as it would seem having ubiquitous cloud hosting support would be very valuable to the project. For now it seems like having just plain Windows process support would be a great stepping stone to this eventual goal. I've been poking around the code, and see that everything seems to be partitioned cleanly into separate packages for xen and unix support. This gives me at least a little hope that windows / hyper-v support could be added piecemeal overtime without being a merging nightmare as development continues to occur. Very impressed with the clean isolation :) As far as I can tell it seems like I would have to implement the following opam packages to get windows process support working: 1) mirage-win Mirage OS library for Windows compilation 2) mirage-console-win A Mirage-compatible Console library for Windows 3) mirage-clock-win A Mirage-compatible Clock library for Windows 4) mirage-entropy-win Mirage entropy device for Windows 5) mirage-block-win Mirage block driver for Windows 6) mirage-fs-win Mirage file system pass through driver for Windows 7) mirage-net-win Ethernet network driver for Mirage (seems like this might be optional?) 8) mirage-tcpip-win Userlevel TCP/IP stack 9) mirage-http-win Mirage HTTP client and server driver for Windows The root mirage package 'mirage' would also have to be modified to support a --win option, and other plumbing. Conceptually this all seems fine and dandy, be it a reasonably large chunk of work. I'm not intimately familiar with the ocaml ecosystem on windows, I've only ever dabbled in the language on unix machines. This leads be to wonder if Windows support for MirageOS is dead on arrival, given the current windows support the tooling MirageOS fundamentally uses. For instance it seems like currently even opam doesn't support running on windows? (I read that it is coming..) I imagine there are many other such cases, that I simply won't know about until I hit them. Am I mistaken, or is windows support for the tooling going to be a big blocker to getting anything working? Any feedback on the idea itself, approach, big blockers, anyone doing similar work would be greatly appreciated. Thanks! - Brian --089e013d17ce2fd0de050371f74c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello All,

I'm interested in working on adding= support for Windows and eventually Hyper-V deployment of MirageOS unikerne= ls.

My end goal is getting MirageOS unikernels running on Windows A= zure, as it would seem having ubiquitous
cloud hosting support would be= very valuable to the project. For now it seems like having just plain Wind= ows process
support would be a great stepping stone to this eventual goa= l.

I've been poking around the code, and see that everything se= ems to be partitioned cleanly into separate packages for
xen and unix s= upport. This gives me at least a little hope that windows / hyper-v support= could be added piecemeal=C2=A0
overtime without being a merging = nightmare as development continues to occur.

Very impressed with the= clean isolation :)

As far as I can tell it seems like I would have= to implement the following opam packages to get windows process support wo= rking:

=C2=A0 1) mirage-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0Mirage OS library for Windows compilation
=C2=A0 2) mir= age-console-win =C2=A0 A Mirage-compatible Console library for Windows
= =C2=A0 3) mirage-clock-win =C2=A0 =C2=A0 =C2=A0 A Mirage-compatible Clock l= ibrary for Windows
=C2=A0 4) mirage-entropy-win =C2=A0 Mirage entropy de= vice for Windows
=C2=A0 5) mirage-block-win =C2=A0 =C2=A0 =C2=A0 Mirage = block driver for Windows
=C2=A0 6) mirage-fs-win =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0Mirage file system pass through driver for Windows
= =C2=A0 7) mirage-net-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ethernet network= driver for Mirage (seems like this might be optional?)
=C2=A0 8) mirage= -tcpip-win =C2=A0 =C2=A0 =C2=A0 Userlevel TCP/IP stack
=C2=A0 9) mirage-= http-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mirage HTTP client and server driver f= or Windows

The root mirage package 'mirage' would also have = to be modified to support a --win option, and other plumbing.=C2=A0

= Conceptually this all seems fine and dandy, be it a reasonably large chunk = of work.

I'm not intimately familiar with the ocaml ecosystem o= n windows, I've only ever dabbled in the language
on unix machines. = This leads be to wonder if Windows support for MirageOS is dead on arrival,= given the
current windows support the tooling MirageOS fundamentally us= es. For instance it seems like currently
even opam doesn't support = running on windows? (I read that it is coming..) I imagine there are many <= br>other such cases, that I simply won't know about until I hit them.
Am I mistaken, or is windows support for the tooling going to be a bi= g blocker to getting anything working?
=C2=A0
Any feedback on the ide= a itself, approach, big blockers, anyone doing similar work would be greatl= y appreciated.

Thanks!
- Brian
--089e013d17ce2fd0de050371f74c-- --===============3845783289905611836== 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 --===============3845783289905611836==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 07:53:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 07:53:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XVyQu-0007JS-I7; Mon, 22 Sep 2014 07:53:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XVyQt-0007JM-HT for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 07:53:15 +0000 Received: from [85.158.139.211:36636] by server-16.bemta-5.messagelabs.com id 56/AB-01029-A65DF145; Mon, 22 Sep 2014 07:53:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-206.messagelabs.com!1411372394!11238315!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19519 invoked from network); 22 Sep 2014 07:53:14 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-7.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2014 07:53:14 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 97f209b8; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 22 Sep 2014 08:54:16 +0100 (BST) From: Anil Madhavapeddy Date: Mon, 22 Sep 2014 08:53:09 +0100 Message-Id: <1E41D202-478F-4796-AFAA-B5CD4B2543EC@recoil.org> To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Cc: Peter Zotov Subject: [MirageOS-devel] u-boot + ocaml tree X-BeenThere: mirageos-devel@lists.xenproject.org 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 something I noticed from Peter Zotov's Twitter stream is that there's an old-but-workable branch of u-boot with an OCaml runtime linked in: http://git.denx.de/?p=u-boot/u-boot-ocaml.git;a=summary Something to file away in the utility toolbox (and the trees no doubt need to be refreshed), but possibly useful to help with HVM Xen/x86 booting as well... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 07:53:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 07:53:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XVyQu-0007JS-I7; Mon, 22 Sep 2014 07:53:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XVyQt-0007JM-HT for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 07:53:15 +0000 Received: from [85.158.139.211:36636] by server-16.bemta-5.messagelabs.com id 56/AB-01029-A65DF145; Mon, 22 Sep 2014 07:53:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-206.messagelabs.com!1411372394!11238315!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19519 invoked from network); 22 Sep 2014 07:53:14 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-7.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2014 07:53:14 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 97f209b8; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 22 Sep 2014 08:54:16 +0100 (BST) From: Anil Madhavapeddy Date: Mon, 22 Sep 2014 08:53:09 +0100 Message-Id: <1E41D202-478F-4796-AFAA-B5CD4B2543EC@recoil.org> To: mirageos-devel Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Cc: Peter Zotov Subject: [MirageOS-devel] u-boot + ocaml tree X-BeenThere: mirageos-devel@lists.xenproject.org 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 something I noticed from Peter Zotov's Twitter stream is that there's an old-but-workable branch of u-boot with an OCaml runtime linked in: http://git.denx.de/?p=u-boot/u-boot-ocaml.git;a=summary Something to file away in the utility toolbox (and the trees no doubt need to be refreshed), but possibly useful to help with HVM Xen/x86 booting as well... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 08:10:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 08:10: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 1XVyhN-0007zO-UR; Mon, 22 Sep 2014 08:10:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XVyhM-0007zH-7o for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 08:10:16 +0000 Received: from [193.109.254.147:14000] by server-13.bemta-14.messagelabs.com id E4/34-19311-769DF145; Mon, 22 Sep 2014 08:10:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1411373413!12053189!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3853 invoked from network); 22 Sep 2014 08:10:14 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2014 08:10:14 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 3b0dd493; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 22 Sep 2014 09:11:16 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 22 Sep 2014 09:10:10 +0100 Message-Id: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> References: To: Brian Gianforcaro X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3089678941375384640==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3089678941375384640== Content-Type: multipart/alternative; boundary="Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D" --Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 19 Sep 2014, at 22:41, Brian Gianforcaro wrote: > Hello All,=20 >=20 > I'm interested in working on adding support for Windows and eventually = Hyper-V deployment of MirageOS unikernels.=20 >=20 > My end goal is getting MirageOS unikernels running on Windows Azure, = as it would seem having ubiquitous=20 > cloud hosting support would be very valuable to the project. For now = it seems like having just plain Windows process > support would be a great stepping stone to this eventual goal.=20 Hi Brian, Glad to hear you're interested in working on this! Windows support has = been oft-asked for, but noone's explicitly started doing anything in = this direction yet. One approach for Azure support that's been pointed out a few times is = adding UEFI bootloader support; see = https://github.com/mirage/mirage/issues/187 However, it would certainly be easier to start with good userspace = support before delving into the kernel mode. > I've been poking around the code, and see that everything seems to be = partitioned cleanly into separate packages for > xen and unix support. This gives me at least a little hope that = windows / hyper-v support could be added piecemeal=20 > overtime without being a merging nightmare as development continues to = occur. >=20 > Very impressed with the clean isolation :)=20 >=20 > As far as I can tell it seems like I would have to implement the = following opam packages to get windows process support working:=20 >=20 > 1) mirage-win Mirage OS library for Windows = compilation > 2) mirage-console-win A Mirage-compatible Console library for = Windows > 3) mirage-clock-win A Mirage-compatible Clock library for = Windows > 4) mirage-entropy-win Mirage entropy device for Windows > 5) mirage-block-win Mirage block driver for Windows > 6) mirage-fs-win Mirage file system pass through driver = for Windows > 7) mirage-net-win Ethernet network driver for Mirage (seems = like this might be optional?) > 8) mirage-tcpip-win Userlevel TCP/IP stack > 9) mirage-http-win Mirage HTTP client and server driver for = Windows >=20 > The root mirage package 'mirage' would also have to be modified to = support a --win option, and other plumbing.=20 >=20 > Conceptually this all seems fine and dandy, be it a reasonably large = chunk of work.=20 >=20 > I'm not intimately familiar with the ocaml ecosystem on windows, I've = only ever dabbled in the language > on unix machines. This leads be to wonder if Windows support for = MirageOS is dead on arrival, given the > current windows support the tooling MirageOS fundamentally uses. For = instance it seems like currently=20 > even opam doesn't support running on windows? (I read that it is = coming..) I imagine there are many=20 > other such cases, that I simply won't know about until I hit them. >=20 > Am I mistaken, or is windows support for the tooling going to be a big = blocker to getting anything working? This is exactly the right analysis -- the package breakup is correct, = but the existing approach to doing build will make things hard to = compile on Windows, I suspect. However, we are working on a package = description system called Assemblage [1] (lead by Thomas Gazagnaire and = Daniel Buenzli) that should simplify build of Mirage packages = considerably. The current interface is being revved and isn't finalised, = but it should be fairly simple to ensure that the Makefiles that it = generates are Windows compliant. Which leads onto the second point -- it would be very useful to = establish an absolute minimal set of libraries to get started with = having a Windows environment on which to build upon. For Mirage, this = is just the hello world example with mirage-win and mirage-console-win = (and possibly the clock). Getting these ported requires selecting the = preferred toolchain (mingw, Cygwin, MSVC?) and ensuring that OCaml = itself is happy with the setup. Once a console port works, the rest is just a matter of filling in the = library blanks, just as we did over the years with the existing *nix and = Xen backends. [1] https://github.com/samoht/assemblage best, Anil= --Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 19 = Sep 2014, at 22:41, Brian Gianforcaro <b.gianfo@gmail.com> = wrote:

Hello All,

I'm interested in = working on adding support for Windows and eventually Hyper-V deployment = of MirageOS unikernels.

My end goal is getting MirageOS = unikernels running on Windows Azure, as it would seem having ubiquitous =
cloud hosting support would be very valuable to the project. For now = it seems like having just plain Windows process
support would be a = great stepping stone to this eventual = goal. 

Hi = Brian,

Glad to hear you're interested in = working on this!  Windows support has been oft-asked for, but = noone's explicitly started doing anything in this direction = yet.

One approach for Azure support that's been = pointed out a few times is adding UEFI bootloader support; see https://github.com/mi= rage/mirage/issues/187

However, it would = certainly be easier to start with good userspace support before delving = into the kernel mode.

I've been poking around the code, and see that everything = seems to be partitioned cleanly into separate packages for
xen and = unix support. This gives me at least a little hope that windows / = hyper-v support could be added piecemeal 
overtime = without being a merging nightmare as development continues to = occur.

Very impressed with the clean isolation :)

As far = as I can tell it seems like I would have to implement the following opam = packages to get windows process support working:

  1) = mirage-win                Mirage = OS library for Windows compilation
  2) mirage-console-win =   A Mirage-compatible Console library for Windows
  3) = mirage-clock-win       A Mirage-compatible Clock library = for Windows
  4) mirage-entropy-win   Mirage entropy device = for Windows
  5) mirage-block-win       Mirage = block driver for Windows
  6) mirage-fs-win       =      Mirage file system pass through driver for = Windows
  7) mirage-net-win         =  Ethernet network driver for Mirage (seems like this might be = optional?)
  8) mirage-tcpip-win       Userlevel = TCP/IP stack
  9) mirage-http-win         = Mirage HTTP client and server driver for Windows

The root mirage = package 'mirage' would also have to be modified to support a --win = option, and other plumbing. 

Conceptually this all seems = fine and dandy, be it a reasonably large chunk of = work. 

I'm not intimately familiar with the ocaml = ecosystem on windows, I've only ever dabbled in the language
on unix = machines. This leads be to wonder if Windows support for MirageOS is = dead on arrival, given the
current windows support the tooling = MirageOS fundamentally uses. For instance it seems like currently =
even opam doesn't support running on windows? (I read that it is = coming..) I imagine there are many
other such cases, that I simply = won't know about until I hit them.

Am I mistaken, or is windows = support for the tooling going to be a big blocker to getting anything = working?

This is exactly the = right analysis -- the package breakup is correct, but the existing = approach to doing build will make things hard to compile on Windows, I = suspect.  However, we are working on a package description system = called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzli) = that should simplify build of Mirage packages considerably. The current = interface is being revved and isn't finalised, but it should be fairly = simple to ensure that the Makefiles that it generates are Windows = compliant.

Which leads onto the second point -- = it would be very useful to establish an absolute minimal set of = libraries to get started with having a Windows environment on which to = build upon.  For Mirage, this is just the hello world example with = mirage-win and mirage-console-win (and possibly the clock). Getting = these ported requires selecting the preferred toolchain (mingw, Cygwin, = MSVC?) and ensuring that OCaml itself is happy with the = setup.

Once a console port works, the rest is = just a matter of filling in the library blanks, just as we did over the = years with the existing *nix and Xen = backends.


best,
Anil
= --Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D-- --===============3089678941375384640== 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 --===============3089678941375384640==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 08:10:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 08:10: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 1XVyhN-0007zO-UR; Mon, 22 Sep 2014 08:10:17 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XVyhM-0007zH-7o for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 08:10:16 +0000 Received: from [193.109.254.147:14000] by server-13.bemta-14.messagelabs.com id E4/34-19311-769DF145; Mon, 22 Sep 2014 08:10:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1411373413!12053189!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.6 required=7.0 tests=BODY_RANDOM_LONG, HTML_20_30,HTML_MESSAGE,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3853 invoked from network); 22 Sep 2014 08:10:14 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-3.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2014 08:10:14 -0000 Received: from [192.168.1.113] (cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net [86.30.244.239]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id 3b0dd493; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 22 Sep 2014 09:11:16 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 22 Sep 2014 09:10:10 +0100 Message-Id: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> References: To: Brian Gianforcaro X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3089678941375384640==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3089678941375384640== Content-Type: multipart/alternative; boundary="Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D" --Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 19 Sep 2014, at 22:41, Brian Gianforcaro wrote: > Hello All,=20 >=20 > I'm interested in working on adding support for Windows and eventually = Hyper-V deployment of MirageOS unikernels.=20 >=20 > My end goal is getting MirageOS unikernels running on Windows Azure, = as it would seem having ubiquitous=20 > cloud hosting support would be very valuable to the project. For now = it seems like having just plain Windows process > support would be a great stepping stone to this eventual goal.=20 Hi Brian, Glad to hear you're interested in working on this! Windows support has = been oft-asked for, but noone's explicitly started doing anything in = this direction yet. One approach for Azure support that's been pointed out a few times is = adding UEFI bootloader support; see = https://github.com/mirage/mirage/issues/187 However, it would certainly be easier to start with good userspace = support before delving into the kernel mode. > I've been poking around the code, and see that everything seems to be = partitioned cleanly into separate packages for > xen and unix support. This gives me at least a little hope that = windows / hyper-v support could be added piecemeal=20 > overtime without being a merging nightmare as development continues to = occur. >=20 > Very impressed with the clean isolation :)=20 >=20 > As far as I can tell it seems like I would have to implement the = following opam packages to get windows process support working:=20 >=20 > 1) mirage-win Mirage OS library for Windows = compilation > 2) mirage-console-win A Mirage-compatible Console library for = Windows > 3) mirage-clock-win A Mirage-compatible Clock library for = Windows > 4) mirage-entropy-win Mirage entropy device for Windows > 5) mirage-block-win Mirage block driver for Windows > 6) mirage-fs-win Mirage file system pass through driver = for Windows > 7) mirage-net-win Ethernet network driver for Mirage (seems = like this might be optional?) > 8) mirage-tcpip-win Userlevel TCP/IP stack > 9) mirage-http-win Mirage HTTP client and server driver for = Windows >=20 > The root mirage package 'mirage' would also have to be modified to = support a --win option, and other plumbing.=20 >=20 > Conceptually this all seems fine and dandy, be it a reasonably large = chunk of work.=20 >=20 > I'm not intimately familiar with the ocaml ecosystem on windows, I've = only ever dabbled in the language > on unix machines. This leads be to wonder if Windows support for = MirageOS is dead on arrival, given the > current windows support the tooling MirageOS fundamentally uses. For = instance it seems like currently=20 > even opam doesn't support running on windows? (I read that it is = coming..) I imagine there are many=20 > other such cases, that I simply won't know about until I hit them. >=20 > Am I mistaken, or is windows support for the tooling going to be a big = blocker to getting anything working? This is exactly the right analysis -- the package breakup is correct, = but the existing approach to doing build will make things hard to = compile on Windows, I suspect. However, we are working on a package = description system called Assemblage [1] (lead by Thomas Gazagnaire and = Daniel Buenzli) that should simplify build of Mirage packages = considerably. The current interface is being revved and isn't finalised, = but it should be fairly simple to ensure that the Makefiles that it = generates are Windows compliant. Which leads onto the second point -- it would be very useful to = establish an absolute minimal set of libraries to get started with = having a Windows environment on which to build upon. For Mirage, this = is just the hello world example with mirage-win and mirage-console-win = (and possibly the clock). Getting these ported requires selecting the = preferred toolchain (mingw, Cygwin, MSVC?) and ensuring that OCaml = itself is happy with the setup. Once a console port works, the rest is just a matter of filling in the = library blanks, just as we did over the years with the existing *nix and = Xen backends. [1] https://github.com/samoht/assemblage best, Anil= --Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 19 = Sep 2014, at 22:41, Brian Gianforcaro <b.gianfo@gmail.com> = wrote:

Hello All,

I'm interested in = working on adding support for Windows and eventually Hyper-V deployment = of MirageOS unikernels.

My end goal is getting MirageOS = unikernels running on Windows Azure, as it would seem having ubiquitous =
cloud hosting support would be very valuable to the project. For now = it seems like having just plain Windows process
support would be a = great stepping stone to this eventual = goal. 

Hi = Brian,

Glad to hear you're interested in = working on this!  Windows support has been oft-asked for, but = noone's explicitly started doing anything in this direction = yet.

One approach for Azure support that's been = pointed out a few times is adding UEFI bootloader support; see https://github.com/mi= rage/mirage/issues/187

However, it would = certainly be easier to start with good userspace support before delving = into the kernel mode.

I've been poking around the code, and see that everything = seems to be partitioned cleanly into separate packages for
xen and = unix support. This gives me at least a little hope that windows / = hyper-v support could be added piecemeal 
overtime = without being a merging nightmare as development continues to = occur.

Very impressed with the clean isolation :)

As far = as I can tell it seems like I would have to implement the following opam = packages to get windows process support working:

  1) = mirage-win                Mirage = OS library for Windows compilation
  2) mirage-console-win =   A Mirage-compatible Console library for Windows
  3) = mirage-clock-win       A Mirage-compatible Clock library = for Windows
  4) mirage-entropy-win   Mirage entropy device = for Windows
  5) mirage-block-win       Mirage = block driver for Windows
  6) mirage-fs-win       =      Mirage file system pass through driver for = Windows
  7) mirage-net-win         =  Ethernet network driver for Mirage (seems like this might be = optional?)
  8) mirage-tcpip-win       Userlevel = TCP/IP stack
  9) mirage-http-win         = Mirage HTTP client and server driver for Windows

The root mirage = package 'mirage' would also have to be modified to support a --win = option, and other plumbing. 

Conceptually this all seems = fine and dandy, be it a reasonably large chunk of = work. 

I'm not intimately familiar with the ocaml = ecosystem on windows, I've only ever dabbled in the language
on unix = machines. This leads be to wonder if Windows support for MirageOS is = dead on arrival, given the
current windows support the tooling = MirageOS fundamentally uses. For instance it seems like currently =
even opam doesn't support running on windows? (I read that it is = coming..) I imagine there are many
other such cases, that I simply = won't know about until I hit them.

Am I mistaken, or is windows = support for the tooling going to be a big blocker to getting anything = working?

This is exactly the = right analysis -- the package breakup is correct, but the existing = approach to doing build will make things hard to compile on Windows, I = suspect.  However, we are working on a package description system = called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzli) = that should simplify build of Mirage packages considerably. The current = interface is being revved and isn't finalised, but it should be fairly = simple to ensure that the Makefiles that it generates are Windows = compliant.

Which leads onto the second point -- = it would be very useful to establish an absolute minimal set of = libraries to get started with having a Windows environment on which to = build upon.  For Mirage, this is just the hello world example with = mirage-win and mirage-console-win (and possibly the clock). Getting = these ported requires selecting the preferred toolchain (mingw, Cygwin, = MSVC?) and ensuring that OCaml itself is happy with the = setup.

Once a console port works, the rest is = just a matter of filling in the library blanks, just as we did over the = years with the existing *nix and Xen = backends.


best,
Anil
= --Apple-Mail=_C9E3F7E0-084B-41E1-AD4E-CA7A5C5F839D-- --===============3089678941375384640== 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 --===============3089678941375384640==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 11:49:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 11:49: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 1XW26w-0007WS-Si; Mon, 22 Sep 2014 11:48:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XW26v-0007WN-Es for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 11:48:53 +0000 Received: from [85.158.139.211:36763] by server-2.bemta-5.messagelabs.com id C1/00-31832-4AC00245; Mon, 22 Sep 2014 11:48:52 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1411386531!11252166!1 X-Originating-IP: [74.125.82.177] 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.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16412 invoked from network); 22 Sep 2014 11:48:51 -0000 Received: from mail-we0-f177.google.com (HELO mail-we0-f177.google.com) (74.125.82.177) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2014 11:48:51 -0000 Received: by mail-we0-f177.google.com with SMTP id t60so2705883wes.8 for ; Mon, 22 Sep 2014 04:48:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qGPgFsMpbhydY739yi6qaOiQXO5c0JL9C3PAzqGWKEM=; b=uSO3sJ3mcJkvF6Bu+wbGXQhUicE/5R2lJtEkk7oQUfyHSMNLuwAXQ/LjtK1D0dduzg EOvldNrmJqmTLTaiOS0lZtYsM4XiZi5wP4GFnF2DjDShgt6BrAbCmnEJhTKHOnO5GiMt EVbH1mvoHWNFWR8AEr8/TuY/YYJVJjLApHogvwbRsuceRE3M1NyhyHDBjq/GuiTdkjaw wvmMTxHTzOjpd+iuXCHAmqoCScupH+a+RsA8PBhPFoch+nif/L6dlz2vNgfBH9xGoiWc EFgaHZHBTDMERtdakNVYdIITPGy4rq+HTQON/4z3zot3eCyKrEcBG3Il1/Ev+Hmq4Bp2 e8bQ== MIME-Version: 1.0 X-Received: by 10.180.101.40 with SMTP id fd8mr2405791wib.63.1411386530917; Mon, 22 Sep 2014 04:48:50 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Mon, 22 Sep 2014 04:48:50 -0700 (PDT) In-Reply-To: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> References: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> Date: Mon, 22 Sep 2014 08:48:50 -0300 Message-ID: From: Stephen Mack To: Anil Madhavapeddy Cc: Brian Gianforcaro , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6727954086917804729==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6727954086917804729== Content-Type: multipart/alternative; boundary=f46d041826c6d0f3cd0503a608f3 --f46d041826c6d0f3cd0503a608f3 Content-Type: text/plain; charset=UTF-8 Anil, Doesn't Mirage depend on the Jane Street Core which has not yet been ported to Windows? Or maybe I am mistaken. The more platforms that accept Mirage the better in my opinion. Cheers --Stephen On Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy wrote: > On 19 Sep 2014, at 22:41, Brian Gianforcaro wrote: > > Hello All, > > I'm interested in working on adding support for Windows and eventually > Hyper-V deployment of MirageOS unikernels. > > My end goal is getting MirageOS unikernels running on Windows Azure, as it > would seem having ubiquitous > cloud hosting support would be very valuable to the project. For now it > seems like having just plain Windows process > support would be a great stepping stone to this eventual goal. > > > Hi Brian, > > Glad to hear you're interested in working on this! Windows support has > been oft-asked for, but noone's explicitly started doing anything in this > direction yet. > > One approach for Azure support that's been pointed out a few times is > adding UEFI bootloader support; see > https://github.com/mirage/mirage/issues/187 > > However, it would certainly be easier to start with good userspace support > before delving into the kernel mode. > > I've been poking around the code, and see that everything seems to be > partitioned cleanly into separate packages for > xen and unix support. This gives me at least a little hope that windows / > hyper-v support could be added piecemeal > overtime without being a merging nightmare as development continues to > occur. > > Very impressed with the clean isolation :) > > As far as I can tell it seems like I would have to implement the following > opam packages to get windows process support working: > > 1) mirage-win Mirage OS library for Windows compilation > 2) mirage-console-win A Mirage-compatible Console library for Windows > 3) mirage-clock-win A Mirage-compatible Clock library for Windows > 4) mirage-entropy-win Mirage entropy device for Windows > 5) mirage-block-win Mirage block driver for Windows > 6) mirage-fs-win Mirage file system pass through driver for > Windows > 7) mirage-net-win Ethernet network driver for Mirage (seems > like this might be optional?) > 8) mirage-tcpip-win Userlevel TCP/IP stack > 9) mirage-http-win Mirage HTTP client and server driver for > Windows > > The root mirage package 'mirage' would also have to be modified to support > a --win option, and other plumbing. > > Conceptually this all seems fine and dandy, be it a reasonably large chunk > of work. > > > I'm not intimately familiar with the ocaml ecosystem on windows, I've only > ever dabbled in the language > on unix machines. This leads be to wonder if Windows support for MirageOS > is dead on arrival, given the > current windows support the tooling MirageOS fundamentally uses. For > instance it seems like currently > even opam doesn't support running on windows? (I read that it is coming..) > I imagine there are many > other such cases, that I simply won't know about until I hit them. > > Am I mistaken, or is windows support for the tooling going to be a big > blocker to getting anything working? > > > This is exactly the right analysis -- the package breakup is correct, but > the existing approach to doing build will make things hard to compile on > Windows, I suspect. However, we are working on a package description > system called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzli) > that should simplify build of Mirage packages considerably. The current > interface is being revved and isn't finalised, but it should be fairly > simple to ensure that the Makefiles that it generates are Windows compliant. > > Which leads onto the second point -- it would be very useful to establish > an absolute minimal set of libraries to get started with having a Windows > environment on which to build upon. For Mirage, this is just the hello > world example with mirage-win and mirage-console-win (and possibly the > clock). Getting these ported requires selecting the preferred toolchain > (mingw, Cygwin, MSVC?) and ensuring that OCaml itself is happy with the > setup. > > Once a console port works, the rest is just a matter of filling in the > library blanks, just as we did over the years with the existing *nix and > Xen backends. > > [1] https://github.com/samoht/assemblage > > best, > Anil > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --f46d041826c6d0f3cd0503a608f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Anil,

Doesn't Mirage depend on the = Jane Street Core which has not yet been ported to Windows?=C2=A0 Or maybe I= am mistaken.

The more platforms that accept Mirag= e the better in my opinion.

Cheers

<= /div>
--Stephen

On Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy <anil@reco= il.org> wrote:
On 19 Sep 2014, at 22:41, Brian = Gianforcaro <b.g= ianfo@gmail.com> wrote:

Hello All,

I'm interested in= working on adding support for Windows and eventually Hyper-V deployment of= MirageOS unikernels.

My end goal is getting MirageOS unikernels ru= nning on Windows Azure, as it would seem having ubiquitous
cloud hostin= g support would be very valuable to the project. For now it seems like havi= ng just plain Windows process
support would be a great stepping stone to= this eventual goal.=C2=A0

Hi B= rian,

Glad to hear you're interested in workin= g on this!=C2=A0 Windows support has been oft-asked for, but noone's ex= plicitly started doing anything in this direction yet.

=
One approach for Azure support that's been pointed out a few times= is adding UEFI bootloader support; see=C2=A0https://github.com/mirage/mirag= e/issues/187

However, it would certainly be ea= sier to start with good userspace support before delving into the kernel mo= de.

I've been poking around the code, and see that everything seems to b= e partitioned cleanly into separate packages for
xen and unix support. = This gives me at least a little hope that windows / hyper-v support could b= e added piecemeal=C2=A0
overtime without being a merging nightmar= e as development continues to occur.

Very impressed with the clean i= solation :)

As far as I can tell it seems like I would have to impl= ement the following opam packages to get windows process support working: <= br>
=C2=A0 1) mirage-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0Mirage OS library for Windows compilation
=C2=A0 2) mirage-con= sole-win =C2=A0 A Mirage-compatible Console library for Windows
=C2=A0 3= ) mirage-clock-win =C2=A0 =C2=A0 =C2=A0 A Mirage-compatible Clock library f= or Windows
=C2=A0 4) mirage-entropy-win =C2=A0 Mirage entropy device for= Windows
=C2=A0 5) mirage-block-win =C2=A0 =C2=A0 =C2=A0 Mirage block dr= iver for Windows
=C2=A0 6) mirage-fs-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0Mirage file system pass through driver for Windows
=C2=A0 7) m= irage-net-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ethernet network driver for= Mirage (seems like this might be optional?)
=C2=A0 8) mirage-tcpip-win = =C2=A0 =C2=A0 =C2=A0 Userlevel TCP/IP stack
=C2=A0 9) mirage-http-win = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mirage HTTP client and server driver for Window= s

The root mirage package 'mirage' would also have to be mod= ified to support a --win option, and other plumbing.=C2=A0

Conceptua= lly this all seems fine and dandy, be it a reasonably large chunk of work.= =C2=A0
<= div>
I'm not intimately familiar with the ocaml ecosystem on windows= , I've only ever dabbled in the language
on unix machines. This lead= s be to wonder if Windows support for MirageOS is dead on arrival, given th= e
current windows support the tooling MirageOS fundamentally uses. For i= nstance it seems like currently
even opam doesn't support running o= n windows? (I read that it is coming..) I imagine there are many
other = such cases, that I simply won't know about until I hit them.

Am = I mistaken, or is windows support for the tooling going to be a big blocker= to getting anything working?

This is exactly the right analysis -- the package breakup is correct, = but the existing approach to doing build will make things hard to compile o= n Windows, I suspect.=C2=A0 However, we are working on a package descriptio= n system called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzl= i) that should simplify build of Mirage packages considerably. The current = interface is being revved and isn't finalised, but it should be fairly = simple to ensure that the Makefiles that it generates are Windows compliant= .

Which leads onto the second point -- it would be= very useful to establish an absolute minimal set of libraries to get start= ed with having a Windows environment on which to build upon.=C2=A0 For Mira= ge, this is just the hello world example with mirage-win and mirage-console= -win (and possibly the clock). Getting these ported requires selecting the = preferred toolchain (mingw, Cygwin, MSVC?) and ensuring that OCaml itself i= s happy with the setup.

Once a console port works,= the rest is just a matter of filling in the library blanks, just as we did= over the years with the existing *nix and Xen backends.


best,<= /div>
Anil

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


--f46d041826c6d0f3cd0503a608f3-- --===============6727954086917804729== 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 --===============6727954086917804729==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 11:49:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 11:49: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 1XW26w-0007WS-Si; Mon, 22 Sep 2014 11:48:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XW26v-0007WN-Es for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 11:48:53 +0000 Received: from [85.158.139.211:36763] by server-2.bemta-5.messagelabs.com id C1/00-31832-4AC00245; Mon, 22 Sep 2014 11:48:52 +0000 X-Env-Sender: smack815@gmail.com X-Msg-Ref: server-9.tower-206.messagelabs.com!1411386531!11252166!1 X-Originating-IP: [74.125.82.177] 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.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16412 invoked from network); 22 Sep 2014 11:48:51 -0000 Received: from mail-we0-f177.google.com (HELO mail-we0-f177.google.com) (74.125.82.177) by server-9.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 22 Sep 2014 11:48:51 -0000 Received: by mail-we0-f177.google.com with SMTP id t60so2705883wes.8 for ; Mon, 22 Sep 2014 04:48:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qGPgFsMpbhydY739yi6qaOiQXO5c0JL9C3PAzqGWKEM=; b=uSO3sJ3mcJkvF6Bu+wbGXQhUicE/5R2lJtEkk7oQUfyHSMNLuwAXQ/LjtK1D0dduzg EOvldNrmJqmTLTaiOS0lZtYsM4XiZi5wP4GFnF2DjDShgt6BrAbCmnEJhTKHOnO5GiMt EVbH1mvoHWNFWR8AEr8/TuY/YYJVJjLApHogvwbRsuceRE3M1NyhyHDBjq/GuiTdkjaw wvmMTxHTzOjpd+iuXCHAmqoCScupH+a+RsA8PBhPFoch+nif/L6dlz2vNgfBH9xGoiWc EFgaHZHBTDMERtdakNVYdIITPGy4rq+HTQON/4z3zot3eCyKrEcBG3Il1/Ev+Hmq4Bp2 e8bQ== MIME-Version: 1.0 X-Received: by 10.180.101.40 with SMTP id fd8mr2405791wib.63.1411386530917; Mon, 22 Sep 2014 04:48:50 -0700 (PDT) Received: by 10.180.149.205 with HTTP; Mon, 22 Sep 2014 04:48:50 -0700 (PDT) In-Reply-To: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> References: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> Date: Mon, 22 Sep 2014 08:48:50 -0300 Message-ID: From: Stephen Mack To: Anil Madhavapeddy Cc: Brian Gianforcaro , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6727954086917804729==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6727954086917804729== Content-Type: multipart/alternative; boundary=f46d041826c6d0f3cd0503a608f3 --f46d041826c6d0f3cd0503a608f3 Content-Type: text/plain; charset=UTF-8 Anil, Doesn't Mirage depend on the Jane Street Core which has not yet been ported to Windows? Or maybe I am mistaken. The more platforms that accept Mirage the better in my opinion. Cheers --Stephen On Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy wrote: > On 19 Sep 2014, at 22:41, Brian Gianforcaro wrote: > > Hello All, > > I'm interested in working on adding support for Windows and eventually > Hyper-V deployment of MirageOS unikernels. > > My end goal is getting MirageOS unikernels running on Windows Azure, as it > would seem having ubiquitous > cloud hosting support would be very valuable to the project. For now it > seems like having just plain Windows process > support would be a great stepping stone to this eventual goal. > > > Hi Brian, > > Glad to hear you're interested in working on this! Windows support has > been oft-asked for, but noone's explicitly started doing anything in this > direction yet. > > One approach for Azure support that's been pointed out a few times is > adding UEFI bootloader support; see > https://github.com/mirage/mirage/issues/187 > > However, it would certainly be easier to start with good userspace support > before delving into the kernel mode. > > I've been poking around the code, and see that everything seems to be > partitioned cleanly into separate packages for > xen and unix support. This gives me at least a little hope that windows / > hyper-v support could be added piecemeal > overtime without being a merging nightmare as development continues to > occur. > > Very impressed with the clean isolation :) > > As far as I can tell it seems like I would have to implement the following > opam packages to get windows process support working: > > 1) mirage-win Mirage OS library for Windows compilation > 2) mirage-console-win A Mirage-compatible Console library for Windows > 3) mirage-clock-win A Mirage-compatible Clock library for Windows > 4) mirage-entropy-win Mirage entropy device for Windows > 5) mirage-block-win Mirage block driver for Windows > 6) mirage-fs-win Mirage file system pass through driver for > Windows > 7) mirage-net-win Ethernet network driver for Mirage (seems > like this might be optional?) > 8) mirage-tcpip-win Userlevel TCP/IP stack > 9) mirage-http-win Mirage HTTP client and server driver for > Windows > > The root mirage package 'mirage' would also have to be modified to support > a --win option, and other plumbing. > > Conceptually this all seems fine and dandy, be it a reasonably large chunk > of work. > > > I'm not intimately familiar with the ocaml ecosystem on windows, I've only > ever dabbled in the language > on unix machines. This leads be to wonder if Windows support for MirageOS > is dead on arrival, given the > current windows support the tooling MirageOS fundamentally uses. For > instance it seems like currently > even opam doesn't support running on windows? (I read that it is coming..) > I imagine there are many > other such cases, that I simply won't know about until I hit them. > > Am I mistaken, or is windows support for the tooling going to be a big > blocker to getting anything working? > > > This is exactly the right analysis -- the package breakup is correct, but > the existing approach to doing build will make things hard to compile on > Windows, I suspect. However, we are working on a package description > system called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzli) > that should simplify build of Mirage packages considerably. The current > interface is being revved and isn't finalised, but it should be fairly > simple to ensure that the Makefiles that it generates are Windows compliant. > > Which leads onto the second point -- it would be very useful to establish > an absolute minimal set of libraries to get started with having a Windows > environment on which to build upon. For Mirage, this is just the hello > world example with mirage-win and mirage-console-win (and possibly the > clock). Getting these ported requires selecting the preferred toolchain > (mingw, Cygwin, MSVC?) and ensuring that OCaml itself is happy with the > setup. > > Once a console port works, the rest is just a matter of filling in the > library blanks, just as we did over the years with the existing *nix and > Xen backends. > > [1] https://github.com/samoht/assemblage > > best, > Anil > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --f46d041826c6d0f3cd0503a608f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Anil,

Doesn't Mirage depend on the = Jane Street Core which has not yet been ported to Windows?=C2=A0 Or maybe I= am mistaken.

The more platforms that accept Mirag= e the better in my opinion.

Cheers

<= /div>
--Stephen

On Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy <anil@reco= il.org> wrote:
On 19 Sep 2014, at 22:41, Brian = Gianforcaro <b.g= ianfo@gmail.com> wrote:

Hello All,

I'm interested in= working on adding support for Windows and eventually Hyper-V deployment of= MirageOS unikernels.

My end goal is getting MirageOS unikernels ru= nning on Windows Azure, as it would seem having ubiquitous
cloud hostin= g support would be very valuable to the project. For now it seems like havi= ng just plain Windows process
support would be a great stepping stone to= this eventual goal.=C2=A0

Hi B= rian,

Glad to hear you're interested in workin= g on this!=C2=A0 Windows support has been oft-asked for, but noone's ex= plicitly started doing anything in this direction yet.

=
One approach for Azure support that's been pointed out a few times= is adding UEFI bootloader support; see=C2=A0https://github.com/mirage/mirag= e/issues/187

However, it would certainly be ea= sier to start with good userspace support before delving into the kernel mo= de.

I've been poking around the code, and see that everything seems to b= e partitioned cleanly into separate packages for
xen and unix support. = This gives me at least a little hope that windows / hyper-v support could b= e added piecemeal=C2=A0
overtime without being a merging nightmar= e as development continues to occur.

Very impressed with the clean i= solation :)

As far as I can tell it seems like I would have to impl= ement the following opam packages to get windows process support working: <= br>
=C2=A0 1) mirage-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0Mirage OS library for Windows compilation
=C2=A0 2) mirage-con= sole-win =C2=A0 A Mirage-compatible Console library for Windows
=C2=A0 3= ) mirage-clock-win =C2=A0 =C2=A0 =C2=A0 A Mirage-compatible Clock library f= or Windows
=C2=A0 4) mirage-entropy-win =C2=A0 Mirage entropy device for= Windows
=C2=A0 5) mirage-block-win =C2=A0 =C2=A0 =C2=A0 Mirage block dr= iver for Windows
=C2=A0 6) mirage-fs-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0Mirage file system pass through driver for Windows
=C2=A0 7) m= irage-net-win =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Ethernet network driver for= Mirage (seems like this might be optional?)
=C2=A0 8) mirage-tcpip-win = =C2=A0 =C2=A0 =C2=A0 Userlevel TCP/IP stack
=C2=A0 9) mirage-http-win = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Mirage HTTP client and server driver for Window= s

The root mirage package 'mirage' would also have to be mod= ified to support a --win option, and other plumbing.=C2=A0

Conceptua= lly this all seems fine and dandy, be it a reasonably large chunk of work.= =C2=A0
<= div>
I'm not intimately familiar with the ocaml ecosystem on windows= , I've only ever dabbled in the language
on unix machines. This lead= s be to wonder if Windows support for MirageOS is dead on arrival, given th= e
current windows support the tooling MirageOS fundamentally uses. For i= nstance it seems like currently
even opam doesn't support running o= n windows? (I read that it is coming..) I imagine there are many
other = such cases, that I simply won't know about until I hit them.

Am = I mistaken, or is windows support for the tooling going to be a big blocker= to getting anything working?

This is exactly the right analysis -- the package breakup is correct, = but the existing approach to doing build will make things hard to compile o= n Windows, I suspect.=C2=A0 However, we are working on a package descriptio= n system called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzl= i) that should simplify build of Mirage packages considerably. The current = interface is being revved and isn't finalised, but it should be fairly = simple to ensure that the Makefiles that it generates are Windows compliant= .

Which leads onto the second point -- it would be= very useful to establish an absolute minimal set of libraries to get start= ed with having a Windows environment on which to build upon.=C2=A0 For Mira= ge, this is just the hello world example with mirage-win and mirage-console= -win (and possibly the clock). Getting these ported requires selecting the = preferred toolchain (mingw, Cygwin, MSVC?) and ensuring that OCaml itself i= s happy with the setup.

Once a console port works,= the rest is just a matter of filling in the library blanks, just as we did= over the years with the existing *nix and Xen backends.


best,<= /div>
Anil

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


--f46d041826c6d0f3cd0503a608f3-- --===============6727954086917804729== 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 --===============6727954086917804729==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 12:36:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 12:36: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 1XW2qe-0001Qb-P2; Mon, 22 Sep 2014 12:36:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XW2qd-0001QT-Fr for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 12:36:07 +0000 Received: from [85.158.137.68:50293] by server-16.bemta-3.messagelabs.com id C5/72-01431-6B710245; Mon, 22 Sep 2014 12:36:06 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-31.messagelabs.com!1411389364!11175719!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22251 invoked from network); 22 Sep 2014 12:36:05 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2014 12:36:05 -0000 Received: from [10.0.0.110] (host81-149-102-120.in-addr.btopenworld.com [81.149.102.120]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id d90869ed; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 22 Sep 2014 13:37:08 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 22 Sep 2014 13:36:01 +0100 Message-Id: <625F90FF-C18F-432B-931B-81AE0BAF837A@recoil.org> References: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) Cc: Brian Gianforcaro , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7232021185123270718==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7232021185123270718== Content-Type: multipart/alternative; boundary="Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E" --Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii None of the Mirage libraries listed below depend on Jane Street Core. = You may be thinking of the Irmin database, which isn't one of the = essential libraries, and that dependency is being made optional there as = well. best, Anil On 22 Sep 2014, at 12:48, Stephen Mack wrote: > Anil, >=20 > Doesn't Mirage depend on the Jane Street Core which has not yet been = ported to Windows? Or maybe I am mistaken. >=20 > The more platforms that accept Mirage the better in my opinion. >=20 > Cheers >=20 > --Stephen >=20 > On Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy = wrote: > On 19 Sep 2014, at 22:41, Brian Gianforcaro = wrote: >=20 >> Hello All,=20 >>=20 >> I'm interested in working on adding support for Windows and = eventually Hyper-V deployment of MirageOS unikernels.=20 >>=20 >> My end goal is getting MirageOS unikernels running on Windows Azure, = as it would seem having ubiquitous=20 >> cloud hosting support would be very valuable to the project. For now = it seems like having just plain Windows process >> support would be a great stepping stone to this eventual goal.=20 >=20 > Hi Brian, >=20 > Glad to hear you're interested in working on this! Windows support = has been oft-asked for, but noone's explicitly started doing anything in = this direction yet. >=20 > One approach for Azure support that's been pointed out a few times is = adding UEFI bootloader support; see = https://github.com/mirage/mirage/issues/187 >=20 > However, it would certainly be easier to start with good userspace = support before delving into the kernel mode. >=20 >> I've been poking around the code, and see that everything seems to be = partitioned cleanly into separate packages for >> xen and unix support. This gives me at least a little hope that = windows / hyper-v support could be added piecemeal=20 >> overtime without being a merging nightmare as development continues = to occur. >>=20 >> Very impressed with the clean isolation :)=20 >>=20 >> As far as I can tell it seems like I would have to implement the = following opam packages to get windows process support working:=20 >>=20 >> 1) mirage-win Mirage OS library for Windows = compilation >> 2) mirage-console-win A Mirage-compatible Console library for = Windows >> 3) mirage-clock-win A Mirage-compatible Clock library for = Windows >> 4) mirage-entropy-win Mirage entropy device for Windows >> 5) mirage-block-win Mirage block driver for Windows >> 6) mirage-fs-win Mirage file system pass through driver = for Windows >> 7) mirage-net-win Ethernet network driver for Mirage = (seems like this might be optional?) >> 8) mirage-tcpip-win Userlevel TCP/IP stack >> 9) mirage-http-win Mirage HTTP client and server driver for = Windows >>=20 >> The root mirage package 'mirage' would also have to be modified to = support a --win option, and other plumbing.=20 >>=20 >> Conceptually this all seems fine and dandy, be it a reasonably large = chunk of work.=20 >>=20 >> I'm not intimately familiar with the ocaml ecosystem on windows, I've = only ever dabbled in the language >> on unix machines. This leads be to wonder if Windows support for = MirageOS is dead on arrival, given the >> current windows support the tooling MirageOS fundamentally uses. For = instance it seems like currently=20 >> even opam doesn't support running on windows? (I read that it is = coming..) I imagine there are many=20 >> other such cases, that I simply won't know about until I hit them. >>=20 >> Am I mistaken, or is windows support for the tooling going to be a = big blocker to getting anything working? >=20 > This is exactly the right analysis -- the package breakup is correct, = but the existing approach to doing build will make things hard to = compile on Windows, I suspect. However, we are working on a package = description system called Assemblage [1] (lead by Thomas Gazagnaire and = Daniel Buenzli) that should simplify build of Mirage packages = considerably. The current interface is being revved and isn't finalised, = but it should be fairly simple to ensure that the Makefiles that it = generates are Windows compliant. >=20 > Which leads onto the second point -- it would be very useful to = establish an absolute minimal set of libraries to get started with = having a Windows environment on which to build upon. For Mirage, this = is just the hello world example with mirage-win and mirage-console-win = (and possibly the clock). Getting these ported requires selecting the = preferred toolchain (mingw, Cygwin, MSVC?) and ensuring that OCaml = itself is happy with the setup. >=20 > Once a console port works, the rest is just a matter of filling in the = library blanks, just as we did over the years with the existing *nix and = Xen backends. >=20 > [1] https://github.com/samoht/assemblage >=20 > best, > Anil >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 --Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii None = of the Mirage libraries listed below depend on Jane Street Core. =  You may be thinking of the Irmin database, which isn't one of the = essential libraries, and that dependency is being made optional there as = well.

best,
Anil

On 22 Sep 2014, at 12:48, Stephen Mack <smack815@gmail.com> = wrote:

Anil,

Doesn't Mirage = depend on the Jane Street Core which has not yet been ported to = Windows?  Or maybe I am mistaken.

The more = platforms that accept Mirage the better in my = opinion.

Cheers

--Stephe= n

On = Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
On 19 Sep 2014, at 22:41, Brian Gianforcaro <b.gianfo@gmail.com> wrote:

Hello All, =

I'm interested in working on adding support for Windows and = eventually Hyper-V deployment of MirageOS unikernels.

My end = goal is getting MirageOS unikernels running on Windows Azure, as it = would seem having ubiquitous
cloud hosting support would be very = valuable to the project. For now it seems like having just plain Windows = process
support would be a great stepping stone to this eventual = goal. 

Hi = Brian,

Glad to hear you're interested in = working on this!  Windows support has been oft-asked for, but = noone's explicitly started doing anything in this direction = yet.

One approach for Azure support that's been = pointed out a few times is adding UEFI bootloader support; see https://github.com/mirage/mirage/issues/187

However, it would certainly be easier to start with = good userspace support before delving into the kernel = mode.

I've been poking around the code, and see that everything = seems to be partitioned cleanly into separate packages for
xen and = unix support. This gives me at least a little hope that windows / = hyper-v support could be added piecemeal 
overtime = without being a merging nightmare as development continues to = occur.

Very impressed with the clean isolation :)

As far = as I can tell it seems like I would have to implement the following opam = packages to get windows process support working:

  1) = mirage-win                Mirage = OS library for Windows compilation
  2) mirage-console-win =   A Mirage-compatible Console library for Windows
  3) = mirage-clock-win       A Mirage-compatible Clock library = for Windows
  4) mirage-entropy-win   Mirage entropy device = for Windows
  5) mirage-block-win       Mirage = block driver for Windows
  6) mirage-fs-win       =      Mirage file system pass through driver for = Windows
  7) mirage-net-win         =  Ethernet network driver for Mirage (seems like this might be = optional?)
  8) mirage-tcpip-win       Userlevel = TCP/IP stack
  9) mirage-http-win         = Mirage HTTP client and server driver for Windows

The root mirage = package 'mirage' would also have to be modified to support a --win = option, and other plumbing. 

Conceptually this all seems = fine and dandy, be it a reasonably large chunk of = work. 

I'm not intimately familiar with the ocaml ecosystem on = windows, I've only ever dabbled in the language
on unix machines. = This leads be to wonder if Windows support for MirageOS is dead on = arrival, given the
current windows support the tooling MirageOS = fundamentally uses. For instance it seems like currently
even opam = doesn't support running on windows? (I read that it is coming..) I = imagine there are many
other such cases, that I simply won't know = about until I hit them.

Am I mistaken, or is windows support for = the tooling going to be a big blocker to getting anything = working?

This is exactly the = right analysis -- the package breakup is correct, but the existing = approach to doing build will make things hard to compile on Windows, I = suspect.  However, we are working on a package description system = called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzli) = that should simplify build of Mirage packages considerably. The current = interface is being revved and isn't finalised, but it should be fairly = simple to ensure that the Makefiles that it generates are Windows = compliant.

Which leads onto the second point -- = it would be very useful to establish an absolute minimal set of = libraries to get started with having a Windows environment on which to = build upon.  For Mirage, this is just the hello world example with = mirage-win and mirage-console-win (and possibly the clock). Getting = these ported requires selecting the preferred toolchain (mingw, Cygwin, = MSVC?) and ensuring that OCaml itself is happy with the = setup.

Once a console port works, the rest is = just a matter of filling in the library blanks, just as we did over the = years with the existing *nix and Xen = backends.


<= /div>
best,
Anil

____________________________= ___________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



= --Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E-- --===============7232021185123270718== 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 --===============7232021185123270718==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 22 12:36:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 22 Sep 2014 12:36: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 1XW2qe-0001Qb-P2; Mon, 22 Sep 2014 12:36:08 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XW2qd-0001QT-Fr for mirageos-devel@lists.xenproject.org; Mon, 22 Sep 2014 12:36:07 +0000 Received: from [85.158.137.68:50293] by server-16.bemta-3.messagelabs.com id C5/72-01431-6B710245; Mon, 22 Sep 2014 12:36:06 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-31.messagelabs.com!1411389364!11175719!1 X-Originating-IP: [5.153.225.51] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_30_40,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR,RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22251 invoked from network); 22 Sep 2014 12:36:05 -0000 Received: from bark.recoil.org (HELO bark.recoil.org) (5.153.225.51) by server-12.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 22 Sep 2014 12:36:05 -0000 Received: from [10.0.0.110] (host81-149-102-120.in-addr.btopenworld.com [81.149.102.120]); by bark.recoil.org (OpenSMTPD) with ESMTPSA id d90869ed; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO; Mon, 22 Sep 2014 13:37:08 +0100 (BST) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 22 Sep 2014 13:36:01 +0100 Message-Id: <625F90FF-C18F-432B-931B-81AE0BAF837A@recoil.org> References: <69E67813-119A-48E5-A096-061695F896CA@recoil.org> To: Stephen Mack X-Mailer: Apple Mail (2.1878.6) Cc: Brian Gianforcaro , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] MirageOS Windows / Hyper-V Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7232021185123270718==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7232021185123270718== Content-Type: multipart/alternative; boundary="Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E" --Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii None of the Mirage libraries listed below depend on Jane Street Core. = You may be thinking of the Irmin database, which isn't one of the = essential libraries, and that dependency is being made optional there as = well. best, Anil On 22 Sep 2014, at 12:48, Stephen Mack wrote: > Anil, >=20 > Doesn't Mirage depend on the Jane Street Core which has not yet been = ported to Windows? Or maybe I am mistaken. >=20 > The more platforms that accept Mirage the better in my opinion. >=20 > Cheers >=20 > --Stephen >=20 > On Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy = wrote: > On 19 Sep 2014, at 22:41, Brian Gianforcaro = wrote: >=20 >> Hello All,=20 >>=20 >> I'm interested in working on adding support for Windows and = eventually Hyper-V deployment of MirageOS unikernels.=20 >>=20 >> My end goal is getting MirageOS unikernels running on Windows Azure, = as it would seem having ubiquitous=20 >> cloud hosting support would be very valuable to the project. For now = it seems like having just plain Windows process >> support would be a great stepping stone to this eventual goal.=20 >=20 > Hi Brian, >=20 > Glad to hear you're interested in working on this! Windows support = has been oft-asked for, but noone's explicitly started doing anything in = this direction yet. >=20 > One approach for Azure support that's been pointed out a few times is = adding UEFI bootloader support; see = https://github.com/mirage/mirage/issues/187 >=20 > However, it would certainly be easier to start with good userspace = support before delving into the kernel mode. >=20 >> I've been poking around the code, and see that everything seems to be = partitioned cleanly into separate packages for >> xen and unix support. This gives me at least a little hope that = windows / hyper-v support could be added piecemeal=20 >> overtime without being a merging nightmare as development continues = to occur. >>=20 >> Very impressed with the clean isolation :)=20 >>=20 >> As far as I can tell it seems like I would have to implement the = following opam packages to get windows process support working:=20 >>=20 >> 1) mirage-win Mirage OS library for Windows = compilation >> 2) mirage-console-win A Mirage-compatible Console library for = Windows >> 3) mirage-clock-win A Mirage-compatible Clock library for = Windows >> 4) mirage-entropy-win Mirage entropy device for Windows >> 5) mirage-block-win Mirage block driver for Windows >> 6) mirage-fs-win Mirage file system pass through driver = for Windows >> 7) mirage-net-win Ethernet network driver for Mirage = (seems like this might be optional?) >> 8) mirage-tcpip-win Userlevel TCP/IP stack >> 9) mirage-http-win Mirage HTTP client and server driver for = Windows >>=20 >> The root mirage package 'mirage' would also have to be modified to = support a --win option, and other plumbing.=20 >>=20 >> Conceptually this all seems fine and dandy, be it a reasonably large = chunk of work.=20 >>=20 >> I'm not intimately familiar with the ocaml ecosystem on windows, I've = only ever dabbled in the language >> on unix machines. This leads be to wonder if Windows support for = MirageOS is dead on arrival, given the >> current windows support the tooling MirageOS fundamentally uses. For = instance it seems like currently=20 >> even opam doesn't support running on windows? (I read that it is = coming..) I imagine there are many=20 >> other such cases, that I simply won't know about until I hit them. >>=20 >> Am I mistaken, or is windows support for the tooling going to be a = big blocker to getting anything working? >=20 > This is exactly the right analysis -- the package breakup is correct, = but the existing approach to doing build will make things hard to = compile on Windows, I suspect. However, we are working on a package = description system called Assemblage [1] (lead by Thomas Gazagnaire and = Daniel Buenzli) that should simplify build of Mirage packages = considerably. The current interface is being revved and isn't finalised, = but it should be fairly simple to ensure that the Makefiles that it = generates are Windows compliant. >=20 > Which leads onto the second point -- it would be very useful to = establish an absolute minimal set of libraries to get started with = having a Windows environment on which to build upon. For Mirage, this = is just the hello world example with mirage-win and mirage-console-win = (and possibly the clock). Getting these ported requires selecting the = preferred toolchain (mingw, Cygwin, MSVC?) and ensuring that OCaml = itself is happy with the setup. >=20 > Once a console port works, the rest is just a matter of filling in the = library blanks, just as we did over the years with the existing *nix and = Xen backends. >=20 > [1] https://github.com/samoht/assemblage >=20 > best, > Anil >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 --Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii None = of the Mirage libraries listed below depend on Jane Street Core. =  You may be thinking of the Irmin database, which isn't one of the = essential libraries, and that dependency is being made optional there as = well.

best,
Anil

On 22 Sep 2014, at 12:48, Stephen Mack <smack815@gmail.com> = wrote:

Anil,

Doesn't Mirage = depend on the Jane Street Core which has not yet been ported to = Windows?  Or maybe I am mistaken.

The more = platforms that accept Mirage the better in my = opinion.

Cheers

--Stephe= n

On = Mon, Sep 22, 2014 at 5:10 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
On 19 Sep 2014, at 22:41, Brian Gianforcaro <b.gianfo@gmail.com> wrote:

Hello All, =

I'm interested in working on adding support for Windows and = eventually Hyper-V deployment of MirageOS unikernels.

My end = goal is getting MirageOS unikernels running on Windows Azure, as it = would seem having ubiquitous
cloud hosting support would be very = valuable to the project. For now it seems like having just plain Windows = process
support would be a great stepping stone to this eventual = goal. 

Hi = Brian,

Glad to hear you're interested in = working on this!  Windows support has been oft-asked for, but = noone's explicitly started doing anything in this direction = yet.

One approach for Azure support that's been = pointed out a few times is adding UEFI bootloader support; see https://github.com/mirage/mirage/issues/187

However, it would certainly be easier to start with = good userspace support before delving into the kernel = mode.

I've been poking around the code, and see that everything = seems to be partitioned cleanly into separate packages for
xen and = unix support. This gives me at least a little hope that windows / = hyper-v support could be added piecemeal 
overtime = without being a merging nightmare as development continues to = occur.

Very impressed with the clean isolation :)

As far = as I can tell it seems like I would have to implement the following opam = packages to get windows process support working:

  1) = mirage-win                Mirage = OS library for Windows compilation
  2) mirage-console-win =   A Mirage-compatible Console library for Windows
  3) = mirage-clock-win       A Mirage-compatible Clock library = for Windows
  4) mirage-entropy-win   Mirage entropy device = for Windows
  5) mirage-block-win       Mirage = block driver for Windows
  6) mirage-fs-win       =      Mirage file system pass through driver for = Windows
  7) mirage-net-win         =  Ethernet network driver for Mirage (seems like this might be = optional?)
  8) mirage-tcpip-win       Userlevel = TCP/IP stack
  9) mirage-http-win         = Mirage HTTP client and server driver for Windows

The root mirage = package 'mirage' would also have to be modified to support a --win = option, and other plumbing. 

Conceptually this all seems = fine and dandy, be it a reasonably large chunk of = work. 

I'm not intimately familiar with the ocaml ecosystem on = windows, I've only ever dabbled in the language
on unix machines. = This leads be to wonder if Windows support for MirageOS is dead on = arrival, given the
current windows support the tooling MirageOS = fundamentally uses. For instance it seems like currently
even opam = doesn't support running on windows? (I read that it is coming..) I = imagine there are many
other such cases, that I simply won't know = about until I hit them.

Am I mistaken, or is windows support for = the tooling going to be a big blocker to getting anything = working?

This is exactly the = right analysis -- the package breakup is correct, but the existing = approach to doing build will make things hard to compile on Windows, I = suspect.  However, we are working on a package description system = called Assemblage [1] (lead by Thomas Gazagnaire and Daniel Buenzli) = that should simplify build of Mirage packages considerably. The current = interface is being revved and isn't finalised, but it should be fairly = simple to ensure that the Makefiles that it generates are Windows = compliant.

Which leads onto the second point -- = it would be very useful to establish an absolute minimal set of = libraries to get started with having a Windows environment on which to = build upon.  For Mirage, this is just the hello world example with = mirage-win and mirage-console-win (and possibly the clock). Getting = these ported requires selecting the preferred toolchain (mingw, Cygwin, = MSVC?) and ensuring that OCaml itself is happy with the = setup.

Once a console port works, the rest is = just a matter of filling in the library blanks, just as we did over the = years with the existing *nix and Xen = backends.


<= /div>
best,
Anil

____________________________= ___________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



= --Apple-Mail=_97314947-2EF6-4DEE-8E99-580C4030088E-- --===============7232021185123270718== 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 --===============7232021185123270718==-- From mirageos-devel-bounces@lists.xenproject.org Tue Sep 23 01:45:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 23 Sep 2014 01:45:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWFAn-0007Ve-Vy; Tue, 23 Sep 2014 01:45:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWFAm-0007V9-2D for mirageos-devel@lists.xenproject.org; Tue, 23 Sep 2014 01:45:44 +0000 Received: from [85.158.143.35:12873] by server-2.bemta-4.messagelabs.com id A7/68-04525-7C0D0245; Tue, 23 Sep 2014 01:45:43 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1411436742!4462126!1 X-Originating-IP: [209.85.217.170] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20715 invoked from network); 23 Sep 2014 01:45:42 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 23 Sep 2014 01:45:42 -0000 Received: by mail-lb0-f170.google.com with SMTP id z11so2470502lbi.1 for ; Mon, 22 Sep 2014 18:45:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=x2sE08rfhWw7VX4MwIyCyNS8vb0H9sW+RAgsqBYOBDQ=; b=gvyyiNElSzDweHg62ve2nE6MPG5T6Vz9dmRbIU/pyV1OoELSQrg8kQ8Pm5kPRCQA/U XjHKYiqz7lqGXxz1Fssdml4WVMqo2bYg/iIIQ+Gl3xOAml3rPlMJg0GrIiEHA/ZaKe+I kJZNbCQE+q2jvuB1KX8Y0L4F5t9jq5D0O5SXHxiJkSly1lIMmE9p2iwEBEcrNShr2sTQ pSuX0XQlxrl7VQzD9cCmtqzE9aqPdQJ8hsKaAKnAjj1BZkUeuCdwLdZm49Ei8sXN+p/i XDAsjsmibNqV5bWB3vLH9z29WAoB21Lg0U7gG96ERX7axsuuSveTsPf2NSfQm+XafAN0 0DkQ== MIME-Version: 1.0 X-Received: by 10.152.7.145 with SMTP id j17mr6445195laa.77.1411436741632; Mon, 22 Sep 2014 18:45:41 -0700 (PDT) Received: by 10.112.12.225 with HTTP; Mon, 22 Sep 2014 18:45:41 -0700 (PDT) Date: Mon, 22 Sep 2014 21:45:41 -0400 X-Google-Sender-Auth: GqTNUZ_sn35gpQIUUY4BuOq8SDI Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] This Wednesday is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.org 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 This is a reminder that this Wednesday, September 24, is Xen Project Document Day. Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki. -- ATTENTION DEVELOPER AND USER SUMMIT ATTENDEES -- You've been part of some great talks in the past few weeks. Do the Wiki pages reflect what was presented? If the information is on another project's Wiki, can you locate that information from our Wiki? No? Well, Wednesday is the day to make it happen! All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments before Wednesday, please take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO So please think about how you can help out. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you Wednesday in #xendocs! _______________________________________________ MirageOS-devel 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 Sep 23 01:45:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 23 Sep 2014 01:45:52 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWFAn-0007Ve-Vy; Tue, 23 Sep 2014 01:45:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWFAm-0007V9-2D for mirageos-devel@lists.xenproject.org; Tue, 23 Sep 2014 01:45:44 +0000 Received: from [85.158.143.35:12873] by server-2.bemta-4.messagelabs.com id A7/68-04525-7C0D0245; Tue, 23 Sep 2014 01:45:43 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-2.tower-21.messagelabs.com!1411436742!4462126!1 X-Originating-IP: [209.85.217.170] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20715 invoked from network); 23 Sep 2014 01:45:42 -0000 Received: from mail-lb0-f170.google.com (HELO mail-lb0-f170.google.com) (209.85.217.170) by server-2.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 23 Sep 2014 01:45:42 -0000 Received: by mail-lb0-f170.google.com with SMTP id z11so2470502lbi.1 for ; Mon, 22 Sep 2014 18:45:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=x2sE08rfhWw7VX4MwIyCyNS8vb0H9sW+RAgsqBYOBDQ=; b=gvyyiNElSzDweHg62ve2nE6MPG5T6Vz9dmRbIU/pyV1OoELSQrg8kQ8Pm5kPRCQA/U XjHKYiqz7lqGXxz1Fssdml4WVMqo2bYg/iIIQ+Gl3xOAml3rPlMJg0GrIiEHA/ZaKe+I kJZNbCQE+q2jvuB1KX8Y0L4F5t9jq5D0O5SXHxiJkSly1lIMmE9p2iwEBEcrNShr2sTQ pSuX0XQlxrl7VQzD9cCmtqzE9aqPdQJ8hsKaAKnAjj1BZkUeuCdwLdZm49Ei8sXN+p/i XDAsjsmibNqV5bWB3vLH9z29WAoB21Lg0U7gG96ERX7axsuuSveTsPf2NSfQm+XafAN0 0DkQ== MIME-Version: 1.0 X-Received: by 10.152.7.145 with SMTP id j17mr6445195laa.77.1411436741632; Mon, 22 Sep 2014 18:45:41 -0700 (PDT) Received: by 10.112.12.225 with HTTP; Mon, 22 Sep 2014 18:45:41 -0700 (PDT) Date: Mon, 22 Sep 2014 21:45:41 -0400 X-Google-Sender-Auth: GqTNUZ_sn35gpQIUUY4BuOq8SDI Message-ID: From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] This Wednesday is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.org 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 This is a reminder that this Wednesday, September 24, is Xen Project Document Day. Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki. -- ATTENTION DEVELOPER AND USER SUMMIT ATTENDEES -- You've been part of some great talks in the past few weeks. Do the Wiki pages reflect what was presented? If the information is on another project's Wiki, can you locate that information from our Wiki? No? Well, Wednesday is the day to make it happen! All the information you need to participate in Document Day is here: http://wiki.xenproject.org/wiki/Xen_Document_Days If you get a few moments before Wednesday, please take a look at the current TODO list to see other items which need attention: http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO So please think about how you can help out. If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day. Just fill out the form below: http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html We hope to see you Wednesday in #xendocs! _______________________________________________ MirageOS-devel 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 Sep 23 20:46:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 23 Sep 2014 20:46:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWWyD-00005V-1S; Tue, 23 Sep 2014 20:45:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWWyB-00005Q-Lg for mirageos-devel@lists.xenproject.org; Tue, 23 Sep 2014 20:45:55 +0000 Received: from [85.158.137.68:28959] by server-9.bemta-3.messagelabs.com id C3/91-30790-20CD1245; Tue, 23 Sep 2014 20:45:54 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1411505154!11620397!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11623 invoked from network); 23 Sep 2014 20:45:54 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 23 Sep 2014 20:45:54 -0000 Received: by mail-wi0-f179.google.com with SMTP id d1so6004819wiv.0 for ; Tue, 23 Sep 2014 13:45:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=b6a9hVWseuO8x8vpoZITjS0lfrmr3mzrbNK1mnM+SG0=; b=udt6zObHWmaw3Zn/RwsSiKwimnJ1EEi2pcfboFPPM9L4A2/e+dZ7ygx8QH9DeVx6Fj cmNeeCxPXvsE1rNvZcJ4lLFlZrpId/L0cfx0+6x869Uf2QaUd2pk8oJ/Yz8gVxLjr4WF LuEtphE27DnkKtFuNI8cl08lQsjcSZsFT+NFc0zFHQQ84g0ObcjH8kpEbGOfY4J4GO8s EIHwO6/agV4cwKfuwFsIfWTCaA3fdxDNiQBQpx63F8RYjSkOCqygoE8yD3DAgy41mLHw Sa/3QZl/f3ny+b7QwGnEohQI9tJ2EjTNEyYJ1rt7ujs+h67IGnC0INsZXXMTj78skWwI wF8g== MIME-Version: 1.0 X-Received: by 10.181.27.132 with SMTP id jg4mr26204255wid.82.1411505153929; Tue, 23 Sep 2014 13:45:53 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Tue, 23 Sep 2014 13:45:53 -0700 (PDT) Date: Tue, 23 Sep 2014 21:45:53 +0100 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , netos@cl.cam.ac.uk Cc: "Leo P. White" Subject: [MirageOS-devel] OCaml compiler hacking next Tuesday (30th September) at Mill Lane X-BeenThere: mirageos-devel@lists.xenproject.org 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 next Cambridge OCaml compiler hacking evening is taking place next Tuesday evening (30th September) at the Postdoc Centre (next door to Makespace) on Mill Lane. All welcome: if you're local to Cambridge and interested in contributing to the OCaml compiler, please come along! The sign-up link is here: http://doodle.com/svwkevcs5p2xs8n8 and further details are on the blog: http://ocamllabs.github.io/compiler-hacking/2014/09/23/compiler-hacking-by-the-river.html _______________________________________________ MirageOS-devel 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 Sep 23 20:46:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 23 Sep 2014 20:46:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWWyD-00005V-1S; Tue, 23 Sep 2014 20:45:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWWyB-00005Q-Lg for mirageos-devel@lists.xenproject.org; Tue, 23 Sep 2014 20:45:55 +0000 Received: from [85.158.137.68:28959] by server-9.bemta-3.messagelabs.com id C3/91-30790-20CD1245; Tue, 23 Sep 2014 20:45:54 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1411505154!11620397!1 X-Originating-IP: [209.85.212.179] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11623 invoked from network); 23 Sep 2014 20:45:54 -0000 Received: from mail-wi0-f179.google.com (HELO mail-wi0-f179.google.com) (209.85.212.179) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 23 Sep 2014 20:45:54 -0000 Received: by mail-wi0-f179.google.com with SMTP id d1so6004819wiv.0 for ; Tue, 23 Sep 2014 13:45:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=b6a9hVWseuO8x8vpoZITjS0lfrmr3mzrbNK1mnM+SG0=; b=udt6zObHWmaw3Zn/RwsSiKwimnJ1EEi2pcfboFPPM9L4A2/e+dZ7ygx8QH9DeVx6Fj cmNeeCxPXvsE1rNvZcJ4lLFlZrpId/L0cfx0+6x869Uf2QaUd2pk8oJ/Yz8gVxLjr4WF LuEtphE27DnkKtFuNI8cl08lQsjcSZsFT+NFc0zFHQQ84g0ObcjH8kpEbGOfY4J4GO8s EIHwO6/agV4cwKfuwFsIfWTCaA3fdxDNiQBQpx63F8RYjSkOCqygoE8yD3DAgy41mLHw Sa/3QZl/f3ny+b7QwGnEohQI9tJ2EjTNEyYJ1rt7ujs+h67IGnC0INsZXXMTj78skWwI wF8g== MIME-Version: 1.0 X-Received: by 10.181.27.132 with SMTP id jg4mr26204255wid.82.1411505153929; Tue, 23 Sep 2014 13:45:53 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Tue, 23 Sep 2014 13:45:53 -0700 (PDT) Date: Tue, 23 Sep 2014 21:45:53 +0100 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , netos@cl.cam.ac.uk Cc: "Leo P. White" Subject: [MirageOS-devel] OCaml compiler hacking next Tuesday (30th September) at Mill Lane X-BeenThere: mirageos-devel@lists.xenproject.org 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 next Cambridge OCaml compiler hacking evening is taking place next Tuesday evening (30th September) at the Postdoc Centre (next door to Makespace) on Mill Lane. All welcome: if you're local to Cambridge and interested in contributing to the OCaml compiler, please come along! The sign-up link is here: http://doodle.com/svwkevcs5p2xs8n8 and further details are on the blog: http://ocamllabs.github.io/compiler-hacking/2014/09/23/compiler-hacking-by-the-river.html _______________________________________________ MirageOS-devel 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 Sep 24 04:42:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 24 Sep 2014 04:42:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWePa-0005DZ-TP; Wed, 24 Sep 2014 04:42:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWePa-0005DT-Eg for mirageos-devel@lists.xenproject.org; Wed, 24 Sep 2014 04:42:42 +0000 Received: from [85.158.137.68:38650] by server-17.bemta-3.messagelabs.com id 00/97-01689-1CB42245; Wed, 24 Sep 2014 04:42:41 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1411533760!11661650!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8911 invoked from network); 24 Sep 2014 04:42:41 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2014 04:42:41 -0000 Received: by mail-la0-f54.google.com with SMTP id ge10so10101346lab.27 for ; Tue, 23 Sep 2014 21:42:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tauS3MqYqaGjV+zYQiP6tX9gEYVfdYXGtCSjQz2EPrY=; b=WjYlXjVXulVR78NMQmanPc1jC9LUKEeQVXW5wRBD65CuYysrDL/RwveQsSFTiwl4Xp 3BPFiQOqCjc0zMCKds5mHHxuB64swuiWiqUuQdhJxXweoTOgt3X8WnM7Uv7hWyljjCUt oaPh0yyPanfcjowWmV2etkJMf9JfWoSvPlGc246VMefYN5NQnZwjUeDzR9nr39zeRvNQ 9njgZ4ybU1iGCgbGy6UHs6kOxSy1i4NmrWqySb1bmUCmx1WSD1CMpFvvnbH0kjoRP03+ lgtSwmCwfWcRdyit7ewG+vIMIuMIRWDrOghvCaYu33q4/wMaladoTCTQmzXvTcHDDY4Z 45eA== MIME-Version: 1.0 X-Received: by 10.152.19.66 with SMTP id c2mr3932957lae.64.1411533760251; Tue, 23 Sep 2014 21:42:40 -0700 (PDT) Received: by 10.112.12.225 with HTTP; Tue, 23 Sep 2014 21:42:40 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Sep 2014 00:42:40 -0400 X-Google-Sender-Auth: HjlYvb9Dq90QnrGtY8-aZTa_DSQ Message-ID: From: Russ Pavlicek To: Russ Pavlicek Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org, xen-devel@lists.xen.org Subject: Re: [MirageOS-devel] This Wednesday is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.org 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 Today is Document Day! Join us on #xendocs! > Xen Project Document Day is a day to help improve overall Xen Project > documentation, particularly that of the Wiki. > > -- ATTENTION DEVELOPER AND USER SUMMIT ATTENDEES -- > > You've been part of some great talks in the past few weeks. Do the > Wiki pages reflect what was presented? If the information is on > another project's Wiki, can you locate that information from our Wiki? > > No? Well, Wednesday is the day to make it happen! > > All the information you need to participate in Document Day is here: > > http://wiki.xenproject.org/wiki/Xen_Document_Days > > If you get a few moments before Wednesday, please take a look at the > current TODO list to see other items which need attention: > > http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO > > So please think about how you can help out. If you haven't requested > to be made a Wiki editor, save time and do it now so you are ready to > go on Document Day. Just fill out the form below: > > http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html _______________________________________________ MirageOS-devel 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 Sep 24 04:42:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 24 Sep 2014 04:42:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWePa-0005DZ-TP; Wed, 24 Sep 2014 04:42:42 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XWePa-0005DT-Eg for mirageos-devel@lists.xenproject.org; Wed, 24 Sep 2014 04:42:42 +0000 Received: from [85.158.137.68:38650] by server-17.bemta-3.messagelabs.com id 00/97-01689-1CB42245; Wed, 24 Sep 2014 04:42:41 +0000 X-Env-Sender: russell.pavlicek.xen@gmail.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1411533760!11661650!1 X-Originating-IP: [209.85.215.54] X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8911 invoked from network); 24 Sep 2014 04:42:41 -0000 Received: from mail-la0-f54.google.com (HELO mail-la0-f54.google.com) (209.85.215.54) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 24 Sep 2014 04:42:41 -0000 Received: by mail-la0-f54.google.com with SMTP id ge10so10101346lab.27 for ; Tue, 23 Sep 2014 21:42:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tauS3MqYqaGjV+zYQiP6tX9gEYVfdYXGtCSjQz2EPrY=; b=WjYlXjVXulVR78NMQmanPc1jC9LUKEeQVXW5wRBD65CuYysrDL/RwveQsSFTiwl4Xp 3BPFiQOqCjc0zMCKds5mHHxuB64swuiWiqUuQdhJxXweoTOgt3X8WnM7Uv7hWyljjCUt oaPh0yyPanfcjowWmV2etkJMf9JfWoSvPlGc246VMefYN5NQnZwjUeDzR9nr39zeRvNQ 9njgZ4ybU1iGCgbGy6UHs6kOxSy1i4NmrWqySb1bmUCmx1WSD1CMpFvvnbH0kjoRP03+ lgtSwmCwfWcRdyit7ewG+vIMIuMIRWDrOghvCaYu33q4/wMaladoTCTQmzXvTcHDDY4Z 45eA== MIME-Version: 1.0 X-Received: by 10.152.19.66 with SMTP id c2mr3932957lae.64.1411533760251; Tue, 23 Sep 2014 21:42:40 -0700 (PDT) Received: by 10.112.12.225 with HTTP; Tue, 23 Sep 2014 21:42:40 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Sep 2014 00:42:40 -0400 X-Google-Sender-Auth: HjlYvb9Dq90QnrGtY8-aZTa_DSQ Message-ID: From: Russ Pavlicek To: Russ Pavlicek Cc: "xen-users@lists.xen.org" , xen-api@lists.xen.org, xs-devel@lists.xenserver.org, mirageos-devel@lists.xenproject.org, xen-devel@lists.xen.org Subject: Re: [MirageOS-devel] This Wednesday is Xen Project Document Day X-BeenThere: mirageos-devel@lists.xenproject.org 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 Today is Document Day! Join us on #xendocs! > Xen Project Document Day is a day to help improve overall Xen Project > documentation, particularly that of the Wiki. > > -- ATTENTION DEVELOPER AND USER SUMMIT ATTENDEES -- > > You've been part of some great talks in the past few weeks. Do the > Wiki pages reflect what was presented? If the information is on > another project's Wiki, can you locate that information from our Wiki? > > No? Well, Wednesday is the day to make it happen! > > All the information you need to participate in Document Day is here: > > http://wiki.xenproject.org/wiki/Xen_Document_Days > > If you get a few moments before Wednesday, please take a look at the > current TODO list to see other items which need attention: > > http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO > > So please think about how you can help out. If you haven't requested > to be made a Wiki editor, save time and do it now so you are ready to > go on Document Day. Just fill out the form below: > > http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html _______________________________________________ MirageOS-devel 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 Sep 25 10:26:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 25 Sep 2014 10:26: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 1XX6G0-0007vx-AW; Thu, 25 Sep 2014 10:26:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XX6Fz-0007vk-5p for mirageos-devel@lists.xenproject.org; Thu, 25 Sep 2014 10:26:39 +0000 Received: from [85.158.139.211:16551] by server-3.bemta-5.messagelabs.com id A1/4D-13873-EDDE3245; Thu, 25 Sep 2014 10:26:38 +0000 X-Env-Sender: manu.delab@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1411640797!7837119!1 X-Originating-IP: [209.85.212.174] 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.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1602 invoked from network); 25 Sep 2014 10:26:37 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2014 10:26:37 -0000 Received: by mail-wi0-f174.google.com with SMTP id fb4so8603843wid.1 for ; Thu, 25 Sep 2014 03:26:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=cIQaZ24LQEVNV1kuLp550osR3xSEcRdsTexrkMisdI8=; b=ts0/ZWvQXOftyKiqN2CeBRhEvmQ9Sdyhc3Mmf9PhFPWefA1WBDG3Qv3gcfdLk+SKDT 0iIzkeFfkiQpfZgUk7EQymBi4WUPz5IhkqmImwUK65QnInwTL99AT89fWQ+CxFj3S3KX Y10NM9hySmtuZkCmnw7ezWB0bKtnE9ChsCYc+AdR/K2dFFjSPI1VBGjIjP1dvPY9GHsN zhFGihD1B7VNmmy699pwOxlLoQJEd9DlBYUqo1/KYHX2rcQU8M7aQvUHYwFjUpJvDM71 D/x1xuVh//rQ1FHWkSU0Ii8znjey7G9mM3d0eSNjcV791AghbMEDDnBTG9jAfA41ib+i oEug== X-Received: by 10.194.48.44 with SMTP id i12mr14184817wjn.83.1411640797146; Thu, 25 Sep 2014 03:26:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.195.12.15 with HTTP; Thu, 25 Sep 2014 03:25:57 -0700 (PDT) From: manu delab Date: Thu, 25 Sep 2014 22:25:57 +1200 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage website syndication X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3002576416656734101==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3002576416656734101== Content-Type: multipart/alternative; boundary=047d7b86f22443b6af0503e13c6a --047d7b86f22443b6af0503e13c6a Content-Type: text/plain; charset=UTF-8 Hello I would like to add blog syndication to mirage-www, as discussed here: https://github.com/mirage/mirage-www/pull/208 What I first had in mind was : - keep a list of feed in a text file (much like: https://github.com/ocaml/ocaml.org/blob/syndic/planet_feeds.txt). Its content would be made available as KV_RO module. - for each request, (say, to: '/community/blogs' ) ,we use an http client to get the feeds and generate the HTML I have a few questions: - Is that what people expect when they talk about syndication for mirage-www ? - fetching the feeds on each request seems unnecessary. Caching would be smarter but how do I write something that updates the cache after say, 3 hours ? A thread with a timer ? - Mirage exposes an HTTP server but not an HTTP client - The Syndic package relies on Calendar which uses Unix.localtime() which is not exposed by Mirage's Clock. How should I handle this ? Thank you M --047d7b86f22443b6af0503e13c6a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello

I would like to add blog syndicat= ion to mirage-www, as discussed here:

What I first had in mi= nd was :
- keep a list of feed in a text file (much like: https://github.com/ocaml/ocaml.org/blob/syndic/planet_feeds.txt= ). Its content would be made available as KV_RO module.=C2=A0
- for each request, (say, to: '/community/blogs'=C2=A0) ,we use an= http client to get the feeds and generate the HTML

I have a few questions:

- Is that what people ex= pect when they talk about syndication for mirage-www ?
- fetching= the feeds on each request seems unnecessary. Caching would be smarter but = how do I write something that updates the cache after say, 3 hours ? A thre= ad with a timer ?
- Mirage exposes an HTTP server but not an HTTP= client=C2=A0
- The Syndic package relies on Calendar which uses = Unix.localtime() which is not exposed by Mirage's Clock. How should I h= andle this ?

Thank you

M<= /div>

--047d7b86f22443b6af0503e13c6a-- --===============3002576416656734101== 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 --===============3002576416656734101==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 25 10:26:47 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 25 Sep 2014 10:26: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 1XX6G0-0007vx-AW; Thu, 25 Sep 2014 10:26:40 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XX6Fz-0007vk-5p for mirageos-devel@lists.xenproject.org; Thu, 25 Sep 2014 10:26:39 +0000 Received: from [85.158.139.211:16551] by server-3.bemta-5.messagelabs.com id A1/4D-13873-EDDE3245; Thu, 25 Sep 2014 10:26:38 +0000 X-Env-Sender: manu.delab@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1411640797!7837119!1 X-Originating-IP: [209.85.212.174] 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.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1602 invoked from network); 25 Sep 2014 10:26:37 -0000 Received: from mail-wi0-f174.google.com (HELO mail-wi0-f174.google.com) (209.85.212.174) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2014 10:26:37 -0000 Received: by mail-wi0-f174.google.com with SMTP id fb4so8603843wid.1 for ; Thu, 25 Sep 2014 03:26:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=cIQaZ24LQEVNV1kuLp550osR3xSEcRdsTexrkMisdI8=; b=ts0/ZWvQXOftyKiqN2CeBRhEvmQ9Sdyhc3Mmf9PhFPWefA1WBDG3Qv3gcfdLk+SKDT 0iIzkeFfkiQpfZgUk7EQymBi4WUPz5IhkqmImwUK65QnInwTL99AT89fWQ+CxFj3S3KX Y10NM9hySmtuZkCmnw7ezWB0bKtnE9ChsCYc+AdR/K2dFFjSPI1VBGjIjP1dvPY9GHsN zhFGihD1B7VNmmy699pwOxlLoQJEd9DlBYUqo1/KYHX2rcQU8M7aQvUHYwFjUpJvDM71 D/x1xuVh//rQ1FHWkSU0Ii8znjey7G9mM3d0eSNjcV791AghbMEDDnBTG9jAfA41ib+i oEug== X-Received: by 10.194.48.44 with SMTP id i12mr14184817wjn.83.1411640797146; Thu, 25 Sep 2014 03:26:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.195.12.15 with HTTP; Thu, 25 Sep 2014 03:25:57 -0700 (PDT) From: manu delab Date: Thu, 25 Sep 2014 22:25:57 +1200 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage website syndication X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3002576416656734101==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3002576416656734101== Content-Type: multipart/alternative; boundary=047d7b86f22443b6af0503e13c6a --047d7b86f22443b6af0503e13c6a Content-Type: text/plain; charset=UTF-8 Hello I would like to add blog syndication to mirage-www, as discussed here: https://github.com/mirage/mirage-www/pull/208 What I first had in mind was : - keep a list of feed in a text file (much like: https://github.com/ocaml/ocaml.org/blob/syndic/planet_feeds.txt). Its content would be made available as KV_RO module. - for each request, (say, to: '/community/blogs' ) ,we use an http client to get the feeds and generate the HTML I have a few questions: - Is that what people expect when they talk about syndication for mirage-www ? - fetching the feeds on each request seems unnecessary. Caching would be smarter but how do I write something that updates the cache after say, 3 hours ? A thread with a timer ? - Mirage exposes an HTTP server but not an HTTP client - The Syndic package relies on Calendar which uses Unix.localtime() which is not exposed by Mirage's Clock. How should I handle this ? Thank you M --047d7b86f22443b6af0503e13c6a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello

I would like to add blog syndicat= ion to mirage-www, as discussed here:

What I first had in mi= nd was :
- keep a list of feed in a text file (much like: https://github.com/ocaml/ocaml.org/blob/syndic/planet_feeds.txt= ). Its content would be made available as KV_RO module.=C2=A0
- for each request, (say, to: '/community/blogs'=C2=A0) ,we use an= http client to get the feeds and generate the HTML

I have a few questions:

- Is that what people ex= pect when they talk about syndication for mirage-www ?
- fetching= the feeds on each request seems unnecessary. Caching would be smarter but = how do I write something that updates the cache after say, 3 hours ? A thre= ad with a timer ?
- Mirage exposes an HTTP server but not an HTTP= client=C2=A0
- The Syndic package relies on Calendar which uses = Unix.localtime() which is not exposed by Mirage's Clock. How should I h= andle this ?

Thank you

M<= /div>

--047d7b86f22443b6af0503e13c6a-- --===============3002576416656734101== 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 --===============3002576416656734101==-- From mirageos-devel-bounces@lists.xenproject.org Thu Sep 25 12:29:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 25 Sep 2014 12:29:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XX8Au-0001w1-Ld; Thu, 25 Sep 2014 12:29:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XX8At-0001vw-Gs for mirageos-devel@lists.xenproject.org; Thu, 25 Sep 2014 12:29:31 +0000 Received: from [85.158.139.211:45084] by server-1.bemta-5.messagelabs.com id CA/1B-17892-AAA04245; Thu, 25 Sep 2014 12:29:30 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1411648170!4404198!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12584 invoked from network); 25 Sep 2014 12:29:30 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2014 12:29:30 -0000 Received: by mail-wg0-f48.google.com with SMTP id x13so4677829wgg.7 for ; Thu, 25 Sep 2014 05:29:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4oNxsPwBR5X/Gs3xd4efecR4xFUymx0qDvjUgiRKqag=; b=lq2UHqS+RgamTdLdozKJihu0N0H8RmYAJWRAZY5V1Lpwt1Cmys1l8VpgwfZURJSgZt 1FDHB7jyTBq6Ee0FvXeF/wXMDw2o81W1kMYbL4tQqsb74Pmx9Z3962xCV51qQO8POKqA HIevmfhtGEak3wfJZOyBlExPuZtZ0mojhkfUKSsM8w+c/615NdfjBkoydwvt/xyjJQlh J0pboqhs6ShY3EfSjqSZ8bwB0tEXznkLs37jSt6SbQCQ2fMPc5DVKSgFnIP93l3ovdNJ W7oPL/n/3fyD/bI3fwvDB2UTQdRnqvcUT25MDUrgjFK+SKVQqjYE5LNeXuUBU3Hh8qvD 7OGA== MIME-Version: 1.0 X-Received: by 10.180.83.39 with SMTP id n7mr4457335wiy.0.1411648169619; Thu, 25 Sep 2014 05:29:29 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Thu, 25 Sep 2014 05:29:29 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Sep 2014 13:29:29 +0100 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , netos@cl.cam.ac.uk Cc: "Leo P. White" Subject: Re: [MirageOS-devel] OCaml compiler hacking next Tuesday (30th September) at Mill Lane X-BeenThere: mirageos-devel@lists.xenproject.org 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 Update: this time round we're having a joint F#/OCaml session, beginning with a talk from Don Syme about F# compiler and language development! On 23 September 2014 21:45, Jeremy Yallop wrote: > The next Cambridge OCaml compiler hacking evening is taking place next > Tuesday evening (30th September) at the Postdoc Centre (next door to > Makespace) on Mill Lane. > > All welcome: if you're local to Cambridge and interested in > contributing to the OCaml compiler, please come along! The sign-up > link is here: > > http://doodle.com/svwkevcs5p2xs8n8 > > and further details are on the blog: > > http://ocamllabs.github.io/compiler-hacking/2014/09/23/compiler-hacking-by-the-river.html _______________________________________________ MirageOS-devel 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 Sep 25 12:29:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 25 Sep 2014 12:29:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XX8Au-0001w1-Ld; Thu, 25 Sep 2014 12:29:32 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XX8At-0001vw-Gs for mirageos-devel@lists.xenproject.org; Thu, 25 Sep 2014 12:29:31 +0000 Received: from [85.158.139.211:45084] by server-1.bemta-5.messagelabs.com id CA/1B-17892-AAA04245; Thu, 25 Sep 2014 12:29:30 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1411648170!4404198!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12584 invoked from network); 25 Sep 2014 12:29:30 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 25 Sep 2014 12:29:30 -0000 Received: by mail-wg0-f48.google.com with SMTP id x13so4677829wgg.7 for ; Thu, 25 Sep 2014 05:29:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4oNxsPwBR5X/Gs3xd4efecR4xFUymx0qDvjUgiRKqag=; b=lq2UHqS+RgamTdLdozKJihu0N0H8RmYAJWRAZY5V1Lpwt1Cmys1l8VpgwfZURJSgZt 1FDHB7jyTBq6Ee0FvXeF/wXMDw2o81W1kMYbL4tQqsb74Pmx9Z3962xCV51qQO8POKqA HIevmfhtGEak3wfJZOyBlExPuZtZ0mojhkfUKSsM8w+c/615NdfjBkoydwvt/xyjJQlh J0pboqhs6ShY3EfSjqSZ8bwB0tEXznkLs37jSt6SbQCQ2fMPc5DVKSgFnIP93l3ovdNJ W7oPL/n/3fyD/bI3fwvDB2UTQdRnqvcUT25MDUrgjFK+SKVQqjYE5LNeXuUBU3Hh8qvD 7OGA== MIME-Version: 1.0 X-Received: by 10.180.83.39 with SMTP id n7mr4457335wiy.0.1411648169619; Thu, 25 Sep 2014 05:29:29 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Thu, 25 Sep 2014 05:29:29 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Sep 2014 13:29:29 +0100 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , netos@cl.cam.ac.uk Cc: "Leo P. White" Subject: Re: [MirageOS-devel] OCaml compiler hacking next Tuesday (30th September) at Mill Lane X-BeenThere: mirageos-devel@lists.xenproject.org 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 Update: this time round we're having a joint F#/OCaml session, beginning with a talk from Don Syme about F# compiler and language development! On 23 September 2014 21:45, Jeremy Yallop wrote: > The next Cambridge OCaml compiler hacking evening is taking place next > Tuesday evening (30th September) at the Postdoc Centre (next door to > Makespace) on Mill Lane. > > All welcome: if you're local to Cambridge and interested in > contributing to the OCaml compiler, please come along! The sign-up > link is here: > > http://doodle.com/svwkevcs5p2xs8n8 > > and further details are on the blog: > > http://ocamllabs.github.io/compiler-hacking/2014/09/23/compiler-hacking-by-the-river.html _______________________________________________ MirageOS-devel 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 Sep 25 15:38:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 25 Sep 2014 15:38: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 1XXB7o-00088t-8U; Thu, 25 Sep 2014 15:38:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XXB7n-00088o-9v for mirageos-devel@lists.xenproject.org; Thu, 25 Sep 2014 15:38:31 +0000 Received: from [193.109.254.147:63826] by server-6.bemta-14.messagelabs.com id A2/DE-01867-6F634245; Thu, 25 Sep 2014 15:38:30 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-14.tower-27.messagelabs.com!1411659509!13025975!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9125 invoked from network); 25 Sep 2014 15:38:29 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2014 15:38:29 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from gw-eduroam.dar.cam.ac.uk ([131.111.194.10]:50272 helo=[192.168.99.55]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XXB7l-0001N2-kT (Exim 4.82_3-c0e5623) (return-path ); Thu, 25 Sep 2014 16:38:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Thu, 25 Sep 2014 16:38:28 +0100 Message-Id: References: To: manu delab X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage website syndication X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 25 Sep 2014, at 11:25, manu delab wrote: > Hello > > I would like to add blog syndication to mirage-www, as discussed here: > https://github.com/mirage/mirage-www/pull/208 Thanks for looking into this! It would be great to get planet-like syndication on openmirage.org > > What I first had in mind was : > - keep a list of feed in a text file (much like: https://github.com/ocaml/ocaml.org/blob/syndic/planet_feeds.txt). Its content would be made available as KV_RO module. > - for each request, (say, to: '/community/blogs' ) ,we use an http client to get the feeds and generate the HTML > > I have a few questions: > > - Is that what people expect when they talk about syndication for mirage-www ? > - fetching the feeds on each request seems unnecessary. Caching would be smarter but how do I write something that updates the cache after say, 3 hours ? A thread with a timer ? > - Mirage exposes an HTTP server but not an HTTP client Something like this is what I have in mind but rather than fetching on each request, I'd only fetch things when the unikernel is built (with Travis running the builds). That seems like it would be more straightforward to implement (with the downside that it might initially be fetching and building the same content for each commit - but at least we'd have something working). Is any of Christophe's work on the feed for ocaml.org useful? It would be good to reuse things if possible/appropriate. > - The Syndic package relies on Calendar which uses Unix.localtime() which is not exposed by Mirage's Clock. How should I handle this ? I don't have anything useful to say on this so I hope others will comment when they get a chance. Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Sep 25 15:38:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 25 Sep 2014 15:38: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 1XXB7o-00088t-8U; Thu, 25 Sep 2014 15:38:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XXB7n-00088o-9v for mirageos-devel@lists.xenproject.org; Thu, 25 Sep 2014 15:38:31 +0000 Received: from [193.109.254.147:63826] by server-6.bemta-14.messagelabs.com id A2/DE-01867-6F634245; Thu, 25 Sep 2014 15:38:30 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-14.tower-27.messagelabs.com!1411659509!13025975!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9125 invoked from network); 25 Sep 2014 15:38:29 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-14.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Sep 2014 15:38:29 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from gw-eduroam.dar.cam.ac.uk ([131.111.194.10]:50272 helo=[192.168.99.55]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XXB7l-0001N2-kT (Exim 4.82_3-c0e5623) (return-path ); Thu, 25 Sep 2014 16:38:29 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Thu, 25 Sep 2014 16:38:28 +0100 Message-Id: References: To: manu delab X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage website syndication X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 25 Sep 2014, at 11:25, manu delab wrote: > Hello > > I would like to add blog syndication to mirage-www, as discussed here: > https://github.com/mirage/mirage-www/pull/208 Thanks for looking into this! It would be great to get planet-like syndication on openmirage.org > > What I first had in mind was : > - keep a list of feed in a text file (much like: https://github.com/ocaml/ocaml.org/blob/syndic/planet_feeds.txt). Its content would be made available as KV_RO module. > - for each request, (say, to: '/community/blogs' ) ,we use an http client to get the feeds and generate the HTML > > I have a few questions: > > - Is that what people expect when they talk about syndication for mirage-www ? > - fetching the feeds on each request seems unnecessary. Caching would be smarter but how do I write something that updates the cache after say, 3 hours ? A thread with a timer ? > - Mirage exposes an HTTP server but not an HTTP client Something like this is what I have in mind but rather than fetching on each request, I'd only fetch things when the unikernel is built (with Travis running the builds). That seems like it would be more straightforward to implement (with the downside that it might initially be fetching and building the same content for each commit - but at least we'd have something working). Is any of Christophe's work on the feed for ocaml.org useful? It would be good to reuse things if possible/appropriate. > - The Syndic package relies on Calendar which uses Unix.localtime() which is not exposed by Mirage's Clock. How should I handle this ? I don't have anything useful to say on this so I hope others will comment when they get a chance. Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Sep 26 03:12:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 26 Sep 2014 03:12: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 1XXLwx-0003Io-QJ; Fri, 26 Sep 2014 03:12:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XXLwv-0003Ij-L2 for mirageos-devel@lists.xenproject.org; Fri, 26 Sep 2014 03:12:02 +0000 Received: from [85.158.143.35:61676] by server-2.bemta-4.messagelabs.com id 32/E5-04525-089D4245; Fri, 26 Sep 2014 03:12:00 +0000 X-Env-Sender: romain.calascibetta@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1411701117!12012915!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23, SUBJECT_EXCESS_QP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22611 invoked from network); 26 Sep 2014 03:11:59 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2014 03:11:59 -0000 Received: by mail-pa0-f54.google.com with SMTP id ey11so405009pad.13 for ; Thu, 25 Sep 2014 20:11:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:mime-version:from:to:cc:subject:importance:date :in-reply-to:references:content-type; bh=nGNm57OsITD/Zn78VRD3H4wrr4HwW+XQS5jPkGZiAsc=; b=wWlGYenIOJ90xuzwmmdTqEVH3PC+FIH1Olrl4TjL2VS3MHSNaLUeqo/NndOvE9vQvT pHaFk6XNIidh0NhdSWGH87HvLOGbQtEnRE5R9y55W9eRr8RpP602ARHZJKYlLg7xy7PK YfesWSJwc9khAnwVJk05ELD+MMB876m6FD4GX0dT3Sz+E8JC+1HUpwJMwVc1EQH3iz1l avnNiUIPdt6BPPH6B7xwFnxaF8Xr4pHJIFsuFDAqLTKR/dNYsnsI5tPE2FTOWTV50D8+ YyQo/wJFwibCxuyW9jjCDza6iHe1pophwTwXiGgxCBTsRqpUY/NfiTALbD03Qpfh72Mq YmcQ== X-Received: by 10.69.31.138 with SMTP id km10mr9454350pbd.67.1411701117423; Thu, 25 Sep 2014 20:11:57 -0700 (PDT) Received: from caca ([60.247.46.112]) by mx.google.com with ESMTPSA id qp9sm3446919pbc.31.2014.09.25.20.11.54 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 25 Sep 2014 20:11:56 -0700 (PDT) Message-ID: <5424d97c.e9de440a.69ac.ffffb9fd@mx.google.com> MIME-Version: 1.0 From: To: =?utf-8?Q?Amir_Chaudhry?= , =?utf-8?Q?manu_delab?= Importance: Normal Date: Fri, 26 Sep 2014 03:10:53 +0000 In-Reply-To: References: , Cc: "=?utf-8?Q?mirageos-devel@lists.xenproject.org?=" Subject: Re: [MirageOS-devel] =?utf-8?q?Mirage_website_syndication?= X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6605117907628490731==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6605117907628490731== Content-Type: multipart/alternative; boundary="_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_" --_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_ Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" PiAtIFRoZSBTeW5kaWMgcGFja2FnZSByZWxpZXMgb24gQ2FsZW5kYXIgd2hpY2ggdXNlcyBVbml4 LmxvY2FsdGltZSgpIHdoaWNoIGlzIG5vdCBleHBvc2VkIGJ5IE1pcmFnZSdzIENsb2NrLiBIb3cg c2hvdWxkIEkgaGFuZGxlIHRoaXMgPw0KDQoNCg0KVGhhbmsgeW91IHVzZSBTeW5kaWMhIFdlIHVz ZSBDYWxlbmRhciBmb3IgY29tcGx5IHdpdGggdGhlIFJGQyBvbiBkYXRlcy4gSW5pdGlhbGx5LCB3 ZSBoYWQgdXNlZCBPY2FtbE5ldCAod2hpY2ggZG9lcyBub3Qgd29yayBlaXRoZXIgb24gTWlyYWdl T1MpIGFuZCB3ZSBoYXZlIGNoYW5nZWQgdG8gQ2FsZW5kYXIsIHRoaW5raW5nIHRoYXQgaXQgd291 bGQgd29yayBvbiBNaXJhZ2VPUy4gVGhpcyBpcyBub3QgdGhlIGNhc2UuDQoNCg0KSSByZW9wZW5l ZCB0aGUgZGViYXRlIG9uIHRoZSBjb21wdXRlIG9mIGRhdGVzIGluIFN5bmRpYywgaWYgeW91IGhh dmUgYSBzdWdnZXN0aW9uLCBoZXJlIGlzIHRoZSBpc3N1ZToNCg0KDQpodHRwczovL2dpdGh1Yi5j b20vQ3VtdWx1cy9TeW5kaWMvaXNzdWVzLzIzDQoNCg0KQmVzdCwNCg0KDQoNCg0KDQoNClJvbWFp biBDYWxhc2NpYmV0dGEgLSBodHRwOi8vZGluLm9zYXUucmUvDQoNCg0KDQoNCg0KRGUgOiBBbWly IENoYXVkaHJ5DQpFbnZvecOpIDog4oCOamV1ZGnigI4g4oCOMjXigI4g4oCOc2VwdGVtYnJl4oCO IOKAjjIwMTQg4oCOMTfigI464oCOMzgNCsOAIDogbWFudSBkZWxhYg0KQ2MgOiBtaXJhZ2Vvcy1k ZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZw0KDQoNCg0KDQoNCg0KT24gMjUgU2VwIDIwMTQsIGF0 IDExOjI1LCBtYW51IGRlbGFiIDxtYW51LmRlbGFiQGdtYWlsLmNvbT4gd3JvdGU6DQoNCj4gSGVs bG8NCj4gDQo+IEkgd291bGQgbGlrZSB0byBhZGQgYmxvZyBzeW5kaWNhdGlvbiB0byBtaXJhZ2Ut d3d3LCBhcyBkaXNjdXNzZWQgaGVyZToNCj4gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS9taXJh Z2Utd3d3L3B1bGwvMjA4DQoNClRoYW5rcyBmb3IgbG9va2luZyBpbnRvIHRoaXMhICBJdCB3b3Vs ZCBiZSBncmVhdCB0byBnZXQgcGxhbmV0LWxpa2Ugc3luZGljYXRpb24gb24gb3Blbm1pcmFnZS5v cmcgDQoNCj4gDQo+IFdoYXQgSSBmaXJzdCBoYWQgaW4gbWluZCB3YXMgOg0KPiAtIGtlZXAgYSBs aXN0IG9mIGZlZWQgaW4gYSB0ZXh0IGZpbGUgKG11Y2ggbGlrZTogaHR0cHM6Ly9naXRodWIuY29t L29jYW1sL29jYW1sLm9yZy9ibG9iL3N5bmRpYy9wbGFuZXRfZmVlZHMudHh0KS4gSXRzIGNvbnRl bnQgd291bGQgYmUgbWFkZSBhdmFpbGFibGUgYXMgS1ZfUk8gbW9kdWxlLiANCj4gLSBmb3IgZWFj aCByZXF1ZXN0LCAoc2F5LCB0bzogJy9jb21tdW5pdHkvYmxvZ3MnICkgLHdlIHVzZSBhbiBodHRw IGNsaWVudCB0byBnZXQgdGhlIGZlZWRzIGFuZCBnZW5lcmF0ZSB0aGUgSFRNTA0KPiANCj4gSSBo YXZlIGEgZmV3IHF1ZXN0aW9uczoNCj4gDQo+IC0gSXMgdGhhdCB3aGF0IHBlb3BsZSBleHBlY3Qg d2hlbiB0aGV5IHRhbGsgYWJvdXQgc3luZGljYXRpb24gZm9yIG1pcmFnZS13d3cgPw0KPiAtIGZl dGNoaW5nIHRoZSBmZWVkcyBvbiBlYWNoIHJlcXVlc3Qgc2VlbXMgdW5uZWNlc3NhcnkuIENhY2hp bmcgd291bGQgYmUgc21hcnRlciBidXQgaG93IGRvIEkgd3JpdGUgc29tZXRoaW5nIHRoYXQgdXBk YXRlcyB0aGUgY2FjaGUgYWZ0ZXIgc2F5LCAzIGhvdXJzID8gQSB0aHJlYWQgd2l0aCBhIHRpbWVy ID8NCj4gLSBNaXJhZ2UgZXhwb3NlcyBhbiBIVFRQIHNlcnZlciBidXQgbm90IGFuIEhUVFAgY2xp ZW50IA0KDQpTb21ldGhpbmcgbGlrZSB0aGlzIGlzIHdoYXQgSSBoYXZlIGluIG1pbmQgYnV0IHJh dGhlciB0aGFuIGZldGNoaW5nIG9uIGVhY2ggcmVxdWVzdCwgSSdkIG9ubHkgZmV0Y2ggdGhpbmdz IHdoZW4gdGhlIHVuaWtlcm5lbCBpcyBidWlsdCAod2l0aCBUcmF2aXMgcnVubmluZyB0aGUgYnVp bGRzKS4gVGhhdCBzZWVtcyBsaWtlIGl0IHdvdWxkIGJlIG1vcmUgc3RyYWlnaHRmb3J3YXJkIHRv IGltcGxlbWVudCAod2l0aCB0aGUgZG93bnNpZGUgdGhhdCBpdCBtaWdodCBpbml0aWFsbHkgYmUg ZmV0Y2hpbmcgYW5kIGJ1aWxkaW5nIHRoZSBzYW1lIGNvbnRlbnQgZm9yIGVhY2ggY29tbWl0IC0g YnV0IGF0IGxlYXN0IHdlJ2QgaGF2ZSBzb21ldGhpbmcgd29ya2luZykuDQoNCklzIGFueSBvZiBD aHJpc3RvcGhlJ3Mgd29yayBvbiB0aGUgZmVlZCBmb3Igb2NhbWwub3JnIHVzZWZ1bD8gIEl0IHdv dWxkIGJlIGdvb2QgdG8gcmV1c2UgdGhpbmdzIGlmIHBvc3NpYmxlL2FwcHJvcHJpYXRlLg0KDQo+ IC0gVGhlIFN5bmRpYyBwYWNrYWdlIHJlbGllcyBvbiBDYWxlbmRhciB3aGljaCB1c2VzIFVuaXgu bG9jYWx0aW1lKCkgd2hpY2ggaXMgbm90IGV4cG9zZWQgYnkgTWlyYWdlJ3MgQ2xvY2suIEhvdyBz aG91bGQgSSBoYW5kbGUgdGhpcyA/DQoNCkkgZG9uJ3QgaGF2ZSBhbnl0aGluZyB1c2VmdWwgdG8g c2F5IG9uIHRoaXMgc28gSSBob3BlIG90aGVycyB3aWxsIGNvbW1lbnQgd2hlbiB0aGV5IGdldCBh IGNoYW5jZS4NCg0KQW1pcg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18NCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdA0KTWlyYWdlT1MtZGV2ZWxAbGlz dHMueGVucHJvamVjdC5vcmcNCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21h aWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWw= --_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_ Content-Transfer-Encoding: base64 Content-Type: text/html; charset="utf-8" CjxodG1sPgo8aGVhZD4KPG1ldGEgbmFtZT0iZ2VuZXJhdG9yIiBjb250ZW50PSJXaW5kb3dzIE1h aWwgMTcuNS45NjAwLjIwNjA1Ij4KPHN0eWxlIHR5cGU9InRleHQvY3NzIj48IS0taHRtbCB7IGZv bnQtZmFtaWx5OiAiQ29sb3IgRW1vamkiLCAiQ2FsaWJyaSIsICJTZWdvZSBVSSIsICJNZWlyeW8i LCAiTWljcm9zb2Z0IFlhSGVpIFVJIiwgIk1pY3Jvc29mdCBKaGVuZ0hlaSBVSSIsICJNYWxndW4g R290aGljIiwgInNhbnMtc2VyaWYiOyB9LS0+PC9zdHlsZT48c3R5bGUgZGF0YS1leHRlcm5hbHN0 eWxlPSJ0cnVlIj48IS0tCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwg ZGl2Lk1zb0xpc3RQYXJhZ3JhcGggewptYXJnaW4tdG9wOjBpbjsKbWFyZ2luLXJpZ2h0OjBpbjsK bWFyZ2luLWJvdHRvbTowaW47Cm1hcmdpbi1sZWZ0Oi41aW47Cm1hcmdpbi1ib3R0b206LjAwMDFw dDsKfQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsIHsKbWFyZ2luOjBp bjsKbWFyZ2luLWJvdHRvbTouMDAwMXB0Owp9CnAuTXNvTGlzdFBhcmFncmFwaEN4U3BGaXJzdCwg bGkuTXNvTGlzdFBhcmFncmFwaEN4U3BGaXJzdCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwRmly c3QsIApwLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCBsaS5Nc29MaXN0UGFyYWdyYXBoQ3hT cE1pZGRsZSwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCAKcC5Nc29MaXN0UGFyYWdy YXBoQ3hTcExhc3QsIGxpLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTGFzdCwgZGl2Lk1zb0xpc3RQYXJh Z3JhcGhDeFNwTGFzdCB7Cm1hcmdpbi10b3A6MGluOwptYXJnaW4tcmlnaHQ6MGluOwptYXJnaW4t Ym90dG9tOjBpbjsKbWFyZ2luLWxlZnQ6LjVpbjsKbWFyZ2luLWJvdHRvbTouMDAwMXB0OwpsaW5l LWhlaWdodDoxMTUlOwp9Ci0tPjwvc3R5bGU+PC9oZWFkPgo8Ym9keSBkaXI9Imx0ciI+CjxkaXYg ZGF0YS1leHRlcm5hbHN0eWxlPSJmYWxzZSIgZGlyPSJsdHIiIHN0eWxlPSJmb250LWZhbWlseTog J0NhbGlicmknLCAnU2Vnb2UgVUknLCAnTWVpcnlvJywgJ01pY3Jvc29mdCBZYUhlaSBVSScsICdN aWNyb3NvZnQgSmhlbmdIZWkgVUknLCAnTWFsZ3VuIEdvdGhpYycsICdzYW5zLXNlcmlmJztmb250 LXNpemU6MTJwdDsiPjxkaXY+Jmd0OyAtIFRoZSBTeW5kaWMgcGFja2FnZSByZWxpZXMgb24gQ2Fs ZW5kYXIgd2hpY2ggdXNlcyBVbml4LmxvY2FsdGltZSgpIHdoaWNoIGlzIG5vdCBleHBvc2VkIGJ5 IE1pcmFnZSdzIENsb2NrLiBIb3cgc2hvdWxkIEkgaGFuZGxlIHRoaXMgPzxicj48L2Rpdj48ZGl2 Pjxicj48L2Rpdj48ZGl2PlRoYW5rIHlvdSB1c2UgU3luZGljISBXZSB1c2UgQ2FsZW5kYXIgZm9y IGNvbXBseSB3aXRoIHRoZSBSRkMgb24gZGF0ZXMuIEluaXRpYWxseSwgd2UgaGFkIHVzZWQgT2Nh bWxOZXQgKHdoaWNoIGRvZXMgbm90IHdvcmsgZWl0aGVyIG9uIE1pcmFnZU9TKSBhbmQgd2UgaGF2 ZSBjaGFuZ2VkIHRvIENhbGVuZGFyLCB0aGlua2luZyB0aGF0IGl0IHdvdWxkIHdvcmsgb24gTWly YWdlT1MuIFRoaXMgaXMgbm90IHRoZSBjYXNlLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+SSBy ZW9wZW5lZCB0aGUgZGViYXRlIG9uIHRoZSBjb21wdXRlIG9mIGRhdGVzIGluIFN5bmRpYywgaWYg eW91IGhhdmUgYSBzdWdnZXN0aW9uLCBoZXJlIGlzIHRoZSBpc3N1ZTo8L2Rpdj48ZGl2Pjxicj48 L2Rpdj48ZGl2PjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9DdW11bHVzL1N5bmRpYy9pc3N1 ZXMvMjMiIHRhcmdldD0iX3BhcmVudCI+aHR0cHM6Ly9naXRodWIuY29tL0N1bXVsdXMvU3luZGlj L2lzc3Vlcy8yMzwvYT48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkJlc3QsPGJyPjwvZGl2Pjxk aXYgZGF0YS1zaWduYXR1cmVibG9jaz0idHJ1ZSI+PGRpdj48YnI+PC9kaXY+PGRpdj5Sb21haW4g Q2FsYXNjaWJldHRhIC0gaHR0cDovL2Rpbi5vc2F1LnJlLzwvZGl2PjxkaXY+PGJyPjwvZGl2Pjwv ZGl2PjxkaXYgc3R5bGU9InBhZGRpbmctdG9wOiA1cHg7IGJvcmRlci10b3AtY29sb3I6IHJnYigy MjksIDIyOSwgMjI5KTsgYm9yZGVyLXRvcC13aWR0aDogMXB4OyBib3JkZXItdG9wLXN0eWxlOiBz b2xpZDsiPjxkaXY+PGZvbnQgZmFjZT0iICdDYWxpYnJpJywgJ1NlZ29lIFVJJywgJ01laXJ5bycs ICdNaWNyb3NvZnQgWWFIZWkgVUknLCAnTWljcm9zb2Z0IEpoZW5nSGVpIFVJJywgJ01hbGd1biBH b3RoaWMnLCAnc2Fucy1zZXJpZiciIHN0eWxlPSdsaW5lLWhlaWdodDogMTVwdDsgbGV0dGVyLXNw YWNpbmc6IDAuMDJlbTsgZm9udC1mYW1pbHk6ICJDYWxpYnJpIiwgIlNlZ29lIFVJIiwgIk1laXJ5 byIsICJNaWNyb3NvZnQgWWFIZWkgVUkiLCAiTWljcm9zb2Z0IEpoZW5nSGVpIFVJIiwgIk1hbGd1 biBHb3RoaWMiLCAic2Fucy1zZXJpZiI7IGZvbnQtc2l6ZTogMTJwdDsnPjxiPkRlJm5ic3A7Ojwv Yj4mbmJzcDs8YSBocmVmPSJtYWlsdG86YW1jNzlAY2FtLmFjLnVrIiB0YXJnZXQ9Il9wYXJlbnQi PkFtaXIgQ2hhdWRocnk8L2E+PGJyPjxiPkVudm95w6kmbmJzcDs6PC9iPiZuYnNwO+KAjmpldWRp 4oCOIOKAjjI14oCOIOKAjnNlcHRlbWJyZeKAjiDigI4yMDE0IOKAjjE34oCOOuKAjjM4PGJyPjxi PsOAIDo8L2I+Jm5ic3A7PGEgaHJlZj0ibWFpbHRvOm1hbnUuZGVsYWJAZ21haWwuY29tIiB0YXJn ZXQ9Il9wYXJlbnQiPm1hbnUgZGVsYWI8L2E+PGJyPjxiPkNjJm5ic3A7OjwvYj4mbmJzcDs8YSBo cmVmPSJtYWlsdG86bWlyYWdlb3MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmciIHRhcmdldD0i X3BhcmVudCI+bWlyYWdlb3MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmc8L2E+PC9mb250Pjwv ZGl2PjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgZGlyPSIiPjxkaXYgaWQ9InJlYWRpbmdQYW5l Qm9keUNvbnRlbnQiPjxicj5PbiAyNSBTZXAgMjAxNCwgYXQgMTE6MjUsIG1hbnUgZGVsYWIgJmx0 O21hbnUuZGVsYWJAZ21haWwuY29tJmd0OyB3cm90ZTo8YnI+PGJyPiZndDsgSGVsbG88YnI+Jmd0 OyA8YnI+Jmd0OyBJIHdvdWxkIGxpa2UgdG8gYWRkIGJsb2cgc3luZGljYXRpb24gdG8gbWlyYWdl LXd3dywgYXMgZGlzY3Vzc2VkIGhlcmU6PGJyPiZndDsgaHR0cHM6Ly9naXRodWIuY29tL21pcmFn ZS9taXJhZ2Utd3d3L3B1bGwvMjA4PGJyPjxicj5UaGFua3MgZm9yIGxvb2tpbmcgaW50byB0aGlz ISZuYnNwOyBJdCB3b3VsZCBiZSBncmVhdCB0byBnZXQgcGxhbmV0LWxpa2Ugc3luZGljYXRpb24g b24gb3Blbm1pcmFnZS5vcmcgPGJyPjxicj4mZ3Q7IDxicj4mZ3Q7IFdoYXQgSSBmaXJzdCBoYWQg aW4gbWluZCB3YXMgOjxicj4mZ3Q7IC0ga2VlcCBhIGxpc3Qgb2YgZmVlZCBpbiBhIHRleHQgZmls ZSAobXVjaCBsaWtlOiBodHRwczovL2dpdGh1Yi5jb20vb2NhbWwvb2NhbWwub3JnL2Jsb2Ivc3lu ZGljL3BsYW5ldF9mZWVkcy50eHQpLiBJdHMgY29udGVudCB3b3VsZCBiZSBtYWRlIGF2YWlsYWJs ZSBhcyBLVl9STyBtb2R1bGUuIDxicj4mZ3Q7IC0gZm9yIGVhY2ggcmVxdWVzdCwgKHNheSwgdG86 ICcvY29tbXVuaXR5L2Jsb2dzJyApICx3ZSB1c2UgYW4gaHR0cCBjbGllbnQgdG8gZ2V0IHRoZSBm ZWVkcyBhbmQgZ2VuZXJhdGUgdGhlIEhUTUw8YnI+Jmd0OyA8YnI+Jmd0OyBJIGhhdmUgYSBmZXcg cXVlc3Rpb25zOjxicj4mZ3Q7IDxicj4mZ3Q7IC0gSXMgdGhhdCB3aGF0IHBlb3BsZSBleHBlY3Qg d2hlbiB0aGV5IHRhbGsgYWJvdXQgc3luZGljYXRpb24gZm9yIG1pcmFnZS13d3cgPzxicj4mZ3Q7 IC0gZmV0Y2hpbmcgdGhlIGZlZWRzIG9uIGVhY2ggcmVxdWVzdCBzZWVtcyB1bm5lY2Vzc2FyeS4g Q2FjaGluZyB3b3VsZCBiZSBzbWFydGVyIGJ1dCBob3cgZG8gSSB3cml0ZSBzb21ldGhpbmcgdGhh dCB1cGRhdGVzIHRoZSBjYWNoZSBhZnRlciBzYXksIDMgaG91cnMgPyBBIHRocmVhZCB3aXRoIGEg dGltZXIgPzxicj4mZ3Q7IC0gTWlyYWdlIGV4cG9zZXMgYW4gSFRUUCBzZXJ2ZXIgYnV0IG5vdCBh biBIVFRQIGNsaWVudCA8YnI+PGJyPlNvbWV0aGluZyBsaWtlIHRoaXMgaXMgd2hhdCBJIGhhdmUg aW4gbWluZCBidXQgcmF0aGVyIHRoYW4gZmV0Y2hpbmcgb24gZWFjaCByZXF1ZXN0LCBJJ2Qgb25s eSBmZXRjaCB0aGluZ3Mgd2hlbiB0aGUgdW5pa2VybmVsIGlzIGJ1aWx0ICh3aXRoIFRyYXZpcyBy dW5uaW5nIHRoZSBidWlsZHMpLiBUaGF0IHNlZW1zIGxpa2UgaXQgd291bGQgYmUgbW9yZSBzdHJh aWdodGZvcndhcmQgdG8gaW1wbGVtZW50ICh3aXRoIHRoZSBkb3duc2lkZSB0aGF0IGl0IG1pZ2h0 IGluaXRpYWxseSBiZSBmZXRjaGluZyBhbmQgYnVpbGRpbmcgdGhlIHNhbWUgY29udGVudCBmb3Ig ZWFjaCBjb21taXQgLSBidXQgYXQgbGVhc3Qgd2UnZCBoYXZlIHNvbWV0aGluZyB3b3JraW5nKS48 YnI+PGJyPklzIGFueSBvZiBDaHJpc3RvcGhlJ3Mgd29yayBvbiB0aGUgZmVlZCBmb3Igb2NhbWwu b3JnIHVzZWZ1bD8mbmJzcDsgSXQgd291bGQgYmUgZ29vZCB0byByZXVzZSB0aGluZ3MgaWYgcG9z c2libGUvYXBwcm9wcmlhdGUuPGJyPjxicj4mZ3Q7IC0gVGhlIFN5bmRpYyBwYWNrYWdlIHJlbGll cyBvbiBDYWxlbmRhciB3aGljaCB1c2VzIFVuaXgubG9jYWx0aW1lKCkgd2hpY2ggaXMgbm90IGV4 cG9zZWQgYnkgTWlyYWdlJ3MgQ2xvY2suIEhvdyBzaG91bGQgSSBoYW5kbGUgdGhpcyA/PGJyPjxi cj5JIGRvbid0IGhhdmUgYW55dGhpbmcgdXNlZnVsIHRvIHNheSBvbiB0aGlzIHNvIEkgaG9wZSBv dGhlcnMgd2lsbCBjb21tZW50IHdoZW4gdGhleSBnZXQgYSBjaGFuY2UuPGJyPjxicj5BbWlyPGJy Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPk1pcmFn ZU9TLWRldmVsIG1haWxpbmcgbGlzdDxicj5NaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0 Lm9yZzxicj5odHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL21pcmFnZW9zLWRldmVsPGJyPjwvZGl2PjwvZGl2PjwvZGl2Pgo8L2JvZHk+CjwvaHRtbD4K --_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_-- --===============6605117907628490731== 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 --===============6605117907628490731==-- From mirageos-devel-bounces@lists.xenproject.org Fri Sep 26 03:12:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 26 Sep 2014 03:12: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 1XXLwx-0003Io-QJ; Fri, 26 Sep 2014 03:12:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XXLwv-0003Ij-L2 for mirageos-devel@lists.xenproject.org; Fri, 26 Sep 2014 03:12:02 +0000 Received: from [85.158.143.35:61676] by server-2.bemta-4.messagelabs.com id 32/E5-04525-089D4245; Fri, 26 Sep 2014 03:12:00 +0000 X-Env-Sender: romain.calascibetta@gmail.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1411701117!12012915!1 X-Originating-IP: [209.85.220.54] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,ML_RADAR_SPEW_LINKS_23, SUBJECT_EXCESS_QP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22611 invoked from network); 26 Sep 2014 03:11:59 -0000 Received: from mail-pa0-f54.google.com (HELO mail-pa0-f54.google.com) (209.85.220.54) by server-11.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 26 Sep 2014 03:11:59 -0000 Received: by mail-pa0-f54.google.com with SMTP id ey11so405009pad.13 for ; Thu, 25 Sep 2014 20:11:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:mime-version:from:to:cc:subject:importance:date :in-reply-to:references:content-type; bh=nGNm57OsITD/Zn78VRD3H4wrr4HwW+XQS5jPkGZiAsc=; b=wWlGYenIOJ90xuzwmmdTqEVH3PC+FIH1Olrl4TjL2VS3MHSNaLUeqo/NndOvE9vQvT pHaFk6XNIidh0NhdSWGH87HvLOGbQtEnRE5R9y55W9eRr8RpP602ARHZJKYlLg7xy7PK YfesWSJwc9khAnwVJk05ELD+MMB876m6FD4GX0dT3Sz+E8JC+1HUpwJMwVc1EQH3iz1l avnNiUIPdt6BPPH6B7xwFnxaF8Xr4pHJIFsuFDAqLTKR/dNYsnsI5tPE2FTOWTV50D8+ YyQo/wJFwibCxuyW9jjCDza6iHe1pophwTwXiGgxCBTsRqpUY/NfiTALbD03Qpfh72Mq YmcQ== X-Received: by 10.69.31.138 with SMTP id km10mr9454350pbd.67.1411701117423; Thu, 25 Sep 2014 20:11:57 -0700 (PDT) Received: from caca ([60.247.46.112]) by mx.google.com with ESMTPSA id qp9sm3446919pbc.31.2014.09.25.20.11.54 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 25 Sep 2014 20:11:56 -0700 (PDT) Message-ID: <5424d97c.e9de440a.69ac.ffffb9fd@mx.google.com> MIME-Version: 1.0 From: To: =?utf-8?Q?Amir_Chaudhry?= , =?utf-8?Q?manu_delab?= Importance: Normal Date: Fri, 26 Sep 2014 03:10:53 +0000 In-Reply-To: References: , Cc: "=?utf-8?Q?mirageos-devel@lists.xenproject.org?=" Subject: Re: [MirageOS-devel] =?utf-8?q?Mirage_website_syndication?= X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6605117907628490731==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6605117907628490731== Content-Type: multipart/alternative; boundary="_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_" --_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_ Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" PiAtIFRoZSBTeW5kaWMgcGFja2FnZSByZWxpZXMgb24gQ2FsZW5kYXIgd2hpY2ggdXNlcyBVbml4 LmxvY2FsdGltZSgpIHdoaWNoIGlzIG5vdCBleHBvc2VkIGJ5IE1pcmFnZSdzIENsb2NrLiBIb3cg c2hvdWxkIEkgaGFuZGxlIHRoaXMgPw0KDQoNCg0KVGhhbmsgeW91IHVzZSBTeW5kaWMhIFdlIHVz ZSBDYWxlbmRhciBmb3IgY29tcGx5IHdpdGggdGhlIFJGQyBvbiBkYXRlcy4gSW5pdGlhbGx5LCB3 ZSBoYWQgdXNlZCBPY2FtbE5ldCAod2hpY2ggZG9lcyBub3Qgd29yayBlaXRoZXIgb24gTWlyYWdl T1MpIGFuZCB3ZSBoYXZlIGNoYW5nZWQgdG8gQ2FsZW5kYXIsIHRoaW5raW5nIHRoYXQgaXQgd291 bGQgd29yayBvbiBNaXJhZ2VPUy4gVGhpcyBpcyBub3QgdGhlIGNhc2UuDQoNCg0KSSByZW9wZW5l ZCB0aGUgZGViYXRlIG9uIHRoZSBjb21wdXRlIG9mIGRhdGVzIGluIFN5bmRpYywgaWYgeW91IGhh dmUgYSBzdWdnZXN0aW9uLCBoZXJlIGlzIHRoZSBpc3N1ZToNCg0KDQpodHRwczovL2dpdGh1Yi5j b20vQ3VtdWx1cy9TeW5kaWMvaXNzdWVzLzIzDQoNCg0KQmVzdCwNCg0KDQoNCg0KDQoNClJvbWFp biBDYWxhc2NpYmV0dGEgLSBodHRwOi8vZGluLm9zYXUucmUvDQoNCg0KDQoNCg0KRGUgOiBBbWly IENoYXVkaHJ5DQpFbnZvecOpIDog4oCOamV1ZGnigI4g4oCOMjXigI4g4oCOc2VwdGVtYnJl4oCO IOKAjjIwMTQg4oCOMTfigI464oCOMzgNCsOAIDogbWFudSBkZWxhYg0KQ2MgOiBtaXJhZ2Vvcy1k ZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZw0KDQoNCg0KDQoNCg0KT24gMjUgU2VwIDIwMTQsIGF0 IDExOjI1LCBtYW51IGRlbGFiIDxtYW51LmRlbGFiQGdtYWlsLmNvbT4gd3JvdGU6DQoNCj4gSGVs bG8NCj4gDQo+IEkgd291bGQgbGlrZSB0byBhZGQgYmxvZyBzeW5kaWNhdGlvbiB0byBtaXJhZ2Ut d3d3LCBhcyBkaXNjdXNzZWQgaGVyZToNCj4gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS9taXJh Z2Utd3d3L3B1bGwvMjA4DQoNClRoYW5rcyBmb3IgbG9va2luZyBpbnRvIHRoaXMhICBJdCB3b3Vs ZCBiZSBncmVhdCB0byBnZXQgcGxhbmV0LWxpa2Ugc3luZGljYXRpb24gb24gb3Blbm1pcmFnZS5v cmcgDQoNCj4gDQo+IFdoYXQgSSBmaXJzdCBoYWQgaW4gbWluZCB3YXMgOg0KPiAtIGtlZXAgYSBs aXN0IG9mIGZlZWQgaW4gYSB0ZXh0IGZpbGUgKG11Y2ggbGlrZTogaHR0cHM6Ly9naXRodWIuY29t L29jYW1sL29jYW1sLm9yZy9ibG9iL3N5bmRpYy9wbGFuZXRfZmVlZHMudHh0KS4gSXRzIGNvbnRl bnQgd291bGQgYmUgbWFkZSBhdmFpbGFibGUgYXMgS1ZfUk8gbW9kdWxlLiANCj4gLSBmb3IgZWFj aCByZXF1ZXN0LCAoc2F5LCB0bzogJy9jb21tdW5pdHkvYmxvZ3MnICkgLHdlIHVzZSBhbiBodHRw IGNsaWVudCB0byBnZXQgdGhlIGZlZWRzIGFuZCBnZW5lcmF0ZSB0aGUgSFRNTA0KPiANCj4gSSBo YXZlIGEgZmV3IHF1ZXN0aW9uczoNCj4gDQo+IC0gSXMgdGhhdCB3aGF0IHBlb3BsZSBleHBlY3Qg d2hlbiB0aGV5IHRhbGsgYWJvdXQgc3luZGljYXRpb24gZm9yIG1pcmFnZS13d3cgPw0KPiAtIGZl dGNoaW5nIHRoZSBmZWVkcyBvbiBlYWNoIHJlcXVlc3Qgc2VlbXMgdW5uZWNlc3NhcnkuIENhY2hp bmcgd291bGQgYmUgc21hcnRlciBidXQgaG93IGRvIEkgd3JpdGUgc29tZXRoaW5nIHRoYXQgdXBk YXRlcyB0aGUgY2FjaGUgYWZ0ZXIgc2F5LCAzIGhvdXJzID8gQSB0aHJlYWQgd2l0aCBhIHRpbWVy ID8NCj4gLSBNaXJhZ2UgZXhwb3NlcyBhbiBIVFRQIHNlcnZlciBidXQgbm90IGFuIEhUVFAgY2xp ZW50IA0KDQpTb21ldGhpbmcgbGlrZSB0aGlzIGlzIHdoYXQgSSBoYXZlIGluIG1pbmQgYnV0IHJh dGhlciB0aGFuIGZldGNoaW5nIG9uIGVhY2ggcmVxdWVzdCwgSSdkIG9ubHkgZmV0Y2ggdGhpbmdz IHdoZW4gdGhlIHVuaWtlcm5lbCBpcyBidWlsdCAod2l0aCBUcmF2aXMgcnVubmluZyB0aGUgYnVp bGRzKS4gVGhhdCBzZWVtcyBsaWtlIGl0IHdvdWxkIGJlIG1vcmUgc3RyYWlnaHRmb3J3YXJkIHRv IGltcGxlbWVudCAod2l0aCB0aGUgZG93bnNpZGUgdGhhdCBpdCBtaWdodCBpbml0aWFsbHkgYmUg ZmV0Y2hpbmcgYW5kIGJ1aWxkaW5nIHRoZSBzYW1lIGNvbnRlbnQgZm9yIGVhY2ggY29tbWl0IC0g YnV0IGF0IGxlYXN0IHdlJ2QgaGF2ZSBzb21ldGhpbmcgd29ya2luZykuDQoNCklzIGFueSBvZiBD aHJpc3RvcGhlJ3Mgd29yayBvbiB0aGUgZmVlZCBmb3Igb2NhbWwub3JnIHVzZWZ1bD8gIEl0IHdv dWxkIGJlIGdvb2QgdG8gcmV1c2UgdGhpbmdzIGlmIHBvc3NpYmxlL2FwcHJvcHJpYXRlLg0KDQo+ IC0gVGhlIFN5bmRpYyBwYWNrYWdlIHJlbGllcyBvbiBDYWxlbmRhciB3aGljaCB1c2VzIFVuaXgu bG9jYWx0aW1lKCkgd2hpY2ggaXMgbm90IGV4cG9zZWQgYnkgTWlyYWdlJ3MgQ2xvY2suIEhvdyBz aG91bGQgSSBoYW5kbGUgdGhpcyA/DQoNCkkgZG9uJ3QgaGF2ZSBhbnl0aGluZyB1c2VmdWwgdG8g c2F5IG9uIHRoaXMgc28gSSBob3BlIG90aGVycyB3aWxsIGNvbW1lbnQgd2hlbiB0aGV5IGdldCBh IGNoYW5jZS4NCg0KQW1pcg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18NCk1pcmFnZU9TLWRldmVsIG1haWxpbmcgbGlzdA0KTWlyYWdlT1MtZGV2ZWxAbGlz dHMueGVucHJvamVjdC5vcmcNCmh0dHA6Ly9saXN0cy54ZW5wcm9qZWN0Lm9yZy9jZ2ktYmluL21h aWxtYW4vbGlzdGluZm8vbWlyYWdlb3MtZGV2ZWw= --_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_ Content-Transfer-Encoding: base64 Content-Type: text/html; charset="utf-8" CjxodG1sPgo8aGVhZD4KPG1ldGEgbmFtZT0iZ2VuZXJhdG9yIiBjb250ZW50PSJXaW5kb3dzIE1h aWwgMTcuNS45NjAwLjIwNjA1Ij4KPHN0eWxlIHR5cGU9InRleHQvY3NzIj48IS0taHRtbCB7IGZv bnQtZmFtaWx5OiAiQ29sb3IgRW1vamkiLCAiQ2FsaWJyaSIsICJTZWdvZSBVSSIsICJNZWlyeW8i LCAiTWljcm9zb2Z0IFlhSGVpIFVJIiwgIk1pY3Jvc29mdCBKaGVuZ0hlaSBVSSIsICJNYWxndW4g R290aGljIiwgInNhbnMtc2VyaWYiOyB9LS0+PC9zdHlsZT48c3R5bGUgZGF0YS1leHRlcm5hbHN0 eWxlPSJ0cnVlIj48IS0tCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwg ZGl2Lk1zb0xpc3RQYXJhZ3JhcGggewptYXJnaW4tdG9wOjBpbjsKbWFyZ2luLXJpZ2h0OjBpbjsK bWFyZ2luLWJvdHRvbTowaW47Cm1hcmdpbi1sZWZ0Oi41aW47Cm1hcmdpbi1ib3R0b206LjAwMDFw dDsKfQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsIHsKbWFyZ2luOjBp bjsKbWFyZ2luLWJvdHRvbTouMDAwMXB0Owp9CnAuTXNvTGlzdFBhcmFncmFwaEN4U3BGaXJzdCwg bGkuTXNvTGlzdFBhcmFncmFwaEN4U3BGaXJzdCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwRmly c3QsIApwLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCBsaS5Nc29MaXN0UGFyYWdyYXBoQ3hT cE1pZGRsZSwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlLCAKcC5Nc29MaXN0UGFyYWdy YXBoQ3hTcExhc3QsIGxpLk1zb0xpc3RQYXJhZ3JhcGhDeFNwTGFzdCwgZGl2Lk1zb0xpc3RQYXJh Z3JhcGhDeFNwTGFzdCB7Cm1hcmdpbi10b3A6MGluOwptYXJnaW4tcmlnaHQ6MGluOwptYXJnaW4t Ym90dG9tOjBpbjsKbWFyZ2luLWxlZnQ6LjVpbjsKbWFyZ2luLWJvdHRvbTouMDAwMXB0OwpsaW5l LWhlaWdodDoxMTUlOwp9Ci0tPjwvc3R5bGU+PC9oZWFkPgo8Ym9keSBkaXI9Imx0ciI+CjxkaXYg ZGF0YS1leHRlcm5hbHN0eWxlPSJmYWxzZSIgZGlyPSJsdHIiIHN0eWxlPSJmb250LWZhbWlseTog J0NhbGlicmknLCAnU2Vnb2UgVUknLCAnTWVpcnlvJywgJ01pY3Jvc29mdCBZYUhlaSBVSScsICdN aWNyb3NvZnQgSmhlbmdIZWkgVUknLCAnTWFsZ3VuIEdvdGhpYycsICdzYW5zLXNlcmlmJztmb250 LXNpemU6MTJwdDsiPjxkaXY+Jmd0OyAtIFRoZSBTeW5kaWMgcGFja2FnZSByZWxpZXMgb24gQ2Fs ZW5kYXIgd2hpY2ggdXNlcyBVbml4LmxvY2FsdGltZSgpIHdoaWNoIGlzIG5vdCBleHBvc2VkIGJ5 IE1pcmFnZSdzIENsb2NrLiBIb3cgc2hvdWxkIEkgaGFuZGxlIHRoaXMgPzxicj48L2Rpdj48ZGl2 Pjxicj48L2Rpdj48ZGl2PlRoYW5rIHlvdSB1c2UgU3luZGljISBXZSB1c2UgQ2FsZW5kYXIgZm9y IGNvbXBseSB3aXRoIHRoZSBSRkMgb24gZGF0ZXMuIEluaXRpYWxseSwgd2UgaGFkIHVzZWQgT2Nh bWxOZXQgKHdoaWNoIGRvZXMgbm90IHdvcmsgZWl0aGVyIG9uIE1pcmFnZU9TKSBhbmQgd2UgaGF2 ZSBjaGFuZ2VkIHRvIENhbGVuZGFyLCB0aGlua2luZyB0aGF0IGl0IHdvdWxkIHdvcmsgb24gTWly YWdlT1MuIFRoaXMgaXMgbm90IHRoZSBjYXNlLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+SSBy ZW9wZW5lZCB0aGUgZGViYXRlIG9uIHRoZSBjb21wdXRlIG9mIGRhdGVzIGluIFN5bmRpYywgaWYg eW91IGhhdmUgYSBzdWdnZXN0aW9uLCBoZXJlIGlzIHRoZSBpc3N1ZTo8L2Rpdj48ZGl2Pjxicj48 L2Rpdj48ZGl2PjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9DdW11bHVzL1N5bmRpYy9pc3N1 ZXMvMjMiIHRhcmdldD0iX3BhcmVudCI+aHR0cHM6Ly9naXRodWIuY29tL0N1bXVsdXMvU3luZGlj L2lzc3Vlcy8yMzwvYT48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkJlc3QsPGJyPjwvZGl2Pjxk aXYgZGF0YS1zaWduYXR1cmVibG9jaz0idHJ1ZSI+PGRpdj48YnI+PC9kaXY+PGRpdj5Sb21haW4g Q2FsYXNjaWJldHRhIC0gaHR0cDovL2Rpbi5vc2F1LnJlLzwvZGl2PjxkaXY+PGJyPjwvZGl2Pjwv ZGl2PjxkaXYgc3R5bGU9InBhZGRpbmctdG9wOiA1cHg7IGJvcmRlci10b3AtY29sb3I6IHJnYigy MjksIDIyOSwgMjI5KTsgYm9yZGVyLXRvcC13aWR0aDogMXB4OyBib3JkZXItdG9wLXN0eWxlOiBz b2xpZDsiPjxkaXY+PGZvbnQgZmFjZT0iICdDYWxpYnJpJywgJ1NlZ29lIFVJJywgJ01laXJ5bycs ICdNaWNyb3NvZnQgWWFIZWkgVUknLCAnTWljcm9zb2Z0IEpoZW5nSGVpIFVJJywgJ01hbGd1biBH b3RoaWMnLCAnc2Fucy1zZXJpZiciIHN0eWxlPSdsaW5lLWhlaWdodDogMTVwdDsgbGV0dGVyLXNw YWNpbmc6IDAuMDJlbTsgZm9udC1mYW1pbHk6ICJDYWxpYnJpIiwgIlNlZ29lIFVJIiwgIk1laXJ5 byIsICJNaWNyb3NvZnQgWWFIZWkgVUkiLCAiTWljcm9zb2Z0IEpoZW5nSGVpIFVJIiwgIk1hbGd1 biBHb3RoaWMiLCAic2Fucy1zZXJpZiI7IGZvbnQtc2l6ZTogMTJwdDsnPjxiPkRlJm5ic3A7Ojwv Yj4mbmJzcDs8YSBocmVmPSJtYWlsdG86YW1jNzlAY2FtLmFjLnVrIiB0YXJnZXQ9Il9wYXJlbnQi PkFtaXIgQ2hhdWRocnk8L2E+PGJyPjxiPkVudm95w6kmbmJzcDs6PC9iPiZuYnNwO+KAjmpldWRp 4oCOIOKAjjI14oCOIOKAjnNlcHRlbWJyZeKAjiDigI4yMDE0IOKAjjE34oCOOuKAjjM4PGJyPjxi PsOAIDo8L2I+Jm5ic3A7PGEgaHJlZj0ibWFpbHRvOm1hbnUuZGVsYWJAZ21haWwuY29tIiB0YXJn ZXQ9Il9wYXJlbnQiPm1hbnUgZGVsYWI8L2E+PGJyPjxiPkNjJm5ic3A7OjwvYj4mbmJzcDs8YSBo cmVmPSJtYWlsdG86bWlyYWdlb3MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmciIHRhcmdldD0i X3BhcmVudCI+bWlyYWdlb3MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmc8L2E+PC9mb250Pjwv ZGl2PjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgZGlyPSIiPjxkaXYgaWQ9InJlYWRpbmdQYW5l Qm9keUNvbnRlbnQiPjxicj5PbiAyNSBTZXAgMjAxNCwgYXQgMTE6MjUsIG1hbnUgZGVsYWIgJmx0 O21hbnUuZGVsYWJAZ21haWwuY29tJmd0OyB3cm90ZTo8YnI+PGJyPiZndDsgSGVsbG88YnI+Jmd0 OyA8YnI+Jmd0OyBJIHdvdWxkIGxpa2UgdG8gYWRkIGJsb2cgc3luZGljYXRpb24gdG8gbWlyYWdl LXd3dywgYXMgZGlzY3Vzc2VkIGhlcmU6PGJyPiZndDsgaHR0cHM6Ly9naXRodWIuY29tL21pcmFn ZS9taXJhZ2Utd3d3L3B1bGwvMjA4PGJyPjxicj5UaGFua3MgZm9yIGxvb2tpbmcgaW50byB0aGlz ISZuYnNwOyBJdCB3b3VsZCBiZSBncmVhdCB0byBnZXQgcGxhbmV0LWxpa2Ugc3luZGljYXRpb24g b24gb3Blbm1pcmFnZS5vcmcgPGJyPjxicj4mZ3Q7IDxicj4mZ3Q7IFdoYXQgSSBmaXJzdCBoYWQg aW4gbWluZCB3YXMgOjxicj4mZ3Q7IC0ga2VlcCBhIGxpc3Qgb2YgZmVlZCBpbiBhIHRleHQgZmls ZSAobXVjaCBsaWtlOiBodHRwczovL2dpdGh1Yi5jb20vb2NhbWwvb2NhbWwub3JnL2Jsb2Ivc3lu ZGljL3BsYW5ldF9mZWVkcy50eHQpLiBJdHMgY29udGVudCB3b3VsZCBiZSBtYWRlIGF2YWlsYWJs ZSBhcyBLVl9STyBtb2R1bGUuIDxicj4mZ3Q7IC0gZm9yIGVhY2ggcmVxdWVzdCwgKHNheSwgdG86 ICcvY29tbXVuaXR5L2Jsb2dzJyApICx3ZSB1c2UgYW4gaHR0cCBjbGllbnQgdG8gZ2V0IHRoZSBm ZWVkcyBhbmQgZ2VuZXJhdGUgdGhlIEhUTUw8YnI+Jmd0OyA8YnI+Jmd0OyBJIGhhdmUgYSBmZXcg cXVlc3Rpb25zOjxicj4mZ3Q7IDxicj4mZ3Q7IC0gSXMgdGhhdCB3aGF0IHBlb3BsZSBleHBlY3Qg d2hlbiB0aGV5IHRhbGsgYWJvdXQgc3luZGljYXRpb24gZm9yIG1pcmFnZS13d3cgPzxicj4mZ3Q7 IC0gZmV0Y2hpbmcgdGhlIGZlZWRzIG9uIGVhY2ggcmVxdWVzdCBzZWVtcyB1bm5lY2Vzc2FyeS4g Q2FjaGluZyB3b3VsZCBiZSBzbWFydGVyIGJ1dCBob3cgZG8gSSB3cml0ZSBzb21ldGhpbmcgdGhh dCB1cGRhdGVzIHRoZSBjYWNoZSBhZnRlciBzYXksIDMgaG91cnMgPyBBIHRocmVhZCB3aXRoIGEg dGltZXIgPzxicj4mZ3Q7IC0gTWlyYWdlIGV4cG9zZXMgYW4gSFRUUCBzZXJ2ZXIgYnV0IG5vdCBh biBIVFRQIGNsaWVudCA8YnI+PGJyPlNvbWV0aGluZyBsaWtlIHRoaXMgaXMgd2hhdCBJIGhhdmUg aW4gbWluZCBidXQgcmF0aGVyIHRoYW4gZmV0Y2hpbmcgb24gZWFjaCByZXF1ZXN0LCBJJ2Qgb25s eSBmZXRjaCB0aGluZ3Mgd2hlbiB0aGUgdW5pa2VybmVsIGlzIGJ1aWx0ICh3aXRoIFRyYXZpcyBy dW5uaW5nIHRoZSBidWlsZHMpLiBUaGF0IHNlZW1zIGxpa2UgaXQgd291bGQgYmUgbW9yZSBzdHJh aWdodGZvcndhcmQgdG8gaW1wbGVtZW50ICh3aXRoIHRoZSBkb3duc2lkZSB0aGF0IGl0IG1pZ2h0 IGluaXRpYWxseSBiZSBmZXRjaGluZyBhbmQgYnVpbGRpbmcgdGhlIHNhbWUgY29udGVudCBmb3Ig ZWFjaCBjb21taXQgLSBidXQgYXQgbGVhc3Qgd2UnZCBoYXZlIHNvbWV0aGluZyB3b3JraW5nKS48 YnI+PGJyPklzIGFueSBvZiBDaHJpc3RvcGhlJ3Mgd29yayBvbiB0aGUgZmVlZCBmb3Igb2NhbWwu b3JnIHVzZWZ1bD8mbmJzcDsgSXQgd291bGQgYmUgZ29vZCB0byByZXVzZSB0aGluZ3MgaWYgcG9z c2libGUvYXBwcm9wcmlhdGUuPGJyPjxicj4mZ3Q7IC0gVGhlIFN5bmRpYyBwYWNrYWdlIHJlbGll cyBvbiBDYWxlbmRhciB3aGljaCB1c2VzIFVuaXgubG9jYWx0aW1lKCkgd2hpY2ggaXMgbm90IGV4 cG9zZWQgYnkgTWlyYWdlJ3MgQ2xvY2suIEhvdyBzaG91bGQgSSBoYW5kbGUgdGhpcyA/PGJyPjxi cj5JIGRvbid0IGhhdmUgYW55dGhpbmcgdXNlZnVsIHRvIHNheSBvbiB0aGlzIHNvIEkgaG9wZSBv dGhlcnMgd2lsbCBjb21tZW50IHdoZW4gdGhleSBnZXQgYSBjaGFuY2UuPGJyPjxicj5BbWlyPGJy Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPk1pcmFn ZU9TLWRldmVsIG1haWxpbmcgbGlzdDxicj5NaXJhZ2VPUy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0 Lm9yZzxicj5odHRwOi8vbGlzdHMueGVucHJvamVjdC5vcmcvY2dpLWJpbi9tYWlsbWFuL2xpc3Rp bmZvL21pcmFnZW9zLWRldmVsPGJyPjwvZGl2PjwvZGl2PjwvZGl2Pgo8L2JvZHk+CjwvaHRtbD4K --_1B1A0C35-53E9-48B0-A422-3FAFCE2076D8_-- --===============6605117907628490731== 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 --===============6605117907628490731==-- From mirageos-devel-bounces@lists.xenproject.org Mon Sep 29 14:17:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 29 Sep 2014 14:17: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 1XYblc-0005Xa-Kg; Mon, 29 Sep 2014 14:17:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XYblb-0005XG-Dn for mirageos-devel@lists.xenproject.org; Mon, 29 Sep 2014 14:17:31 +0000 Received: from [193.109.254.147:9754] by server-10.bemta-14.messagelabs.com id 20/AD-01463-AF969245; Mon, 29 Sep 2014 14:17:30 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1412000249!7612238!1 X-Originating-IP: [74.125.82.174] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11163 invoked from network); 29 Sep 2014 14:17:30 -0000 Received: from mail-we0-f174.google.com (HELO mail-we0-f174.google.com) (74.125.82.174) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2014 14:17:30 -0000 Received: by mail-we0-f174.google.com with SMTP id w62so12645055wes.19 for ; Mon, 29 Sep 2014 07:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p9RrZGgB9fj1mI74J+tb0LiIkdugDZYc8A8kFF1t+1M=; b=bBPZXwsnTELL6BJM/9uVyte2r4boTk4rSN97L4PL71/s5GZxKOrIudTQbYGtt8oLIZ 0UWnJpdceq5GjD1q/zGg1Y/lGTQw4RFn0lQmL3zxNpFRLsaIB1s8LHMqOb+uQTD1G/zH oHiW/QyrEBU5KSZgr75gw56sMWC4SyeUnwXurVIb1Eh0ZGwOZ0fz93D5isL6rGzm0Ybz vDcRA1kPJhqlY+f5MhqowEzwlYqMioosjeNAlHG97RQrCnRup0LVD5ZpM1QZe4/Ov9Gx fSd8i/hPLLL0s1M+iEAagbmYMZvPhWGng1qcVn6176DHI6Y965LKzARcKuNlFbKHdXyb 7klg== MIME-Version: 1.0 X-Received: by 10.180.103.131 with SMTP id fw3mr66795593wib.77.1412000249602; Mon, 29 Sep 2014 07:17:29 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Mon, 29 Sep 2014 07:17:29 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 15:17:29 +0100 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , netos@cl.cam.ac.uk Cc: "Leo P. White" Subject: Re: [MirageOS-devel] OCaml compiler hacking next Tuesday (30th September) at Mill Lane X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Reminder: it's compiler hacking at Mill Lane tomorrow! If you're planning to come, but haven't yet signed up, please add your name to the Doodle poll: http://doodle.com/svwkevcs5p2xs8n8 On 25 September 2014 13:29, Jeremy Yallop wrote: > Update: this time round we're having a joint F#/OCaml session, > beginning with a talk from Don Syme about F# compiler and language > development! > > On 23 September 2014 21:45, Jeremy Yallop wrote: >> The next Cambridge OCaml compiler hacking evening is taking place next >> Tuesday evening (30th September) at the Postdoc Centre (next door to >> Makespace) on Mill Lane. >> >> All welcome: if you're local to Cambridge and interested in >> contributing to the OCaml compiler, please come along! The sign-up >> link is here: >> >> http://doodle.com/svwkevcs5p2xs8n8 >> >> and further details are on the blog: >> >> http://ocamllabs.github.io/compiler-hacking/2014/09/23/compiler-hacking-by-the-river.html _______________________________________________ MirageOS-devel 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 Sep 29 14:17:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 29 Sep 2014 14:17: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 1XYblc-0005Xa-Kg; Mon, 29 Sep 2014 14:17:32 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XYblb-0005XG-Dn for mirageos-devel@lists.xenproject.org; Mon, 29 Sep 2014 14:17:31 +0000 Received: from [193.109.254.147:9754] by server-10.bemta-14.messagelabs.com id 20/AD-01463-AF969245; Mon, 29 Sep 2014 14:17:30 +0000 X-Env-Sender: yallop@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1412000249!7612238!1 X-Originating-IP: [74.125.82.174] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11163 invoked from network); 29 Sep 2014 14:17:30 -0000 Received: from mail-we0-f174.google.com (HELO mail-we0-f174.google.com) (74.125.82.174) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 29 Sep 2014 14:17:30 -0000 Received: by mail-we0-f174.google.com with SMTP id w62so12645055wes.19 for ; Mon, 29 Sep 2014 07:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p9RrZGgB9fj1mI74J+tb0LiIkdugDZYc8A8kFF1t+1M=; b=bBPZXwsnTELL6BJM/9uVyte2r4boTk4rSN97L4PL71/s5GZxKOrIudTQbYGtt8oLIZ 0UWnJpdceq5GjD1q/zGg1Y/lGTQw4RFn0lQmL3zxNpFRLsaIB1s8LHMqOb+uQTD1G/zH oHiW/QyrEBU5KSZgr75gw56sMWC4SyeUnwXurVIb1Eh0ZGwOZ0fz93D5isL6rGzm0Ybz vDcRA1kPJhqlY+f5MhqowEzwlYqMioosjeNAlHG97RQrCnRup0LVD5ZpM1QZe4/Ov9Gx fSd8i/hPLLL0s1M+iEAagbmYMZvPhWGng1qcVn6176DHI6Y965LKzARcKuNlFbKHdXyb 7klg== MIME-Version: 1.0 X-Received: by 10.180.103.131 with SMTP id fw3mr66795593wib.77.1412000249602; Mon, 29 Sep 2014 07:17:29 -0700 (PDT) Received: by 10.217.129.194 with HTTP; Mon, 29 Sep 2014 07:17:29 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Sep 2014 15:17:29 +0100 Message-ID: From: Jeremy Yallop To: cam-compiler-hacking@lists.ocaml.org, "cl-ocamllabs@lists.cam.ac.uk" , "cl-ocamllabs-staff@lists.cam.ac.uk" , "mirageos-devel@lists.xenproject.org" , netos@cl.cam.ac.uk Cc: "Leo P. White" Subject: Re: [MirageOS-devel] OCaml compiler hacking next Tuesday (30th September) at Mill Lane X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Reminder: it's compiler hacking at Mill Lane tomorrow! If you're planning to come, but haven't yet signed up, please add your name to the Doodle poll: http://doodle.com/svwkevcs5p2xs8n8 On 25 September 2014 13:29, Jeremy Yallop wrote: > Update: this time round we're having a joint F#/OCaml session, > beginning with a talk from Don Syme about F# compiler and language > development! > > On 23 September 2014 21:45, Jeremy Yallop wrote: >> The next Cambridge OCaml compiler hacking evening is taking place next >> Tuesday evening (30th September) at the Postdoc Centre (next door to >> Makespace) on Mill Lane. >> >> All welcome: if you're local to Cambridge and interested in >> contributing to the OCaml compiler, please come along! The sign-up >> link is here: >> >> http://doodle.com/svwkevcs5p2xs8n8 >> >> and further details are on the blog: >> >> http://ocamllabs.github.io/compiler-hacking/2014/09/23/compiler-hacking-by-the-river.html _______________________________________________ MirageOS-devel 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 Sep 29 16:58:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 29 Sep 2014 16:58: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 1XYeHF-0007Mo-Db; Mon, 29 Sep 2014 16:58:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XYeHE-0007Mj-FM for mirageos-devel@lists.xenproject.org; Mon, 29 Sep 2014 16:58:20 +0000 Received: from [85.158.137.68:29724] by server-2.bemta-3.messagelabs.com id 3F/50-09149-BAF89245; Mon, 29 Sep 2014 16:58:19 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1412009898!12741472!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15840 invoked from network); 29 Sep 2014 16:58:19 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-16.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Sep 2014 16:58:19 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:55411 helo=[10.0.0.151]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XYeHC-0006RH-ka (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 29 Sep 2014 17:58:18 +0100 From: Amir Chaudhry Message-Id: Date: Mon, 29 Sep 2014 17:58:17 +0100 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Tuesday 30th at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place tomorrow afternoon (Tuesday) at 4pm BST. As always, calls are open to all! If you have anything you'd like to bring up, please add it to the agenda. Agenda: https://github.com/mirage/mirage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays with this, I'll switch to a public Google Hangout. If that happens, I'll post the link here and also in the IRC channel (#mirage on freenode). Join us at 4pm BST tomorrow! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Sep 29 16:58:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 29 Sep 2014 16:58: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 1XYeHF-0007Mo-Db; Mon, 29 Sep 2014 16:58:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XYeHE-0007Mj-FM for mirageos-devel@lists.xenproject.org; Mon, 29 Sep 2014 16:58:20 +0000 Received: from [85.158.137.68:29724] by server-2.bemta-3.messagelabs.com id 3F/50-09149-BAF89245; Mon, 29 Sep 2014 16:58:19 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1412009898!12741472!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.12.2; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15840 invoked from network); 29 Sep 2014 16:58:19 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-16.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Sep 2014 16:58:19 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:55411 helo=[10.0.0.151]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1XYeHC-0006RH-ka (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 29 Sep 2014 17:58:18 +0100 From: Amir Chaudhry Message-Id: Date: Mon, 29 Sep 2014 17:58:17 +0100 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] Mirage fortnightly call - Tuesday 30th at 4pm BST (== GMT + 1) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, The next Mirage call will take place tomorrow afternoon (Tuesday) at 4pm BST. As always, calls are open to all! If you have anything you'd like to bring up, please add it to the agenda. Agenda: https://github.com/mirage/mirage-www/wiki/Call-Agenda GoToMeeting details are below but if there are any hiccups/delays with this, I'll switch to a public Google Hangout. If that happens, I'll post the link here and also in the IRC channel (#mirage on freenode). Join us at 4pm BST tomorrow! 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Dial in numbers (ask if you need a specific country): United Kingdom: +44 (0) 20 3657 6778 United States: +1 (213) 493-0014 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Best wishes, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel