From mirageos-devel-bounces@lists.xenproject.org Fri Aug 01 07:36:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 01 Aug 2014 07: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 1XD7Nk-00014q-IR; Fri, 01 Aug 2014 07:36:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XD7Ni-00014l-Hj for mirageos-devel@lists.xenproject.org; Fri, 01 Aug 2014 07:36:02 +0000 Received: from [85.158.137.68:26249] by server-12.bemta-3.messagelabs.com id E7/00-02460-1634BD35; Fri, 01 Aug 2014 07:36:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1406878558!11277664!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 1849 invoked from network); 1 Aug 2014 07:35:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 1 Aug 2014 07:35:58 -0000 Received: (qmail 23277 invoked by uid 634); 1 Aug 2014 07:35:57 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 01 Aug 2014 08:35:56 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 1 Aug 2014 08:35:55 +0100 Message-Id: <3852300D-6679-4599-BF92-ACDE67DF3405@recoil.org> References: <12C67A1EEC419342AF5E59DA31562C3F0D9039AE90@EXCHANGE1.ad.nottingham.ac.uk> To: Masoud Koleini 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] Lwt is deprecated - Async? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 mirrored this thread on https://github.com/mirage/mirage/issues/282 to make it easier to keep track of progress towards an Async_xen. -anil On 2 Jul 2014, at 08:46, Anil Madhavapeddy wrote: > On 1 Jul 2014, at 20:28, Masoud Koleini wrote: > >> Hi All, >> >> I am working on porting Frenetic OpenFlow to Mirage. Recently, Frenetic has replaced Lwt library with Async, since Lwt is now deprecated and not actively maintained. >> >> Is there any plan to support Async in future Mirage developments? Do you have any suggestion to make Frenetic, or any Async based code, to interact with Mirage Lwt-based libraries? > > Hi Masoud, > > Great to hear that you're porting Frenetic to Mirage! We've been making steady progress on porting Async to the Xen backend, but it's still going to take some time to complete. Here's the steps: > > - Lwt splits out the logical threading core (the Lwt module) and the Unix-specific execution portions (Lwt_unix). Async needs to be restructured along similar lines, which has already begun: there is a Core_kernel that is Unix-independent and is used by our Irmin db. There is also an Async_kernel. > > - An Async_xen needs to be written which implements the subset of Async_unix functionality necessary to drive traffic. Async_unix is much bigger than Lwt_unix, so finding a viable subset is important (for instance, Async_unix.Reader and Async_xen.Reader need to have a similar module type, but cannot be exactly the same). > > - Frenetic needs to use Async_kernel in the OS-independent portions, instead of using Async (which packs in both Async_kernel and Async_unix). > > In the short term, it's worth porting the low-level protocol portions first, for instance the Openflow switch logic. Haris did some of this last year, so it's worth figuring out the differences between that Openflow switch and the Frenetic interfaces, and ensuring that they are compatible. > > A Mirage OpenFlow switch, with a controller running in a Unix VM (perhaps connected via vchan) is something that wouldn't take too long to build, and doesn't require the full Async port to be completed since the controller could run under Unix for now. > > Let me know if this e-mail made any sense, Masoud :-) Happy to clarify further. > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Aug 01 07:36:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 01 Aug 2014 07: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 1XD7Nk-00014q-IR; Fri, 01 Aug 2014 07:36:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XD7Ni-00014l-Hj for mirageos-devel@lists.xenproject.org; Fri, 01 Aug 2014 07:36:02 +0000 Received: from [85.158.137.68:26249] by server-12.bemta-3.messagelabs.com id E7/00-02460-1634BD35; Fri, 01 Aug 2014 07:36:01 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1406878558!11277664!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 1849 invoked from network); 1 Aug 2014 07:35:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 1 Aug 2014 07:35:58 -0000 Received: (qmail 23277 invoked by uid 634); 1 Aug 2014 07:35:57 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 01 Aug 2014 08:35:56 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 1 Aug 2014 08:35:55 +0100 Message-Id: <3852300D-6679-4599-BF92-ACDE67DF3405@recoil.org> References: <12C67A1EEC419342AF5E59DA31562C3F0D9039AE90@EXCHANGE1.ad.nottingham.ac.uk> To: Masoud Koleini 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] Lwt is deprecated - Async? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 mirrored this thread on https://github.com/mirage/mirage/issues/282 to make it easier to keep track of progress towards an Async_xen. -anil On 2 Jul 2014, at 08:46, Anil Madhavapeddy wrote: > On 1 Jul 2014, at 20:28, Masoud Koleini wrote: > >> Hi All, >> >> I am working on porting Frenetic OpenFlow to Mirage. Recently, Frenetic has replaced Lwt library with Async, since Lwt is now deprecated and not actively maintained. >> >> Is there any plan to support Async in future Mirage developments? Do you have any suggestion to make Frenetic, or any Async based code, to interact with Mirage Lwt-based libraries? > > Hi Masoud, > > Great to hear that you're porting Frenetic to Mirage! We've been making steady progress on porting Async to the Xen backend, but it's still going to take some time to complete. Here's the steps: > > - Lwt splits out the logical threading core (the Lwt module) and the Unix-specific execution portions (Lwt_unix). Async needs to be restructured along similar lines, which has already begun: there is a Core_kernel that is Unix-independent and is used by our Irmin db. There is also an Async_kernel. > > - An Async_xen needs to be written which implements the subset of Async_unix functionality necessary to drive traffic. Async_unix is much bigger than Lwt_unix, so finding a viable subset is important (for instance, Async_unix.Reader and Async_xen.Reader need to have a similar module type, but cannot be exactly the same). > > - Frenetic needs to use Async_kernel in the OS-independent portions, instead of using Async (which packs in both Async_kernel and Async_unix). > > In the short term, it's worth porting the low-level protocol portions first, for instance the Openflow switch logic. Haris did some of this last year, so it's worth figuring out the differences between that Openflow switch and the Frenetic interfaces, and ensuring that they are compatible. > > A Mirage OpenFlow switch, with a controller running in a Unix VM (perhaps connected via vchan) is something that wouldn't take too long to build, and doesn't require the full Async port to be completed since the controller could run under Unix for now. > > Let me know if this e-mail made any sense, Masoud :-) Happy to clarify further. > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Aug 01 15:08:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 01 Aug 2014 15:08: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 1XDERv-0001Rc-Hs; Fri, 01 Aug 2014 15:08:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDERu-0001R9-54 for mirageos-devel@lists.xenproject.org; Fri, 01 Aug 2014 15:08:50 +0000 Received: from [85.158.139.211:35097] by server-6.bemta-5.messagelabs.com id DE/10-06284-18DABD35; Fri, 01 Aug 2014 15:08:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1406905727!8483575!1 X-Originating-IP: [74.125.82.46] 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 15114 invoked from network); 1 Aug 2014 15:08:47 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Aug 2014 15:08:47 -0000 Received: by mail-wg0-f46.google.com with SMTP id m15so4400330wgh.5 for ; Fri, 01 Aug 2014 08:08:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=lO44GlKfTqyrPhAQ79upeoHlNLc0nB+Q5cMS2eL0Fxw=; b=KIeiN9y0hVtMltW/2Z6fR5XJyoIjZzOAiyAGkISsdHb/TJ2LVhZnX2k9bEv90LNcA5 6kttyePWVNZUA7AB6Fc1YIExKXfDGYv9Ej3erklOhGuNBZd/dGX4h8uu3swEpIKhm07L +d86QqmwwngrFMSPtLID5nIShAQsRbI7DRAdLdqwPKz8CQUlqLauA89Q+XWpVOntzjrB M6Jk8YL1QjoZWPSb4D56pUlOr7hq0koTeBxGoeq0TJ/1TtoGAB6RvPh6HSQJiMSBUIjH zwyPFrcEueTthfKINQRcZ/P0B7aC9t0yDpUXWu+lunUrhdYSbzsEgAw6GbWBV8q7QKuX Z1qg== X-Received: by 10.180.94.234 with SMTP id df10mr7883301wib.76.1406905726116; Fri, 01 Aug 2014 08:08:46 -0700 (PDT) Received: from [172.16.26.11] (host86-174-110-189.range86-174.btcentralplus.com. [86.174.110.189]) by mx.google.com with ESMTPSA id k19sm9488183wie.20.2014.08.01.08.08.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Aug 2014 08:08:45 -0700 (PDT) Message-ID: <53DBAD7B.3070206@xen.org> Date: Fri, 01 Aug 2014 16:08:43 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] 2 weeks to Xen Project Developer Summit : Chicago 18-19, IL, USA X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4958262191533607349==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============4958262191533607349== Content-Type: multipart/alternative; boundary="------------030802000806030202040207" This is a multi-part message in MIME format. --------------030802000806030202040207 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Only last week, the Xen Project team was at OSCON where we launched Mirage OS 2.0 (event report to follow soon, but in the meantime check out the following sessions Nymote and Mirage , Floss Weekly on Mirage OS and Community War Stories ) and now our Developer Summit is just round the corner. As we have seen tremendous community growth in the last 12 months (>30%) and the most feature reach Xen Project Hypervisor release coming up soon, I thought I'd share what you can expect. What to expect? Xen Project Developer Summits are packed with highly technical content where the core developers of the Xen Project community come together to discuss the evolution of the Xen Project. The conference is a mixture of talks and interactive sessions in un-conference format (which we call BoFs). Newcomers and those who are interested in the progress and future of the Xen Project, it's sub projects (Hypervisor on ARM and x86, Upstreams and Downstreams, Embedded and Automotive variants, Cloud Operating Systems such as Mirage OS) usually will get tremendous value from attending the event. Besides roadmap, feature updates and developer topics, this year features a few themes: * Network Function Virtualization * Security * Performance and Scalability * Cloud Operating Systems * Topics that are important for automotive/embedded/mobile use-cases, such as Real-time virtualization, certification and ARM support Why not check out the agenda or watch last year's sessions to get a sense of what is coming. Note that BoF's and discussion groups will be published next week. Register for The Developer Meeting on Aug 20th If you are planning to attend the Developer Meeting on Aug 20th, please do sign up at http://wiki.xenproject.org/wiki/Developer_Meeting/Aug2014 such that I get a sense of numbers and can order the right amount of food. How to get the most out of the Summit? Our developer events are designed to help you make connections and to participate. A good way to network are our evening social event and to network during the breaks. Another great way to get the most out of the summit is to submit a BoF/discussion groups about a topic you care about or to participate in a BoF/discussion group. BoF submissions are open until August 11 and the BoF schedule will be published the week before the event. Most of our talks will have an extensive and interactive Q&A portion, which is another way to engage. Links: http://events.linuxfoundation.org/events/xen-project-developer-summit/program/schedule http://events.linuxfoundation.org/events/xen-project-developer-summit/attend/register http://events.linuxfoundation.org/events/xen-project-developer-summit --------------030802000806030202040207 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Only last week, the Xen Project team was at OSCON where we launched Mirage OS 2.0(event report to follow soon, but in the meantime check out the following sessions Nymote and Mirage, Floss Weekly on Mirage OS and Community War Stories) and now our Developer Summit is just round the corner. As we have seen tremendous community growth in the last 12 months (>30%) and the most feature reach Xen Project Hypervisor release coming up soon, I thought I’d share what you can expect.

What to expect?

Xen Project Developer Summits are packed with highly technical content where the core developers of the Xen Project community come together to discuss the evolution of the Xen Project. The conference is a mixture of talks and interactive sessions in un-conference format (which we call BoFs). Newcomers and those who are interested in the progress and future of the Xen Project, it’s sub projects (Hypervisor on ARM and x86, Upstreams and Downstreams, Embedded and Automotive variants, Cloud Operating Systems such as Mirage OS) usually will get tremendous value from attending the event.

Besides roadmap, feature updates and developer topics, this year features a few themes:

  • Network Function Virtualization
  • Security
  • Performance and Scalability
  • Cloud Operating Systems
  • Topics that are important for automotive/embedded/mobile use-cases, such as Real-time virtualization, certification and ARM support

Why not check out the agenda or watch last year’s sessions to get a sense of what is coming. Note that BoF’s and discussion groups will be published next week.

Register for The Developer Meeting on Aug 20th

If you are planning to attend the Developer Meeting on Aug 20th, please do sign up at http://wiki.xenproject.org/wiki/Developer_Meeting/Aug2014 such that I get a sense of numbers and can order the right amount of food.

How to get the most out of the Summit?

Our developer events are designed to help you make connections and to participate. A good way to network are our evening social event and to network during the breaks. Another great way to get the most out of the summit is to submit a BoF/discussion groups about a topic you care about or to participate in a BoF/discussion group. BoF submissions are open until August 11 and the BoF schedule will be published the week before the event. Most of our talks will have an extensive and interactive Q&A portion, which is another way to engage.

Links:

http://events.linuxfoundation.org/events/xen-project-developer-summit/program/schedule
http://events.linuxfoundation.org/events/xen-project-developer-summit/attend/register
http://events.linuxfoundation.org/events/xen-project-developer-summit

--------------030802000806030202040207-- --===============4958262191533607349== 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 --===============4958262191533607349==-- From mirageos-devel-bounces@lists.xenproject.org Fri Aug 01 15:08:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 01 Aug 2014 15:08: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 1XDERv-0001Rc-Hs; Fri, 01 Aug 2014 15:08:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDERu-0001R9-54 for mirageos-devel@lists.xenproject.org; Fri, 01 Aug 2014 15:08:50 +0000 Received: from [85.158.139.211:35097] by server-6.bemta-5.messagelabs.com id DE/10-06284-18DABD35; Fri, 01 Aug 2014 15:08:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1406905727!8483575!1 X-Originating-IP: [74.125.82.46] 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 15114 invoked from network); 1 Aug 2014 15:08:47 -0000 Received: from mail-wg0-f46.google.com (HELO mail-wg0-f46.google.com) (74.125.82.46) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 1 Aug 2014 15:08:47 -0000 Received: by mail-wg0-f46.google.com with SMTP id m15so4400330wgh.5 for ; Fri, 01 Aug 2014 08:08:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type; bh=lO44GlKfTqyrPhAQ79upeoHlNLc0nB+Q5cMS2eL0Fxw=; b=KIeiN9y0hVtMltW/2Z6fR5XJyoIjZzOAiyAGkISsdHb/TJ2LVhZnX2k9bEv90LNcA5 6kttyePWVNZUA7AB6Fc1YIExKXfDGYv9Ej3erklOhGuNBZd/dGX4h8uu3swEpIKhm07L +d86QqmwwngrFMSPtLID5nIShAQsRbI7DRAdLdqwPKz8CQUlqLauA89Q+XWpVOntzjrB M6Jk8YL1QjoZWPSb4D56pUlOr7hq0koTeBxGoeq0TJ/1TtoGAB6RvPh6HSQJiMSBUIjH zwyPFrcEueTthfKINQRcZ/P0B7aC9t0yDpUXWu+lunUrhdYSbzsEgAw6GbWBV8q7QKuX Z1qg== X-Received: by 10.180.94.234 with SMTP id df10mr7883301wib.76.1406905726116; Fri, 01 Aug 2014 08:08:46 -0700 (PDT) Received: from [172.16.26.11] (host86-174-110-189.range86-174.btcentralplus.com. [86.174.110.189]) by mx.google.com with ESMTPSA id k19sm9488183wie.20.2014.08.01.08.08.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Aug 2014 08:08:45 -0700 (PDT) Message-ID: <53DBAD7B.3070206@xen.org> Date: Fri, 01 Aug 2014 16:08:43 +0100 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] 2 weeks to Xen Project Developer Summit : Chicago 18-19, IL, USA X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4958262191533607349==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============4958262191533607349== Content-Type: multipart/alternative; boundary="------------030802000806030202040207" This is a multi-part message in MIME format. --------------030802000806030202040207 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Only last week, the Xen Project team was at OSCON where we launched Mirage OS 2.0 (event report to follow soon, but in the meantime check out the following sessions Nymote and Mirage , Floss Weekly on Mirage OS and Community War Stories ) and now our Developer Summit is just round the corner. As we have seen tremendous community growth in the last 12 months (>30%) and the most feature reach Xen Project Hypervisor release coming up soon, I thought I'd share what you can expect. What to expect? Xen Project Developer Summits are packed with highly technical content where the core developers of the Xen Project community come together to discuss the evolution of the Xen Project. The conference is a mixture of talks and interactive sessions in un-conference format (which we call BoFs). Newcomers and those who are interested in the progress and future of the Xen Project, it's sub projects (Hypervisor on ARM and x86, Upstreams and Downstreams, Embedded and Automotive variants, Cloud Operating Systems such as Mirage OS) usually will get tremendous value from attending the event. Besides roadmap, feature updates and developer topics, this year features a few themes: * Network Function Virtualization * Security * Performance and Scalability * Cloud Operating Systems * Topics that are important for automotive/embedded/mobile use-cases, such as Real-time virtualization, certification and ARM support Why not check out the agenda or watch last year's sessions to get a sense of what is coming. Note that BoF's and discussion groups will be published next week. Register for The Developer Meeting on Aug 20th If you are planning to attend the Developer Meeting on Aug 20th, please do sign up at http://wiki.xenproject.org/wiki/Developer_Meeting/Aug2014 such that I get a sense of numbers and can order the right amount of food. How to get the most out of the Summit? Our developer events are designed to help you make connections and to participate. A good way to network are our evening social event and to network during the breaks. Another great way to get the most out of the summit is to submit a BoF/discussion groups about a topic you care about or to participate in a BoF/discussion group. BoF submissions are open until August 11 and the BoF schedule will be published the week before the event. Most of our talks will have an extensive and interactive Q&A portion, which is another way to engage. Links: http://events.linuxfoundation.org/events/xen-project-developer-summit/program/schedule http://events.linuxfoundation.org/events/xen-project-developer-summit/attend/register http://events.linuxfoundation.org/events/xen-project-developer-summit --------------030802000806030202040207 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

Only last week, the Xen Project team was at OSCON where we launched Mirage OS 2.0(event report to follow soon, but in the meantime check out the following sessions Nymote and Mirage, Floss Weekly on Mirage OS and Community War Stories) and now our Developer Summit is just round the corner. As we have seen tremendous community growth in the last 12 months (>30%) and the most feature reach Xen Project Hypervisor release coming up soon, I thought I’d share what you can expect.

What to expect?

Xen Project Developer Summits are packed with highly technical content where the core developers of the Xen Project community come together to discuss the evolution of the Xen Project. The conference is a mixture of talks and interactive sessions in un-conference format (which we call BoFs). Newcomers and those who are interested in the progress and future of the Xen Project, it’s sub projects (Hypervisor on ARM and x86, Upstreams and Downstreams, Embedded and Automotive variants, Cloud Operating Systems such as Mirage OS) usually will get tremendous value from attending the event.

Besides roadmap, feature updates and developer topics, this year features a few themes:

  • Network Function Virtualization
  • Security
  • Performance and Scalability
  • Cloud Operating Systems
  • Topics that are important for automotive/embedded/mobile use-cases, such as Real-time virtualization, certification and ARM support

Why not check out the agenda or watch last year’s sessions to get a sense of what is coming. Note that BoF’s and discussion groups will be published next week.

Register for The Developer Meeting on Aug 20th

If you are planning to attend the Developer Meeting on Aug 20th, please do sign up at http://wiki.xenproject.org/wiki/Developer_Meeting/Aug2014 such that I get a sense of numbers and can order the right amount of food.

How to get the most out of the Summit?

Our developer events are designed to help you make connections and to participate. A good way to network are our evening social event and to network during the breaks. Another great way to get the most out of the summit is to submit a BoF/discussion groups about a topic you care about or to participate in a BoF/discussion group. BoF submissions are open until August 11 and the BoF schedule will be published the week before the event. Most of our talks will have an extensive and interactive Q&A portion, which is another way to engage.

Links:

http://events.linuxfoundation.org/events/xen-project-developer-summit/program/schedule
http://events.linuxfoundation.org/events/xen-project-developer-summit/attend/register
http://events.linuxfoundation.org/events/xen-project-developer-summit

--------------030802000806030202040207-- --===============4958262191533607349== 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 --===============4958262191533607349==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 11:18:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 11:18: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 1XDtnl-000622-4G; Sun, 03 Aug 2014 11:18:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDtnj-00061u-Ep for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 11:18:07 +0000 Received: from [85.158.143.35:40874] by server-3.bemta-4.messagelabs.com id 92/89-06192-E6A1ED35; Sun, 03 Aug 2014 11:18:06 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-21.messagelabs.com!1407064685!13170389!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1531 invoked from network); 3 Aug 2014 11:18:05 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-21.messagelabs.com with SMTP; 3 Aug 2014 11:18:05 -0000 Received: (qmail 27540 invoked by uid 634); 3 Aug 2014 11:18:04 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 12:18:03 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> Date: Sun, 3 Aug 2014 12:18:02 +0100 Message-Id: <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> To: Gregory Tsipenyuk 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] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5308227215772652230==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5308227215772652230== Content-Type: multipart/alternative; boundary="Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C" --Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi Gregory, [ccing mirageos-devel] The root cause of this issue is a clash with top-level module names. = Somewhere in your library dependency chain, something has also defined a = module called "Base64" that is different from the one that Nocrypto = thinks its using. One way to fix this is by not exposing a library's internal modules to = the outside world by packing them inside a single top-level module. = Cohttp is one example of a library that does this. (see = https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-ty= pe-checking.html#modules-and-separate-compilation for more information = on packing). It's difficult to workaround this without just fixing the libraries = themselves -- although you will never get a segfault (as would happen in = C if you mix up object files), the compiler will just reject = inconsistent library checksums all the time. I'm not sure which makefile you're referring to (vs oasis below), but = perhaps David and Hannes can comment on whether they can pack the = various crypto libraries for easier use. Also, we could just pull Base64 into a separate OPAM package since it's = very commonly cut-and-pasted. I've taken a quick shot at this on = https://github.com/mirage/ocaml-base64. This is a different = implementation (but possibly the same spec) as nocrypto's, so needs some = review to see if they're compatible or not (padding is possibly slightly = different). -anil On 2 Aug 2014, at 13:08, Gregory Tsipenyuk wrote: > Hi Anil, >=20 > I got another =93inconsistent assumptions=94 issue. It looks like it = is similar to the one I opened a few days ago against asn1-combinators. = Nocrypto does have its own Base64 module. What puzzles me though is that = it fails if I build with oasis generated stuff and if I build with the = regular Makefile then it builds. Can you think of any flags that I can = tweak to fix it? >=20 > Thanks, > Gregory=20 >=20 > File "_none_", line 1: > Error: Files utils.cmx > and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa > make inconsistent assumptions over interface Base64 > Command exited with code 2 --Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Hi = Gregory, [ccing mirageos-devel]

The root cause of = this issue is a clash with top-level module names.  Somewhere in = your library dependency chain, something has also defined a module = called "Base64" that is different from the one that Nocrypto thinks its = using.

One way to fix this is by not exposing a = library's internal modules to the outside world by packing them inside a = single top-level module.  Cohttp is one example of a library that = does this.  (see https://realwor= ldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.htm= l#modules-and-separate-compilation for more information on = packing).

It's difficult to workaround this = without just fixing the libraries themselves -- although you will never = get a segfault (as would happen in C if you mix up object files), the = compiler will just reject inconsistent library checksums all the = time.

I'm not sure which makefile you're = referring to (vs oasis below), but perhaps David and Hannes can comment = on whether they can pack the various crypto libraries for easier = use.

Also, we could just pull Base64 into a = separate OPAM package since it's very commonly cut-and-pasted. =  I've taken a quick shot at this on https://github.com/mirage/= ocaml-base64.  This is a different implementation (but possibly = the same spec) as nocrypto's, so needs some review to see if they're = compatible or not (padding is possibly slightly = different).

-anil

<= div>On 2 Aug 2014, at 13:08, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Hi Anil,

I got another = =93inconsistent assumptions=94 issue. It looks like it is similar to the = one I opened a few days ago against asn1-combinators. Nocrypto does have = its own Base64 module. What puzzles me though is that  it fails if = I build with oasis generated stuff and if I build with the regular = Makefile then it builds. Can you think of any flags that I can tweak to = fix = it?

Thanks,
Gregory 
File "_none_", line 1:
Error: Files utils.cmx
   =     and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa
   =     make inconsistent assumptions over interface = Base64
Command exited with code = 2

= --Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C-- --===============5308227215772652230== 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 --===============5308227215772652230==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 11:18:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 11:18: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 1XDtnl-000622-4G; Sun, 03 Aug 2014 11:18:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDtnj-00061u-Ep for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 11:18:07 +0000 Received: from [85.158.143.35:40874] by server-3.bemta-4.messagelabs.com id 92/89-06192-E6A1ED35; Sun, 03 Aug 2014 11:18:06 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-21.messagelabs.com!1407064685!13170389!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1531 invoked from network); 3 Aug 2014 11:18:05 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-21.messagelabs.com with SMTP; 3 Aug 2014 11:18:05 -0000 Received: (qmail 27540 invoked by uid 634); 3 Aug 2014 11:18:04 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 12:18:03 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> Date: Sun, 3 Aug 2014 12:18:02 +0100 Message-Id: <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> To: Gregory Tsipenyuk 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] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5308227215772652230==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5308227215772652230== Content-Type: multipart/alternative; boundary="Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C" --Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi Gregory, [ccing mirageos-devel] The root cause of this issue is a clash with top-level module names. = Somewhere in your library dependency chain, something has also defined a = module called "Base64" that is different from the one that Nocrypto = thinks its using. One way to fix this is by not exposing a library's internal modules to = the outside world by packing them inside a single top-level module. = Cohttp is one example of a library that does this. (see = https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-ty= pe-checking.html#modules-and-separate-compilation for more information = on packing). It's difficult to workaround this without just fixing the libraries = themselves -- although you will never get a segfault (as would happen in = C if you mix up object files), the compiler will just reject = inconsistent library checksums all the time. I'm not sure which makefile you're referring to (vs oasis below), but = perhaps David and Hannes can comment on whether they can pack the = various crypto libraries for easier use. Also, we could just pull Base64 into a separate OPAM package since it's = very commonly cut-and-pasted. I've taken a quick shot at this on = https://github.com/mirage/ocaml-base64. This is a different = implementation (but possibly the same spec) as nocrypto's, so needs some = review to see if they're compatible or not (padding is possibly slightly = different). -anil On 2 Aug 2014, at 13:08, Gregory Tsipenyuk wrote: > Hi Anil, >=20 > I got another =93inconsistent assumptions=94 issue. It looks like it = is similar to the one I opened a few days ago against asn1-combinators. = Nocrypto does have its own Base64 module. What puzzles me though is that = it fails if I build with oasis generated stuff and if I build with the = regular Makefile then it builds. Can you think of any flags that I can = tweak to fix it? >=20 > Thanks, > Gregory=20 >=20 > File "_none_", line 1: > Error: Files utils.cmx > and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa > make inconsistent assumptions over interface Base64 > Command exited with code 2 --Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Hi = Gregory, [ccing mirageos-devel]

The root cause of = this issue is a clash with top-level module names.  Somewhere in = your library dependency chain, something has also defined a module = called "Base64" that is different from the one that Nocrypto thinks its = using.

One way to fix this is by not exposing a = library's internal modules to the outside world by packing them inside a = single top-level module.  Cohttp is one example of a library that = does this.  (see https://realwor= ldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.htm= l#modules-and-separate-compilation for more information on = packing).

It's difficult to workaround this = without just fixing the libraries themselves -- although you will never = get a segfault (as would happen in C if you mix up object files), the = compiler will just reject inconsistent library checksums all the = time.

I'm not sure which makefile you're = referring to (vs oasis below), but perhaps David and Hannes can comment = on whether they can pack the various crypto libraries for easier = use.

Also, we could just pull Base64 into a = separate OPAM package since it's very commonly cut-and-pasted. =  I've taken a quick shot at this on https://github.com/mirage/= ocaml-base64.  This is a different implementation (but possibly = the same spec) as nocrypto's, so needs some review to see if they're = compatible or not (padding is possibly slightly = different).

-anil

<= div>On 2 Aug 2014, at 13:08, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Hi Anil,

I got another = =93inconsistent assumptions=94 issue. It looks like it is similar to the = one I opened a few days ago against asn1-combinators. Nocrypto does have = its own Base64 module. What puzzles me though is that  it fails if = I build with oasis generated stuff and if I build with the regular = Makefile then it builds. Can you think of any flags that I can tweak to = fix = it?

Thanks,
Gregory 
File "_none_", line 1:
Error: Files utils.cmx
   =     and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa
   =     make inconsistent assumptions over interface = Base64
Command exited with code = 2

= --Apple-Mail=_54F6AB43-BBF6-4354-9084-C876FA66D79C-- --===============5308227215772652230== 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 --===============5308227215772652230==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 11:43:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 11:43: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 1XDuCg-0006AX-6J; Sun, 03 Aug 2014 11:43:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDuCe-0006AS-QR for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 11:43:52 +0000 Received: from [85.158.139.211:30547] by server-17.bemta-5.messagelabs.com id CF/B8-08943-7702ED35; Sun, 03 Aug 2014 11:43:51 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-16.tower-206.messagelabs.com!1407066231!8691517!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 8572 invoked from network); 3 Aug 2014 11:43:51 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Aug 2014 11:43:51 -0000 Received: from [192.168.1.5] (host-92-13-194-67.as43234.net [92.13.194.67]) (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 BFF3D1839 for ; Sun, 3 Aug 2014 13:43:49 +0200 (CEST) Message-ID: <53DE201D.802@mehnert.org> Date: Sun, 03 Aug 2014 12:42:21 +0100 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 References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> In-Reply-To: <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> Subject: Re: [MirageOS-devel] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 On 08/03/2014 12:18, Anil Madhavapeddy wrote: > Also, we could just pull Base64 into a separate OPAM package since > it's very commonly cut-and-pasted. I've taken a quick shot at > this on https://github.com/mirage/ocaml-base64. This is a > different implementation (but possibly the same spec) as > nocrypto's, so needs some review to see if they're compatible or > not (padding is possibly slightly different). While I didn't look into the algorithm, the interface is slightly different - string vs Cstruct.t -- and I wonder whether we should have an implementation providing both a string and Cstruct.t interface (because conversion includes copying)? Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJT3iAdAAoJELyJZYjffCjulCkP/isArzMjGk/IWwSfKE5nhJcj uNHajQOXeuSTjE7bKYn8oU61cNy8ktMYoMlPQxMXE5XRfhrGAoUJeXEbUJyarObf F76/fCSzC544ExRQa2oEoSvSHBBcuZNeSDCgrPCQ57J3eudpiNvoUpOmG14FvVTO ndOl5zNnPRslJk9vV/Cd7gDNvLygLKd4foMQZYxwQnHoCUxFARz5LWfWfF3bgqFa mb4HpD3gWgLmNYBrltG/BDnLxT6ipvdXonCVKbbkb8p1IVpf2JLwmyx4XM1xPluA pdQyotquM6hf5WkbJC9WXgiNPjC3B8jEif+A3ZivVjV7PZ++i5KGVtQG9BREQC1j /q/lxsRHrdpOIPy76Ue0oOFMr1QZYwO8IY9z9Q+jM9rvVe27fUE65WbKYTK7ecHI 7Sru61/uAxvcmqiO7sWEyOz0ykKEdF3VaT9csau6b6vesEwpl0+NSCkoixZhdBqj Tn5npelXnNCjLKT/xRFJ8C8Yj11MoGSUAM5fNHcEHcqO+jjvJrNrrpwn2FDryCDz fW/GlJTIwFXzbsCLv+SBB/+UVVmeqPTMk6Ly2DzBXOnYam6nAUkiuRvE+NDrB1jp Z1o5lxN4TEkwOHsWKHFSPOfu2jcJQL8JylzynKxCkf1ADnetfWfOt7LVwrhvEE6o liVMxTuS7nWLABXmhLkF =HHno -----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 Sun Aug 03 11:43:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 11:43: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 1XDuCg-0006AX-6J; Sun, 03 Aug 2014 11:43:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDuCe-0006AS-QR for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 11:43:52 +0000 Received: from [85.158.139.211:30547] by server-17.bemta-5.messagelabs.com id CF/B8-08943-7702ED35; Sun, 03 Aug 2014 11:43:51 +0000 X-Env-Sender: hannes@mehnert.org X-Msg-Ref: server-16.tower-206.messagelabs.com!1407066231!8691517!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 8572 invoked from network); 3 Aug 2014 11:43:51 -0000 Received: from mail.mehnert.org (HELO mail.mehnert.org) (213.73.89.200) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 3 Aug 2014 11:43:51 -0000 Received: from [192.168.1.5] (host-92-13-194-67.as43234.net [92.13.194.67]) (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 BFF3D1839 for ; Sun, 3 Aug 2014 13:43:49 +0200 (CEST) Message-ID: <53DE201D.802@mehnert.org> Date: Sun, 03 Aug 2014 12:42:21 +0100 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 References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> In-Reply-To: <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> Subject: Re: [MirageOS-devel] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 On 08/03/2014 12:18, Anil Madhavapeddy wrote: > Also, we could just pull Base64 into a separate OPAM package since > it's very commonly cut-and-pasted. I've taken a quick shot at > this on https://github.com/mirage/ocaml-base64. This is a > different implementation (but possibly the same spec) as > nocrypto's, so needs some review to see if they're compatible or > not (padding is possibly slightly different). While I didn't look into the algorithm, the interface is slightly different - string vs Cstruct.t -- and I wonder whether we should have an implementation providing both a string and Cstruct.t interface (because conversion includes copying)? Hannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCQAGBQJT3iAdAAoJELyJZYjffCjulCkP/isArzMjGk/IWwSfKE5nhJcj uNHajQOXeuSTjE7bKYn8oU61cNy8ktMYoMlPQxMXE5XRfhrGAoUJeXEbUJyarObf F76/fCSzC544ExRQa2oEoSvSHBBcuZNeSDCgrPCQ57J3eudpiNvoUpOmG14FvVTO ndOl5zNnPRslJk9vV/Cd7gDNvLygLKd4foMQZYxwQnHoCUxFARz5LWfWfF3bgqFa mb4HpD3gWgLmNYBrltG/BDnLxT6ipvdXonCVKbbkb8p1IVpf2JLwmyx4XM1xPluA pdQyotquM6hf5WkbJC9WXgiNPjC3B8jEif+A3ZivVjV7PZ++i5KGVtQG9BREQC1j /q/lxsRHrdpOIPy76Ue0oOFMr1QZYwO8IY9z9Q+jM9rvVe27fUE65WbKYTK7ecHI 7Sru61/uAxvcmqiO7sWEyOz0ykKEdF3VaT9csau6b6vesEwpl0+NSCkoixZhdBqj Tn5npelXnNCjLKT/xRFJ8C8Yj11MoGSUAM5fNHcEHcqO+jjvJrNrrpwn2FDryCDz fW/GlJTIwFXzbsCLv+SBB/+UVVmeqPTMk6Ly2DzBXOnYam6nAUkiuRvE+NDrB1jp Z1o5lxN4TEkwOHsWKHFSPOfu2jcJQL8JylzynKxCkf1ADnetfWfOt7LVwrhvEE6o liVMxTuS7nWLABXmhLkF =HHno -----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 Sun Aug 03 14:01:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 14:01: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 1XDwM3-0007X3-Q5; Sun, 03 Aug 2014 14:01:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDvV4-000715-8Y for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 13:06:58 +0000 Received: from [85.158.137.68:45023] by server-16.bemta-3.messagelabs.com id 1E/F5-14115-1F33ED35; Sun, 03 Aug 2014 13:06:57 +0000 X-Env-Sender: gt303@cam.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1407071215!11558732!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17698 invoked from network); 3 Aug 2014 13:06:56 -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; 3 Aug 2014 13:06:56 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc2-acto3-2-0-cust121.4-2.cable.virginm.net ([86.11.72.122]:50539 helo=[192.168.0.5]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpsa (PLAIN:gt303) (TLSv1:AES128-SHA:128) id 1XDvV1-0004RN-kO (Exim 4.82_3-c0e5623) (return-path ); Sun, 03 Aug 2014 14:06:55 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Gregory Tsipenyuk In-Reply-To: <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> Date: Sun, 3 Aug 2014 14:06:54 +0100 Message-Id: <87E52E42-16E7-4D31-A7F0-4DC5B003B71F@cam.ac.uk> References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) X-Mailman-Approved-At: Sun, 03 Aug 2014 14:01:43 +0000 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7756224945739030938==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7756224945739030938== Content-Type: multipart/alternative; boundary="Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467" --Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Anil, Thanks, I understand the clash issue. By regular Makefile I just mean a manually created Makefile that has = "ocamlbuild -use-ocamlfind=85 app.native=94 This builds.=20 I replaced Extlib.Base64 with Batteries.Base64, which doesn=92t conflict = with Nocrypto and builds, so I=92m good. The =93Core=94 conflict in asn1-combinators is more annoying as I have a = file used in both Async and Lwt and I wanted to use Core.Std.Io_channel = that works in both, but I think I have a work around for this too. Thanks, Gregory On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy wrote: > Hi Gregory, [ccing mirageos-devel] >=20 > The root cause of this issue is a clash with top-level module names. = Somewhere in your library dependency chain, something has also defined a = module called "Base64" that is different from the one that Nocrypto = thinks its using. >=20 > One way to fix this is by not exposing a library's internal modules to = the outside world by packing them inside a single top-level module. = Cohttp is one example of a library that does this. (see = https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-ty= pe-checking.html#modules-and-separate-compilation for more information = on packing). >=20 > It's difficult to workaround this without just fixing the libraries = themselves -- although you will never get a segfault (as would happen in = C if you mix up object files), the compiler will just reject = inconsistent library checksums all the time. >=20 > I'm not sure which makefile you're referring to (vs oasis below), but = perhaps David and Hannes can comment on whether they can pack the = various crypto libraries for easier use. >=20 > Also, we could just pull Base64 into a separate OPAM package since = it's very commonly cut-and-pasted. I've taken a quick shot at this on = https://github.com/mirage/ocaml-base64. This is a different = implementation (but possibly the same spec) as nocrypto's, so needs some = review to see if they're compatible or not (padding is possibly slightly = different). >=20 > -anil >=20 > On 2 Aug 2014, at 13:08, Gregory Tsipenyuk wrote: >=20 >> Hi Anil, >>=20 >> I got another =93inconsistent assumptions=94 issue. It looks like it = is similar to the one I opened a few days ago against asn1-combinators. = Nocrypto does have its own Base64 module. What puzzles me though is that = it fails if I build with oasis generated stuff and if I build with the = regular Makefile then it builds. Can you think of any flags that I can = tweak to fix it? >>=20 >> Thanks, >> Gregory=20 >>=20 >> File "_none_", line 1: >> Error: Files utils.cmx >> and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa >> make inconsistent assumptions over interface Base64 >> Command exited with code 2 >=20 --Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Anil,

Thanks, I understand the = clash issue.

By regular Makefile I just mean a = manually created Makefile that has "ocamlbuild -use-ocamlfind=85 app.native=94 This = builds. 

I replaced Extlib.Base64 with = Batteries.Base64, which doesn=92t conflict with Nocrypto and builds, so = I=92m good.

The =93Core=94 conflict in = asn1-combinators is more annoying as I have a file used in both Async = and Lwt and I wanted to use Core.Std.Io_channel that works in both, but = I think I have a work around for this = too.

Thanks,

Gregory

On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy = <anil@recoil.org> = wrote:

Hi = Gregory, [ccing mirageos-devel]

The root cause of = this issue is a clash with top-level module names.  Somewhere in = your library dependency chain, something has also defined a module = called "Base64" that is different from the one that Nocrypto thinks its = using.

One way to fix this is by not exposing a = library's internal modules to the outside world by packing them inside a = single top-level module.  Cohttp is one example of a library that = does this.  (see https://realwor= ldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.htm= l#modules-and-separate-compilation for more information on = packing).

It's difficult to workaround this = without just fixing the libraries themselves -- although you will never = get a segfault (as would happen in C if you mix up object files), the = compiler will just reject inconsistent library checksums all the = time.

I'm not sure which makefile you're = referring to (vs oasis below), but perhaps David and Hannes can comment = on whether they can pack the various crypto libraries for easier = use.

Also, we could just pull Base64 into a = separate OPAM package since it's very commonly cut-and-pasted. =  I've taken a quick shot at this on https://github.com/mirage/= ocaml-base64.  This is a different implementation (but possibly = the same spec) as nocrypto's, so needs some review to see if they're = compatible or not (padding is possibly slightly = different).

-anil

<= div>On 2 Aug 2014, at 13:08, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Hi Anil,

I got another = =93inconsistent assumptions=94 issue. It looks like it is similar to the = one I opened a few days ago against asn1-combinators. Nocrypto does have = its own Base64 module. What puzzles me though is that  it fails if = I build with oasis generated stuff and if I build with the regular = Makefile then it builds. Can you think of any flags that I can tweak to = fix = it?

Thanks,
Gregory 
File "_none_", line 1:
Error: Files utils.cmx
   =     and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa
   =     make inconsistent assumptions over interface = Base64
Command exited with code = 2

<= br>
= --Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467-- --===============7756224945739030938== 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 --===============7756224945739030938==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 14:01:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 14:01: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 1XDwM3-0007X3-Q5; Sun, 03 Aug 2014 14:01:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDvV4-000715-8Y for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 13:06:58 +0000 Received: from [85.158.137.68:45023] by server-16.bemta-3.messagelabs.com id 1E/F5-14115-1F33ED35; Sun, 03 Aug 2014 13:06:57 +0000 X-Env-Sender: gt303@cam.ac.uk X-Msg-Ref: server-16.tower-31.messagelabs.com!1407071215!11558732!1 X-Originating-IP: [131.111.8.140] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17698 invoked from network); 3 Aug 2014 13:06:56 -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; 3 Aug 2014 13:06:56 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc2-acto3-2-0-cust121.4-2.cable.virginm.net ([86.11.72.122]:50539 helo=[192.168.0.5]) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpsa (PLAIN:gt303) (TLSv1:AES128-SHA:128) id 1XDvV1-0004RN-kO (Exim 4.82_3-c0e5623) (return-path ); Sun, 03 Aug 2014 14:06:55 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Gregory Tsipenyuk In-Reply-To: <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> Date: Sun, 3 Aug 2014 14:06:54 +0100 Message-Id: <87E52E42-16E7-4D31-A7F0-4DC5B003B71F@cam.ac.uk> References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) X-Mailman-Approved-At: Sun, 03 Aug 2014 14:01:43 +0000 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7756224945739030938==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7756224945739030938== Content-Type: multipart/alternative; boundary="Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467" --Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Anil, Thanks, I understand the clash issue. By regular Makefile I just mean a manually created Makefile that has = "ocamlbuild -use-ocamlfind=85 app.native=94 This builds.=20 I replaced Extlib.Base64 with Batteries.Base64, which doesn=92t conflict = with Nocrypto and builds, so I=92m good. The =93Core=94 conflict in asn1-combinators is more annoying as I have a = file used in both Async and Lwt and I wanted to use Core.Std.Io_channel = that works in both, but I think I have a work around for this too. Thanks, Gregory On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy wrote: > Hi Gregory, [ccing mirageos-devel] >=20 > The root cause of this issue is a clash with top-level module names. = Somewhere in your library dependency chain, something has also defined a = module called "Base64" that is different from the one that Nocrypto = thinks its using. >=20 > One way to fix this is by not exposing a library's internal modules to = the outside world by packing them inside a single top-level module. = Cohttp is one example of a library that does this. (see = https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-ty= pe-checking.html#modules-and-separate-compilation for more information = on packing). >=20 > It's difficult to workaround this without just fixing the libraries = themselves -- although you will never get a segfault (as would happen in = C if you mix up object files), the compiler will just reject = inconsistent library checksums all the time. >=20 > I'm not sure which makefile you're referring to (vs oasis below), but = perhaps David and Hannes can comment on whether they can pack the = various crypto libraries for easier use. >=20 > Also, we could just pull Base64 into a separate OPAM package since = it's very commonly cut-and-pasted. I've taken a quick shot at this on = https://github.com/mirage/ocaml-base64. This is a different = implementation (but possibly the same spec) as nocrypto's, so needs some = review to see if they're compatible or not (padding is possibly slightly = different). >=20 > -anil >=20 > On 2 Aug 2014, at 13:08, Gregory Tsipenyuk wrote: >=20 >> Hi Anil, >>=20 >> I got another =93inconsistent assumptions=94 issue. It looks like it = is similar to the one I opened a few days ago against asn1-combinators. = Nocrypto does have its own Base64 module. What puzzles me though is that = it fails if I build with oasis generated stuff and if I build with the = regular Makefile then it builds. Can you think of any flags that I can = tweak to fix it? >>=20 >> Thanks, >> Gregory=20 >>=20 >> File "_none_", line 1: >> Error: Files utils.cmx >> and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa >> make inconsistent assumptions over interface Base64 >> Command exited with code 2 >=20 --Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Anil,

Thanks, I understand the = clash issue.

By regular Makefile I just mean a = manually created Makefile that has "ocamlbuild -use-ocamlfind=85 app.native=94 This = builds. 

I replaced Extlib.Base64 with = Batteries.Base64, which doesn=92t conflict with Nocrypto and builds, so = I=92m good.

The =93Core=94 conflict in = asn1-combinators is more annoying as I have a file used in both Async = and Lwt and I wanted to use Core.Std.Io_channel that works in both, but = I think I have a work around for this = too.

Thanks,

Gregory

On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy = <anil@recoil.org> = wrote:

Hi = Gregory, [ccing mirageos-devel]

The root cause of = this issue is a clash with top-level module names.  Somewhere in = your library dependency chain, something has also defined a module = called "Base64" that is different from the one that Nocrypto thinks its = using.

One way to fix this is by not exposing a = library's internal modules to the outside world by packing them inside a = single top-level module.  Cohttp is one example of a library that = does this.  (see https://realwor= ldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.htm= l#modules-and-separate-compilation for more information on = packing).

It's difficult to workaround this = without just fixing the libraries themselves -- although you will never = get a segfault (as would happen in C if you mix up object files), the = compiler will just reject inconsistent library checksums all the = time.

I'm not sure which makefile you're = referring to (vs oasis below), but perhaps David and Hannes can comment = on whether they can pack the various crypto libraries for easier = use.

Also, we could just pull Base64 into a = separate OPAM package since it's very commonly cut-and-pasted. =  I've taken a quick shot at this on https://github.com/mirage/= ocaml-base64.  This is a different implementation (but possibly = the same spec) as nocrypto's, so needs some review to see if they're = compatible or not (padding is possibly slightly = different).

-anil

<= div>On 2 Aug 2014, at 13:08, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Hi Anil,

I got another = =93inconsistent assumptions=94 issue. It looks like it is similar to the = one I opened a few days ago against asn1-combinators. Nocrypto does have = its own Base64 module. What puzzles me though is that  it fails if = I build with oasis generated stuff and if I build with the regular = Makefile then it builds. Can you think of any flags that I can tweak to = fix = it?

Thanks,
Gregory 
File "_none_", line 1:
Error: Files utils.cmx
   =     and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa
   =     make inconsistent assumptions over interface = Base64
Command exited with code = 2

<= br>
= --Apple-Mail=_21E49CB9-186A-4887-BED8-3B5C27C65467-- --===============7756224945739030938== 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 --===============7756224945739030938==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 14:04:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 14:04: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 1XDwOh-0007Yy-2e; Sun, 03 Aug 2014 14:04:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDwOg-0007Yt-11 for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 14:04:26 +0000 Received: from [85.158.137.68:42689] by server-13.bemta-3.messagelabs.com id 93/0D-09942-9614ED35; Sun, 03 Aug 2014 14:04:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1407074663!7842411!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16816 invoked from network); 3 Aug 2014 14:04:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 3 Aug 2014 14:04:23 -0000 Received: (qmail 7901 invoked by uid 634); 3 Aug 2014 14:04: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 m.cb1.com (HELO [192.168.1.94]) (217.155.139.150) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 15:04:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <87E52E42-16E7-4D31-A7F0-4DC5B003B71F@cam.ac.uk> Date: Sun, 3 Aug 2014 15:04:20 +0100 Message-Id: References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> <87E52E42-16E7-4D31-A7F0-4DC5B003B71F@cam.ac.uk> To: Gregory Tsipenyuk 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] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1683333006645514692==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1683333006645514692== Content-Type: multipart/alternative; boundary="Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8" --Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 The manual makefile probably doesn't pull in as many dependencies. The = real answer here is just to fix the upstream I think, as it'll block any = non-trivial uses of the OCaml TLS stack. -anil On 3 Aug 2014, at 14:06, Gregory Tsipenyuk wrote: > Anil, >=20 > Thanks, I understand the clash issue. >=20 > By regular Makefile I just mean a manually created Makefile that has = "ocamlbuild -use-ocamlfind=85 app.native=94 This builds.=20 >=20 > I replaced Extlib.Base64 with Batteries.Base64, which doesn=92t = conflict with Nocrypto and builds, so I=92m good. >=20 > The =93Core=94 conflict in asn1-combinators is more annoying as I have = a file used in both Async and Lwt and I wanted to use = Core.Std.Io_channel that works in both, but I think I have a work around = for this too. >=20 > Thanks, >=20 > Gregory >=20 > On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy = wrote: >=20 >> Hi Gregory, [ccing mirageos-devel] >>=20 >> The root cause of this issue is a clash with top-level module names. = Somewhere in your library dependency chain, something has also defined a = module called "Base64" that is different from the one that Nocrypto = thinks its using. >>=20 >> One way to fix this is by not exposing a library's internal modules = to the outside world by packing them inside a single top-level module. = Cohttp is one example of a library that does this. (see = https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-ty= pe-checking.html#modules-and-separate-compilation for more information = on packing). >>=20 >> It's difficult to workaround this without just fixing the libraries = themselves -- although you will never get a segfault (as would happen in = C if you mix up object files), the compiler will just reject = inconsistent library checksums all the time. >>=20 >> I'm not sure which makefile you're referring to (vs oasis below), but = perhaps David and Hannes can comment on whether they can pack the = various crypto libraries for easier use. >>=20 >> Also, we could just pull Base64 into a separate OPAM package since = it's very commonly cut-and-pasted. I've taken a quick shot at this on = https://github.com/mirage/ocaml-base64. This is a different = implementation (but possibly the same spec) as nocrypto's, so needs some = review to see if they're compatible or not (padding is possibly slightly = different). >>=20 >> -anil >>=20 >> On 2 Aug 2014, at 13:08, Gregory Tsipenyuk wrote: >>=20 >>> Hi Anil, >>>=20 >>> I got another =93inconsistent assumptions=94 issue. It looks like it = is similar to the one I opened a few days ago against asn1-combinators. = Nocrypto does have its own Base64 module. What puzzles me though is that = it fails if I build with oasis generated stuff and if I build with the = regular Makefile then it builds. Can you think of any flags that I can = tweak to fix it? >>>=20 >>> Thanks, >>> Gregory=20 >>>=20 >>> File "_none_", line 1: >>> Error: Files utils.cmx >>> and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa >>> make inconsistent assumptions over interface Base64 >>> Command exited with code 2 >>=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 The = manual makefile probably doesn't pull in as many dependencies.  The = real answer here is just to fix the upstream I think, as it'll block any = non-trivial uses of the OCaml TLS = stack.

-anil

On 3 Aug 2014, = at 14:06, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Anil,

Thanks, I understand the = clash issue.

By regular Makefile I just mean a = manually created Makefile that has "ocamlbuild -use-ocamlfind=85 app.native=94 This = builds. 

I replaced Extlib.Base64 with = Batteries.Base64, which doesn=92t conflict with Nocrypto and builds, so = I=92m good.

The =93Core=94 conflict in = asn1-combinators is more annoying as I have a file used in both Async = and Lwt and I wanted to use Core.Std.Io_channel that works in both, but = I think I have a work around for this = too.

Thanks,

Gregory

On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy = <anil@recoil.org> = wrote:

Hi = Gregory, [ccing mirageos-devel]

The root cause of = this issue is a clash with top-level module names.  Somewhere in = your library dependency chain, something has also defined a module = called "Base64" that is different from the one that Nocrypto thinks its = using.

One way to fix this is by not exposing a = library's internal modules to the outside world by packing them inside a = single top-level module.  Cohttp is one example of a library that = does this.  (see https://realwor= ldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.htm= l#modules-and-separate-compilation for more information on = packing).

It's difficult to workaround this = without just fixing the libraries themselves -- although you will never = get a segfault (as would happen in C if you mix up object files), the = compiler will just reject inconsistent library checksums all the = time.

I'm not sure which makefile you're = referring to (vs oasis below), but perhaps David and Hannes can comment = on whether they can pack the various crypto libraries for easier = use.

Also, we could just pull Base64 into a = separate OPAM package since it's very commonly cut-and-pasted. =  I've taken a quick shot at this on https://github.com/mirage/= ocaml-base64.  This is a different implementation (but possibly = the same spec) as nocrypto's, so needs some review to see if they're = compatible or not (padding is possibly slightly = different).

-anil

<= div>On 2 Aug 2014, at 13:08, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Hi Anil,

I got another = =93inconsistent assumptions=94 issue. It looks like it is similar to the = one I opened a few days ago against asn1-combinators. Nocrypto does have = its own Base64 module. What puzzles me though is that  it fails if = I build with oasis generated stuff and if I build with the regular = Makefile then it builds. Can you think of any flags that I can tweak to = fix = it?

Thanks,
Gregory 
File "_none_", line 1:
Error: Files utils.cmx
   =     and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa
   =     make inconsistent assumptions over interface = Base64
Command exited with code = 2

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

= --Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8-- --===============1683333006645514692== 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 --===============1683333006645514692==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 14:04:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 14:04: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 1XDwOh-0007Yy-2e; Sun, 03 Aug 2014 14:04:27 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDwOg-0007Yt-11 for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 14:04:26 +0000 Received: from [85.158.137.68:42689] by server-13.bemta-3.messagelabs.com id 93/0D-09942-9614ED35; Sun, 03 Aug 2014 14:04:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-31.messagelabs.com!1407074663!7842411!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16816 invoked from network); 3 Aug 2014 14:04:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-31.messagelabs.com with SMTP; 3 Aug 2014 14:04:23 -0000 Received: (qmail 7901 invoked by uid 634); 3 Aug 2014 14:04: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 m.cb1.com (HELO [192.168.1.94]) (217.155.139.150) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 15:04:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <87E52E42-16E7-4D31-A7F0-4DC5B003B71F@cam.ac.uk> Date: Sun, 3 Aug 2014 15:04:20 +0100 Message-Id: References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> <87E52E42-16E7-4D31-A7F0-4DC5B003B71F@cam.ac.uk> To: Gregory Tsipenyuk 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] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1683333006645514692==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1683333006645514692== Content-Type: multipart/alternative; boundary="Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8" --Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 The manual makefile probably doesn't pull in as many dependencies. The = real answer here is just to fix the upstream I think, as it'll block any = non-trivial uses of the OCaml TLS stack. -anil On 3 Aug 2014, at 14:06, Gregory Tsipenyuk wrote: > Anil, >=20 > Thanks, I understand the clash issue. >=20 > By regular Makefile I just mean a manually created Makefile that has = "ocamlbuild -use-ocamlfind=85 app.native=94 This builds.=20 >=20 > I replaced Extlib.Base64 with Batteries.Base64, which doesn=92t = conflict with Nocrypto and builds, so I=92m good. >=20 > The =93Core=94 conflict in asn1-combinators is more annoying as I have = a file used in both Async and Lwt and I wanted to use = Core.Std.Io_channel that works in both, but I think I have a work around = for this too. >=20 > Thanks, >=20 > Gregory >=20 > On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy = wrote: >=20 >> Hi Gregory, [ccing mirageos-devel] >>=20 >> The root cause of this issue is a clash with top-level module names. = Somewhere in your library dependency chain, something has also defined a = module called "Base64" that is different from the one that Nocrypto = thinks its using. >>=20 >> One way to fix this is by not exposing a library's internal modules = to the outside world by packing them inside a single top-level module. = Cohttp is one example of a library that does this. (see = https://realworldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-ty= pe-checking.html#modules-and-separate-compilation for more information = on packing). >>=20 >> It's difficult to workaround this without just fixing the libraries = themselves -- although you will never get a segfault (as would happen in = C if you mix up object files), the compiler will just reject = inconsistent library checksums all the time. >>=20 >> I'm not sure which makefile you're referring to (vs oasis below), but = perhaps David and Hannes can comment on whether they can pack the = various crypto libraries for easier use. >>=20 >> Also, we could just pull Base64 into a separate OPAM package since = it's very commonly cut-and-pasted. I've taken a quick shot at this on = https://github.com/mirage/ocaml-base64. This is a different = implementation (but possibly the same spec) as nocrypto's, so needs some = review to see if they're compatible or not (padding is possibly slightly = different). >>=20 >> -anil >>=20 >> On 2 Aug 2014, at 13:08, Gregory Tsipenyuk wrote: >>=20 >>> Hi Anil, >>>=20 >>> I got another =93inconsistent assumptions=94 issue. It looks like it = is similar to the one I opened a few days ago against asn1-combinators. = Nocrypto does have its own Base64 module. What puzzles me though is that = it fails if I build with oasis generated stuff and if I build with the = regular Makefile then it builds. Can you think of any flags that I can = tweak to fix it? >>>=20 >>> Thanks, >>> Gregory=20 >>>=20 >>> File "_none_", line 1: >>> Error: Files utils.cmx >>> and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa >>> make inconsistent assumptions over interface Base64 >>> Command exited with code 2 >>=20 >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 The = manual makefile probably doesn't pull in as many dependencies.  The = real answer here is just to fix the upstream I think, as it'll block any = non-trivial uses of the OCaml TLS = stack.

-anil

On 3 Aug 2014, = at 14:06, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Anil,

Thanks, I understand the = clash issue.

By regular Makefile I just mean a = manually created Makefile that has "ocamlbuild -use-ocamlfind=85 app.native=94 This = builds. 

I replaced Extlib.Base64 with = Batteries.Base64, which doesn=92t conflict with Nocrypto and builds, so = I=92m good.

The =93Core=94 conflict in = asn1-combinators is more annoying as I have a file used in both Async = and Lwt and I wanted to use Core.Std.Io_channel that works in both, but = I think I have a work around for this = too.

Thanks,

Gregory

On Aug 3, 2014, at 12:18 PM, Anil Madhavapeddy = <anil@recoil.org> = wrote:

Hi = Gregory, [ccing mirageos-devel]

The root cause of = this issue is a clash with top-level module names.  Somewhere in = your library dependency chain, something has also defined a module = called "Base64" that is different from the one that Nocrypto thinks its = using.

One way to fix this is by not exposing a = library's internal modules to the outside world by packing them inside a = single top-level module.  Cohttp is one example of a library that = does this.  (see https://realwor= ldocaml.org/v1/en/html/the-compiler-frontend-parsing-and-type-checking.htm= l#modules-and-separate-compilation for more information on = packing).

It's difficult to workaround this = without just fixing the libraries themselves -- although you will never = get a segfault (as would happen in C if you mix up object files), the = compiler will just reject inconsistent library checksums all the = time.

I'm not sure which makefile you're = referring to (vs oasis below), but perhaps David and Hannes can comment = on whether they can pack the various crypto libraries for easier = use.

Also, we could just pull Base64 into a = separate OPAM package since it's very commonly cut-and-pasted. =  I've taken a quick shot at this on https://github.com/mirage/= ocaml-base64.  This is a different implementation (but possibly = the same spec) as nocrypto's, so needs some review to see if they're = compatible or not (padding is possibly slightly = different).

-anil

<= div>On 2 Aug 2014, at 13:08, Gregory Tsipenyuk <gt303@cam.ac.uk> wrote:

Hi Anil,

I got another = =93inconsistent assumptions=94 issue. It looks like it is similar to the = one I opened a few days ago against asn1-combinators. Nocrypto does have = its own Base64 module. What puzzles me though is that  it fails if = I build with oasis generated stuff and if I build with the regular = Makefile then it builds. Can you think of any flags that I can tweak to = fix = it?

Thanks,
Gregory 
File "_none_", line 1:
Error: Files utils.cmx
   =     and = /Users/gregt/.opam/4.01.0+clang-fix/lib/nocrypto/nocrypto.cmxa
   =     make inconsistent assumptions over interface = Base64
Command exited with code = 2

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

= --Apple-Mail=_55B867AD-6CFF-4EDC-9448-7A8C6A7648B8-- --===============1683333006645514692== 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 --===============1683333006645514692==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 14:06:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 14:06: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 1XDwQI-0007bu-SL; Sun, 03 Aug 2014 14:06:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDwQH-0007bo-G8 for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 14:06:05 +0000 Received: from [85.158.137.68:45508] by server-3.bemta-3.messagelabs.com id AE/72-22751-CC14ED35; Sun, 03 Aug 2014 14:06:04 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1407074763!11601040!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 24616 invoked from network); 3 Aug 2014 14:06:03 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 3 Aug 2014 14:06:03 -0000 Received: (qmail 5794 invoked by uid 634); 3 Aug 2014 14:06: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 m.cb1.com (HELO [192.168.1.94]) (217.155.139.150) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 15:05:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <53DE201D.802@mehnert.org> Date: Sun, 3 Aug 2014 15:05:54 +0100 Message-Id: <29DBD2F2-228E-4810-A14E-4BBC0F2DD482@recoil.org> References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> <53DE201D.802@mehnert.org> To: Hannes Mehnert 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] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 12:42, Hannes Mehnert wrote: > While I didn't look into the algorithm, the interface is slightly > different - string vs Cstruct.t -- and I wonder whether we should have > an implementation providing both a string and Cstruct.t interface > (because conversion includes copying)? Yes, I think that'd be fine. The easiest way forward is for me to tag a base64.1.0.0 that'll be compatible with the existing `string` users (Cohttp, Dns), and for you to submit a Cstruct pull request that will let the TLS libraries shift over. Solving the packing issue would also unblock Conduit using TLS, as that depends on Async and Lwt, which triggers the inconsistent build issue (Gregory was blazing a trail in discovering the bug first :) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 14:06:06 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 14:06: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 1XDwQI-0007bu-SL; Sun, 03 Aug 2014 14:06:06 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDwQH-0007bo-G8 for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 14:06:05 +0000 Received: from [85.158.137.68:45508] by server-3.bemta-3.messagelabs.com id AE/72-22751-CC14ED35; Sun, 03 Aug 2014 14:06:04 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1407074763!11601040!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 24616 invoked from network); 3 Aug 2014 14:06:03 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 3 Aug 2014 14:06:03 -0000 Received: (qmail 5794 invoked by uid 634); 3 Aug 2014 14:06: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 m.cb1.com (HELO [192.168.1.94]) (217.155.139.150) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 15:05:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <53DE201D.802@mehnert.org> Date: Sun, 3 Aug 2014 15:05:54 +0100 Message-Id: <29DBD2F2-228E-4810-A14E-4BBC0F2DD482@recoil.org> References: <3D2E3711-3E3A-42B8-B986-680B3B4BE510@cam.ac.uk> <42034DAC-DE20-4EE4-A112-D8F9E1E41161@recoil.org> <53DE201D.802@mehnert.org> To: Hannes Mehnert 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] inconsistent assumptions over interface error X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 12:42, Hannes Mehnert wrote: > While I didn't look into the algorithm, the interface is slightly > different - string vs Cstruct.t -- and I wonder whether we should have > an implementation providing both a string and Cstruct.t interface > (because conversion includes copying)? Yes, I think that'd be fine. The easiest way forward is for me to tag a base64.1.0.0 that'll be compatible with the existing `string` users (Cohttp, Dns), and for you to submit a Cstruct pull request that will let the TLS libraries shift over. Solving the packing issue would also unblock Conduit using TLS, as that depends on Async and Lwt, which triggers the inconsistent build issue (Gregory was blazing a trail in discovering the bug first :) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 15:34:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 15:34: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 1XDxnz-0008Oi-L3; Sun, 03 Aug 2014 15:34:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDxnx-0008Od-UA for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 15:34:38 +0000 Received: from [85.158.139.211:22335] by server-8.bemta-5.messagelabs.com id 10/27-22440-D865ED35; Sun, 03 Aug 2014 15:34:37 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-2.tower-206.messagelabs.com!1407080076!11582073!1 X-Originating-IP: [80.12.242.132] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30258 invoked from network); 3 Aug 2014 15:34:36 -0000 Received: from smtp10.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.132) by server-2.tower-206.messagelabs.com with SMTP; 3 Aug 2014 15:34:36 -0000 Received: from wwinf1h10 ([10.232.41.53]) by mwinf5d19 with ME id aFaa1o00F18pLn603FaaWQ; Sun, 03 Aug 2014 17:34:34 +0200 X-ME-Helo: wwinf1h10 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Sun, 03 Aug 2014 17:34:34 +0200 X-ME-IP: 90.29.191.133 Date: Sun, 3 Aug 2014 17:34:34 +0200 (CEST) From: Gilles DALMAS To: mirageos-devel@lists.xenproject.org Message-ID: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7931257875657569211==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7931257875657569211== Content-Type: multipart/alternative; boundary="----=_Part_5995_1169323602.1407080074697" ------=_Part_5995_1169323602.1407080074697 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hi, I recently compiled mirage for cubietruck. Everything works fine, but the system is extremely slow. Initially, I had put others options in the kernel because I wanted the syst= em can manage RAID systems. =C2=A0Then given the very slow speed of mirage, I tried to only necessary o= ptions to operate xen, but the system was still very slow. I then added a swap partition, which is not mentioned in the wiki. There, t= he system became a bit faster but it is still very inssuffisant. I thought that to install directly on the nand could improve things, but mi= rage does not seem to recognize the nand. There are currently no nand in th= e mnt directory ... is this a bug or an oversight on my leaving? ------=_Part_5995_1169323602.1407080074697 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

hi,

I recently compiled mirage for cubietruck.

Everything works fine, but the system is extremely slow.

Initially, I had put others options in the kernel because I wanted the s= ystem can manage RAID systems.

=C2=A0Then given the very slow speed of mirage, I tried to only necessar= y options to operate xen, but the system was still very slow.

I then added a swap partition, which is not mentioned in the wiki. There= , the system became a bit faster but it is still very inssuffisant.

I thought that to install directly on the nand could improve things, but= mirage does not seem to recognize the nand. There are currently no nand in= the mnt directory ... is this a bug or an oversight on my leaving?

------=_Part_5995_1169323602.1407080074697-- --===============7931257875657569211== 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 --===============7931257875657569211==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 15:34:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 15:34: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 1XDxnz-0008Oi-L3; Sun, 03 Aug 2014 15:34:39 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDxnx-0008Od-UA for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 15:34:38 +0000 Received: from [85.158.139.211:22335] by server-8.bemta-5.messagelabs.com id 10/27-22440-D865ED35; Sun, 03 Aug 2014 15:34:37 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-2.tower-206.messagelabs.com!1407080076!11582073!1 X-Originating-IP: [80.12.242.132] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30258 invoked from network); 3 Aug 2014 15:34:36 -0000 Received: from smtp10.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.132) by server-2.tower-206.messagelabs.com with SMTP; 3 Aug 2014 15:34:36 -0000 Received: from wwinf1h10 ([10.232.41.53]) by mwinf5d19 with ME id aFaa1o00F18pLn603FaaWQ; Sun, 03 Aug 2014 17:34:34 +0200 X-ME-Helo: wwinf1h10 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Sun, 03 Aug 2014 17:34:34 +0200 X-ME-IP: 90.29.191.133 Date: Sun, 3 Aug 2014 17:34:34 +0200 (CEST) From: Gilles DALMAS To: mirageos-devel@lists.xenproject.org Message-ID: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7931257875657569211==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7931257875657569211== Content-Type: multipart/alternative; boundary="----=_Part_5995_1169323602.1407080074697" ------=_Part_5995_1169323602.1407080074697 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hi, I recently compiled mirage for cubietruck. Everything works fine, but the system is extremely slow. Initially, I had put others options in the kernel because I wanted the syst= em can manage RAID systems. =C2=A0Then given the very slow speed of mirage, I tried to only necessary o= ptions to operate xen, but the system was still very slow. I then added a swap partition, which is not mentioned in the wiki. There, t= he system became a bit faster but it is still very inssuffisant. I thought that to install directly on the nand could improve things, but mi= rage does not seem to recognize the nand. There are currently no nand in th= e mnt directory ... is this a bug or an oversight on my leaving? ------=_Part_5995_1169323602.1407080074697 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

hi,

I recently compiled mirage for cubietruck.

Everything works fine, but the system is extremely slow.

Initially, I had put others options in the kernel because I wanted the s= ystem can manage RAID systems.

=C2=A0Then given the very slow speed of mirage, I tried to only necessar= y options to operate xen, but the system was still very slow.

I then added a swap partition, which is not mentioned in the wiki. There= , the system became a bit faster but it is still very inssuffisant.

I thought that to install directly on the nand could improve things, but= mirage does not seem to recognize the nand. There are currently no nand in= the mnt directory ... is this a bug or an oversight on my leaving?

------=_Part_5995_1169323602.1407080074697-- --===============7931257875657569211== 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 --===============7931257875657569211==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 16:21:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 16:21:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDyX1-0000cO-42; Sun, 03 Aug 2014 16:21:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDyWz-0000cJ-GQ for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 16:21:09 +0000 Received: from [85.158.139.211:65362] by server-14.bemta-5.messagelabs.com id 6D/D3-12422-4716ED35; Sun, 03 Aug 2014 16:21:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1407082865!7455863!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16231 invoked from network); 3 Aug 2014 16:21:05 -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; 3 Aug 2014 16:21:05 -0000 Received: (qmail 12789 invoked by uid 634); 3 Aug 2014 16:21:05 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 17:21:01 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> Date: Sun, 3 Aug 2014 17:20:59 +0100 Message-Id: <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> To: Gilles DALMAS 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 os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0923947265435042557==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0923947265435042557== Content-Type: multipart/alternative; boundary="Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271" --Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > hi, >=20 > I recently compiled mirage for cubietruck. >=20 > Everything works fine, but the system is extremely slow. >=20 Hi Gilles, Glad to hear you've got it up and running. Could you shed some light = about the nature of the application that is slow? If it's networking, there's a known bug at the moment [1] due to a = limitation on Xen 4.4/ARM that prevents multiple mapping of pages. = Thomas Leonard has just applied a backport to the SDCard image builder = [2] that fixes this issue in Xen itself, so we could remove the = workaround now and hopefully get back to decent networking performance = (is this correct, Thomas? I haven't had a chance to rebuild my own = Cubie2 yet). [1] = http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00163.= html [2] https://github.com/mirage/xen-arm-builder/pull/13 > Initially, I had put others options in the kernel because I wanted the = system can manage RAID systems. >=20 Incidentally, if there are useful kernel options in the SDcard image = that don't conflict with others, then please do feel free to tweak the = kernel config and submit them as a pull request to the Xen ARM builder: = https://github.com/mirage/xen-arm-builder I'm just automating the rebuilding of the SDcard images, so this will = help keep a "known good Xen/ARM/Mirage" software configuration in one = place. > Then given the very slow speed of mirage, I tried to only necessary = options to operate xen, but the system was still very slow. >=20 > I then added a swap partition, which is not mentioned in the wiki. = There, the system became a bit faster but it is still very inssuffisant. >=20 I'm still a little unclear on what is slow -- is it your Linux dom0, or = a Mirage app, or both? > I thought that to install directly on the nand could improve things, = but mirage does not seem to recognize the nand. There are currently no = nand in the mnt directory ... is this a bug or an oversight on my = leaving? >=20 I'm not sure if NAND support has been upstreamed yet into Linux. It = shouldn't affect your system performance very much though. -anil= --Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 3 = Aug 2014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

hi,

I recently compiled mirage for = cubietruck.

Everything works fine, but the system is extremely = slow.

Hi Gilles,

Glad to hear = you've got it up and running. Could you shed some light about the nature = of the application that is slow?

If it's = networking, there's a known bug at the moment [1] due to a limitation on = Xen 4.4/ARM that prevents multiple mapping of pages.   Thomas = Leonard has just applied a backport to the SDCard image builder [2] that = fixes this issue in Xen itself, so we could remove the workaround now = and hopefully get back to decent networking performance (is this = correct, Thomas?  I haven't had a chance to rebuild my own Cubie2 = yet).

Initially, I had put others options in the kernel = because I wanted the system can manage RAID = systems.

Incidentally, if there are useful kernel = options in the SDcard image that don't conflict with others, then please = do feel free to tweak the kernel config and submit them as a pull = request to the Xen ARM builder: https://github.com/mira= ge/xen-arm-builder

I'm just automating the = rebuilding of the SDcard images, so this will help keep a "known good = Xen/ARM/Mirage" software configuration in one = place.

 Then given the very = slow speed of mirage, I tried to only necessary options to operate xen, = but the system was still very slow.

I then added a swap partition, = which is not mentioned in the wiki. There, the system became a bit = faster but it is still very = inssuffisant.


I'm still a little unclear = on what is slow -- is it your Linux dom0, or a Mirage app, or = both?

I thought that to = install directly on the nand could improve things, but mirage does not = seem to recognize the nand. There are currently no nand in the mnt = directory ... is this a bug or an oversight on my = leaving?

I'm not sure if NAND support has been = upstreamed yet into Linux.  It shouldn't affect your system = performance very much = though.

-anil
= --Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271-- --===============0923947265435042557== 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 --===============0923947265435042557==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 16:21:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 16:21:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDyX1-0000cO-42; Sun, 03 Aug 2014 16:21:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDyWz-0000cJ-GQ for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 16:21:09 +0000 Received: from [85.158.139.211:65362] by server-14.bemta-5.messagelabs.com id 6D/D3-12422-4716ED35; Sun, 03 Aug 2014 16:21:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1407082865!7455863!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16231 invoked from network); 3 Aug 2014 16:21:05 -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; 3 Aug 2014 16:21:05 -0000 Received: (qmail 12789 invoked by uid 634); 3 Aug 2014 16:21:05 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 03 Aug 2014 17:21:01 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> Date: Sun, 3 Aug 2014 17:20:59 +0100 Message-Id: <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> To: Gilles DALMAS 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 os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0923947265435042557==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0923947265435042557== Content-Type: multipart/alternative; boundary="Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271" --Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > hi, >=20 > I recently compiled mirage for cubietruck. >=20 > Everything works fine, but the system is extremely slow. >=20 Hi Gilles, Glad to hear you've got it up and running. Could you shed some light = about the nature of the application that is slow? If it's networking, there's a known bug at the moment [1] due to a = limitation on Xen 4.4/ARM that prevents multiple mapping of pages. = Thomas Leonard has just applied a backport to the SDCard image builder = [2] that fixes this issue in Xen itself, so we could remove the = workaround now and hopefully get back to decent networking performance = (is this correct, Thomas? I haven't had a chance to rebuild my own = Cubie2 yet). [1] = http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00163.= html [2] https://github.com/mirage/xen-arm-builder/pull/13 > Initially, I had put others options in the kernel because I wanted the = system can manage RAID systems. >=20 Incidentally, if there are useful kernel options in the SDcard image = that don't conflict with others, then please do feel free to tweak the = kernel config and submit them as a pull request to the Xen ARM builder: = https://github.com/mirage/xen-arm-builder I'm just automating the rebuilding of the SDcard images, so this will = help keep a "known good Xen/ARM/Mirage" software configuration in one = place. > Then given the very slow speed of mirage, I tried to only necessary = options to operate xen, but the system was still very slow. >=20 > I then added a swap partition, which is not mentioned in the wiki. = There, the system became a bit faster but it is still very inssuffisant. >=20 I'm still a little unclear on what is slow -- is it your Linux dom0, or = a Mirage app, or both? > I thought that to install directly on the nand could improve things, = but mirage does not seem to recognize the nand. There are currently no = nand in the mnt directory ... is this a bug or an oversight on my = leaving? >=20 I'm not sure if NAND support has been upstreamed yet into Linux. It = shouldn't affect your system performance very much though. -anil= --Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 3 = Aug 2014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

hi,

I recently compiled mirage for = cubietruck.

Everything works fine, but the system is extremely = slow.

Hi Gilles,

Glad to hear = you've got it up and running. Could you shed some light about the nature = of the application that is slow?

If it's = networking, there's a known bug at the moment [1] due to a limitation on = Xen 4.4/ARM that prevents multiple mapping of pages.   Thomas = Leonard has just applied a backport to the SDCard image builder [2] that = fixes this issue in Xen itself, so we could remove the workaround now = and hopefully get back to decent networking performance (is this = correct, Thomas?  I haven't had a chance to rebuild my own Cubie2 = yet).

Initially, I had put others options in the kernel = because I wanted the system can manage RAID = systems.

Incidentally, if there are useful kernel = options in the SDcard image that don't conflict with others, then please = do feel free to tweak the kernel config and submit them as a pull = request to the Xen ARM builder: https://github.com/mira= ge/xen-arm-builder

I'm just automating the = rebuilding of the SDcard images, so this will help keep a "known good = Xen/ARM/Mirage" software configuration in one = place.

 Then given the very = slow speed of mirage, I tried to only necessary options to operate xen, = but the system was still very slow.

I then added a swap partition, = which is not mentioned in the wiki. There, the system became a bit = faster but it is still very = inssuffisant.


I'm still a little unclear = on what is slow -- is it your Linux dom0, or a Mirage app, or = both?

I thought that to = install directly on the nand could improve things, but mirage does not = seem to recognize the nand. There are currently no nand in the mnt = directory ... is this a bug or an oversight on my = leaving?

I'm not sure if NAND support has been = upstreamed yet into Linux.  It shouldn't affect your system = performance very much = though.

-anil
= --Apple-Mail=_BAD1C760-12FE-485F-A348-BA9EEBE9C271-- --===============0923947265435042557== 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 --===============0923947265435042557==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 03 16:24:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 16:24: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 1XDyaQ-0000fP-H7; Sun, 03 Aug 2014 16:24:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDyaQ-0000fK-3A for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 16:24:42 +0000 Received: from [85.158.139.211:32419] by server-11.bemta-5.messagelabs.com id 80/50-31757-9426ED35; Sun, 03 Aug 2014 16:24:41 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1407083079!11585729!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 29574 invoked from network); 3 Aug 2014 16:24:40 -0000 Received: from mail-oi0-f52.google.com (HELO mail-oi0-f52.google.com) (209.85.218.52) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Aug 2014 16:24:40 -0000 Received: by mail-oi0-f52.google.com with SMTP id h136so3923239oig.39 for ; Sun, 03 Aug 2014 09:24:39 -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=GEFVRudwulwQ9gXdIzwIIxvPpJq6Ov/A92H1V5ec26c=; b=QJNh3azCv0u1ZYCnKMhrr/hptB6TW6yeKa435dvFE5jd+i3fkEXoX72ECqXASsBcgH dR5WH5mi+9IpawyUdDhs81ZeeMUfx2Bvc22p3eWZhQuoKhor80ONz4ekCDSsCD1V63bI CVIRpojXDKR+Knw0L7rZLefxM1db5/0xBvHU4GGuRLQPys8dEfnHQSK5IvRebDUBVqiX FtTZtOvWy1C2Cki/WRrWBNew0fTAhwOzJDRmw/aPnyFf0nnSJcLAc9K2ruKNLJCHlqbH 8vJOhLSir/jAzgp7wlFbleLha+VHrFgKAb9/8Ev5/AMG3o9I1swspiF88PpJp7wYNoXW DJCg== MIME-Version: 1.0 X-Received: by 10.60.133.203 with SMTP id pe11mr25583125oeb.24.1407083078946; Sun, 03 Aug 2014 09:24:38 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sun, 3 Aug 2014 09:24:38 -0700 (PDT) In-Reply-To: <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> Date: Sun, 3 Aug 2014 17:24:38 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 August 2014 17:20, Anil Madhavapeddy wrote: > On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > > hi, > > I recently compiled mirage for cubietruck. > > Everything works fine, but the system is extremely slow. > > Hi Gilles, > > Glad to hear you've got it up and running. Could you shed some light about > the nature of the application that is slow? > > If it's networking, there's a known bug at the moment [1] due to a > limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Thomas > Leonard has just applied a backport to the SDCard image builder [2] that > fixes this issue in Xen itself, so we could remove the workaround now and > hopefully get back to decent networking performance (is this correct, > Thomas? I haven't had a chance to rebuild my own Cubie2 yet). Yes, I'll rebuild the binary images at some point but for now you can build from Git. With that, you can revert back to the older mirage-net-xen v1.1.1 to avoid the wait after sending each packet. > [1] > http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00163.html > [2] https://github.com/mirage/xen-arm-builder/pull/13 > > Initially, I had put others options in the kernel because I wanted the > system can manage RAID systems. > > Incidentally, if there are useful kernel options in the SDcard image that > don't conflict with others, then please do feel free to tweak the kernel > config and submit them as a pull request to the Xen ARM builder: > https://github.com/mirage/xen-arm-builder > > I'm just automating the rebuilding of the SDcard images, so this will help > keep a "known good Xen/ARM/Mirage" software configuration in one place. > > Then given the very slow speed of mirage, I tried to only necessary options > to operate xen, but the system was still very slow. > > I then added a swap partition, which is not mentioned in the wiki. There, > the system became a bit faster but it is still very inssuffisant. > > > I'm still a little unclear on what is slow -- is it your Linux dom0, or a > Mirage app, or both? > > I thought that to install directly on the nand could improve things, but > mirage does not seem to recognize the nand. There are currently no nand in > the mnt directory ... is this a bug or an oversight on my leaving? > > I'm not sure if NAND support has been upstreamed yet into Linux. It > shouldn't affect your system performance very much though. I haven't tried it, but there is a CONFIG_SUNXI_NAND option in the sunxi-3.4 branch of the sunxi Linux Git repository (but not in the branch we use or upstream Linux). -- 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 Sun Aug 03 16:24:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 03 Aug 2014 16:24: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 1XDyaQ-0000fP-H7; Sun, 03 Aug 2014 16:24:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XDyaQ-0000fK-3A for mirageos-devel@lists.xenproject.org; Sun, 03 Aug 2014 16:24:42 +0000 Received: from [85.158.139.211:32419] by server-11.bemta-5.messagelabs.com id 80/50-31757-9426ED35; Sun, 03 Aug 2014 16:24:41 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-2.tower-206.messagelabs.com!1407083079!11585729!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 29574 invoked from network); 3 Aug 2014 16:24:40 -0000 Received: from mail-oi0-f52.google.com (HELO mail-oi0-f52.google.com) (209.85.218.52) by server-2.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 3 Aug 2014 16:24:40 -0000 Received: by mail-oi0-f52.google.com with SMTP id h136so3923239oig.39 for ; Sun, 03 Aug 2014 09:24:39 -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=GEFVRudwulwQ9gXdIzwIIxvPpJq6Ov/A92H1V5ec26c=; b=QJNh3azCv0u1ZYCnKMhrr/hptB6TW6yeKa435dvFE5jd+i3fkEXoX72ECqXASsBcgH dR5WH5mi+9IpawyUdDhs81ZeeMUfx2Bvc22p3eWZhQuoKhor80ONz4ekCDSsCD1V63bI CVIRpojXDKR+Knw0L7rZLefxM1db5/0xBvHU4GGuRLQPys8dEfnHQSK5IvRebDUBVqiX FtTZtOvWy1C2Cki/WRrWBNew0fTAhwOzJDRmw/aPnyFf0nnSJcLAc9K2ruKNLJCHlqbH 8vJOhLSir/jAzgp7wlFbleLha+VHrFgKAb9/8Ev5/AMG3o9I1swspiF88PpJp7wYNoXW DJCg== MIME-Version: 1.0 X-Received: by 10.60.133.203 with SMTP id pe11mr25583125oeb.24.1407083078946; Sun, 03 Aug 2014 09:24:38 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Sun, 3 Aug 2014 09:24:38 -0700 (PDT) In-Reply-To: <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> Date: Sun, 3 Aug 2014 17:24:38 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 August 2014 17:20, Anil Madhavapeddy wrote: > On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > > hi, > > I recently compiled mirage for cubietruck. > > Everything works fine, but the system is extremely slow. > > Hi Gilles, > > Glad to hear you've got it up and running. Could you shed some light about > the nature of the application that is slow? > > If it's networking, there's a known bug at the moment [1] due to a > limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Thomas > Leonard has just applied a backport to the SDCard image builder [2] that > fixes this issue in Xen itself, so we could remove the workaround now and > hopefully get back to decent networking performance (is this correct, > Thomas? I haven't had a chance to rebuild my own Cubie2 yet). Yes, I'll rebuild the binary images at some point but for now you can build from Git. With that, you can revert back to the older mirage-net-xen v1.1.1 to avoid the wait after sending each packet. > [1] > http://lists.xenproject.org/archives/html/mirageos-devel/2014-07/msg00163.html > [2] https://github.com/mirage/xen-arm-builder/pull/13 > > Initially, I had put others options in the kernel because I wanted the > system can manage RAID systems. > > Incidentally, if there are useful kernel options in the SDcard image that > don't conflict with others, then please do feel free to tweak the kernel > config and submit them as a pull request to the Xen ARM builder: > https://github.com/mirage/xen-arm-builder > > I'm just automating the rebuilding of the SDcard images, so this will help > keep a "known good Xen/ARM/Mirage" software configuration in one place. > > Then given the very slow speed of mirage, I tried to only necessary options > to operate xen, but the system was still very slow. > > I then added a swap partition, which is not mentioned in the wiki. There, > the system became a bit faster but it is still very inssuffisant. > > > I'm still a little unclear on what is slow -- is it your Linux dom0, or a > Mirage app, or both? > > I thought that to install directly on the nand could improve things, but > mirage does not seem to recognize the nand. There are currently no nand in > the mnt directory ... is this a bug or an oversight on my leaving? > > I'm not sure if NAND support has been upstreamed yet into Linux. It > shouldn't affect your system performance very much though. I haven't tried it, but there is a CONFIG_SUNXI_NAND option in the sunxi-3.4 branch of the sunxi Linux Git repository (but not in the branch we use or upstream Linux). -- 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 Mon Aug 04 11:28:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 11:28: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 1XEGR3-0007Yo-FM; Mon, 04 Aug 2014 11:28:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEGR2-0007YY-8x for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 11:28:12 +0000 Received: from [85.158.139.211:52703] by server-4.bemta-5.messagelabs.com id D1/A4-10551-B4E6FD35; Mon, 04 Aug 2014 11:28:11 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1407151689!11756759!1 X-Originating-IP: [209.85.219.49] 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 26270 invoked from network); 4 Aug 2014 11:28:10 -0000 Received: from mail-oa0-f49.google.com (HELO mail-oa0-f49.google.com) (209.85.219.49) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Aug 2014 11:28:10 -0000 Received: by mail-oa0-f49.google.com with SMTP id eb12so4822125oac.22 for ; Mon, 04 Aug 2014 04:28:09 -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=wS2GnPQaVpcLQ83XgicsZKVYZIAC/dML2PTDeWkQMDU=; b=GR3wgN99LpLQHSYlWPuMNQjVMei8YPa/0a93u3pC37hjmfGqpYs8BB6CP/lNTlHKMa hPomBOOXd3m1UOvnLAEnOA8IBOI4FJtlifLsfJM18w88RMI5vRaRU1LUF8K7naTl6qyJ TqGUtPRuDY9V5mC99y2RXKPhkaSXYefWKRVQoqbzCYWLD3yk/cMBc5RcZTzFn8e3cwgI R8nZfBSY7q89YN952FHVoKKgKeCVcbdcbSHphn8cnwzHILj1ITe5x2mWtz+RW5qDRpR7 CqKFzsTIVABZG/5ZKSSxxbYOVclk9w0L3chxCC17FD1QRWZkWplnClxNSDCtknpg5YEV NSvw== MIME-Version: 1.0 X-Received: by 10.182.205.231 with SMTP id lj7mr30784996obc.37.1407151689246; Mon, 04 Aug 2014 04:28:09 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 4 Aug 2014 04:28:09 -0700 (PDT) In-Reply-To: References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> Date: Mon, 4 Aug 2014 12:28:09 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 August 2014 17:24, Thomas Leonard wrote: > On 3 August 2014 17:20, Anil Madhavapeddy wrote: >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: >> >> hi, >> >> I recently compiled mirage for cubietruck. >> >> Everything works fine, but the system is extremely slow. >> >> Hi Gilles, >> >> Glad to hear you've got it up and running. Could you shed some light about >> the nature of the application that is slow? >> >> If it's networking, there's a known bug at the moment [1] due to a >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Thomas >> Leonard has just applied a backport to the SDCard image builder [2] that >> fixes this issue in Xen itself, so we could remove the workaround now and >> hopefully get back to decent networking performance (is this correct, >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > Yes, I'll rebuild the binary images at some point but for now you can > build from Git. With that, you can revert back to the older > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. Here are the new images: http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 Installation instructions are here: https://github.com/mirage/xen-arm-builder Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1.1 -- 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 Mon Aug 04 11:28:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 11:28: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 1XEGR3-0007Yo-FM; Mon, 04 Aug 2014 11:28:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEGR2-0007YY-8x for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 11:28:12 +0000 Received: from [85.158.139.211:52703] by server-4.bemta-5.messagelabs.com id D1/A4-10551-B4E6FD35; Mon, 04 Aug 2014 11:28:11 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1407151689!11756759!1 X-Originating-IP: [209.85.219.49] 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 26270 invoked from network); 4 Aug 2014 11:28:10 -0000 Received: from mail-oa0-f49.google.com (HELO mail-oa0-f49.google.com) (209.85.219.49) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 4 Aug 2014 11:28:10 -0000 Received: by mail-oa0-f49.google.com with SMTP id eb12so4822125oac.22 for ; Mon, 04 Aug 2014 04:28:09 -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=wS2GnPQaVpcLQ83XgicsZKVYZIAC/dML2PTDeWkQMDU=; b=GR3wgN99LpLQHSYlWPuMNQjVMei8YPa/0a93u3pC37hjmfGqpYs8BB6CP/lNTlHKMa hPomBOOXd3m1UOvnLAEnOA8IBOI4FJtlifLsfJM18w88RMI5vRaRU1LUF8K7naTl6qyJ TqGUtPRuDY9V5mC99y2RXKPhkaSXYefWKRVQoqbzCYWLD3yk/cMBc5RcZTzFn8e3cwgI R8nZfBSY7q89YN952FHVoKKgKeCVcbdcbSHphn8cnwzHILj1ITe5x2mWtz+RW5qDRpR7 CqKFzsTIVABZG/5ZKSSxxbYOVclk9w0L3chxCC17FD1QRWZkWplnClxNSDCtknpg5YEV NSvw== MIME-Version: 1.0 X-Received: by 10.182.205.231 with SMTP id lj7mr30784996obc.37.1407151689246; Mon, 04 Aug 2014 04:28:09 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Mon, 4 Aug 2014 04:28:09 -0700 (PDT) In-Reply-To: References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> Date: Mon, 4 Aug 2014 12:28:09 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 August 2014 17:24, Thomas Leonard wrote: > On 3 August 2014 17:20, Anil Madhavapeddy wrote: >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: >> >> hi, >> >> I recently compiled mirage for cubietruck. >> >> Everything works fine, but the system is extremely slow. >> >> Hi Gilles, >> >> Glad to hear you've got it up and running. Could you shed some light about >> the nature of the application that is slow? >> >> If it's networking, there's a known bug at the moment [1] due to a >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Thomas >> Leonard has just applied a backport to the SDCard image builder [2] that >> fixes this issue in Xen itself, so we could remove the workaround now and >> hopefully get back to decent networking performance (is this correct, >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > Yes, I'll rebuild the binary images at some point but for now you can > build from Git. With that, you can revert back to the older > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. Here are the new images: http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 Installation instructions are here: https://github.com/mirage/xen-arm-builder Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1.1 -- 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 Mon Aug 04 12:29:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 12:29: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 1XEHOa-0002sz-V7; Mon, 04 Aug 2014 12:29:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEHOZ-0002se-3j for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 12:29:43 +0000 Received: from [85.158.143.35:62682] by server-1.bemta-4.messagelabs.com id 72/FC-05872-6BC7FD35; Mon, 04 Aug 2014 12:29:42 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-16.tower-21.messagelabs.com!1407155381!9885329!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29090 invoked from network); 4 Aug 2014 12:29:41 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-16.tower-21.messagelabs.com with SMTP; 4 Aug 2014 12:29:41 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d07 with ME id acVg1o00a11Dd4A03cVgBu; Mon, 04 Aug 2014 14:29:40 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 14:29:40 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 14:29:40 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard , Anil Madhavapeddy Message-ID: <2117752099.11110.1407155380714.JavaMail.www@wwinf1p23> In-Reply-To: References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7823928908729055352==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7823928908729055352== Content-Type: multipart/alternative; boundary="----=_Part_11109_2024052997.1407155380711" ------=_Part_11109_2024052997.1407155380711 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable thank you, I'm testing with the compilation of "xen-arm-builder." I'm tryin= g to put the image on my microsd there. I also added some options related t= o the nand in the kernel, but I do not know if it will suffice. I have not used mirage-xen-next yet. I learn about integration. =C2=A0 =C2=A0 > Message du 04/08/14 13:28 > De : "Thomas Leonard"=20 > A : "Anil Madhavapeddy"=20 > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 3 August 2014 17:24, Thomas Leonard wrote: > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > >> > >> hi, > >> > >> I recently compiled mirage for cubietruck. > >> > >> Everything works fine, but the system is extremely slow. > >> > >> Hi Gilles, > >> > >> Glad to hear you've got it up and running. Could you shed some light a= bout > >> the nature of the application that is slow? > >> > >> If it's networking, there's a known bug at the moment [1] due to a > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Tho= mas > >> Leonard has just applied a backport to the SDCard image builder [2] th= at > >> fixes this issue in Xen itself, so we could remove the workaround now = and > >> hopefully get back to decent networking performance (is this correct, > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > Yes, I'll rebuild the binary images at some point but for now you can > > build from Git. With that, you can revert back to the older > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. >=20 > Here are the new images: >=20 > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 >=20 > Installation instructions are here: >=20 > https://github.com/mirage/xen-arm-builder >=20 > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: >=20 > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1= .1 >=20 >=20 > --=20 > 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 > ------=_Part_11109_2024052997.1407155380711 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

thank you, I'm testing with the compilation of "xen-arm-builder." I'm tr= ying to put the image on my microsd there. I also added some options relate= d to the nand in the kernel, but I do not know if it will suffice.

I have not used mirage-xen-next yet. I learn about integration.

=C2=A0

=C2=A0

> Message du 04/08/14 13:28
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Anil Madhavapeddy" <anil@rec= oil.org>
> Copie =C3=A0 : "Gilles DALMAS" <gdalmas@wanadoo.fr= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
> On 3 August 2014 17:24, Thomas Leonard= <talex5@gmail.com> wrote:
> > On 3 August 2014 17:20, Ani= l Madhavapeddy <anil@recoil.org> wrote:
> >> On 3 Aug 2= 014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;>
> >> hi,
> >>
> >> I recen= tly compiled mirage for cubietruck.
> >>
> >> E= verything works fine, but the system is extremely slow.
> >><= br />> >> Hi Gilles,
> >>
> >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; >> the nature of the application that is slow?
> >><= br />> >> If it's networking, there's a known bug at the moment [1= ] due to a
> >> limitation on Xen 4.4/ARM that prevents multi= ple mapping of pages. Thomas
> >> Leonard has just applied a = backport to the SDCard image builder [2] that
> >> fixes this= issue in Xen itself, so we could remove the workaround now and
> &= gt;> hopefully get back to decent networking performance (is this correc= t,
> >> Thomas? I haven't had a chance to rebuild my own Cubi= e2 yet).
> >
> > Yes, I'll rebuild the binary images = at some point but for now you can
> > build from Git. With that,= you can revert back to the older
> > mirage-net-xen v1.1.1 to a= void the wait after sending each packet.
>
> Here are the = new images:
>
> http://blobs.openmirage.org/cubieboard2-xe= n-iso.tar.bz2
> http://blobs.openmirage.org/cubietruck-xen-iso.tar.= bz2
>
> Installation instructions are here:
>
> https://github.com/mirage/xen-arm-builder
>
> Remem= ber to use mirage-net-xen v1.1.1 as well, or it will still be slow:
&g= t;
> opam pin mirage-net-xen https://github.com/mirage/mirage-net-= xen.git#v1.1.1
>
>
> --
> Dr Thomas Leon= ard 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
>
------=_Part_11109_2024052997.1407155380711-- --===============7823928908729055352== 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 --===============7823928908729055352==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 12:29:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 12:29: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 1XEHOa-0002sz-V7; Mon, 04 Aug 2014 12:29:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEHOZ-0002se-3j for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 12:29:43 +0000 Received: from [85.158.143.35:62682] by server-1.bemta-4.messagelabs.com id 72/FC-05872-6BC7FD35; Mon, 04 Aug 2014 12:29:42 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-16.tower-21.messagelabs.com!1407155381!9885329!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29090 invoked from network); 4 Aug 2014 12:29:41 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-16.tower-21.messagelabs.com with SMTP; 4 Aug 2014 12:29:41 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d07 with ME id acVg1o00a11Dd4A03cVgBu; Mon, 04 Aug 2014 14:29:40 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 14:29:40 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 14:29:40 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard , Anil Madhavapeddy Message-ID: <2117752099.11110.1407155380714.JavaMail.www@wwinf1p23> In-Reply-To: References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7823928908729055352==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7823928908729055352== Content-Type: multipart/alternative; boundary="----=_Part_11109_2024052997.1407155380711" ------=_Part_11109_2024052997.1407155380711 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable thank you, I'm testing with the compilation of "xen-arm-builder." I'm tryin= g to put the image on my microsd there. I also added some options related t= o the nand in the kernel, but I do not know if it will suffice. I have not used mirage-xen-next yet. I learn about integration. =C2=A0 =C2=A0 > Message du 04/08/14 13:28 > De : "Thomas Leonard"=20 > A : "Anil Madhavapeddy"=20 > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 3 August 2014 17:24, Thomas Leonard wrote: > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > >> > >> hi, > >> > >> I recently compiled mirage for cubietruck. > >> > >> Everything works fine, but the system is extremely slow. > >> > >> Hi Gilles, > >> > >> Glad to hear you've got it up and running. Could you shed some light a= bout > >> the nature of the application that is slow? > >> > >> If it's networking, there's a known bug at the moment [1] due to a > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Tho= mas > >> Leonard has just applied a backport to the SDCard image builder [2] th= at > >> fixes this issue in Xen itself, so we could remove the workaround now = and > >> hopefully get back to decent networking performance (is this correct, > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > Yes, I'll rebuild the binary images at some point but for now you can > > build from Git. With that, you can revert back to the older > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. >=20 > Here are the new images: >=20 > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 >=20 > Installation instructions are here: >=20 > https://github.com/mirage/xen-arm-builder >=20 > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: >=20 > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1= .1 >=20 >=20 > --=20 > 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 > ------=_Part_11109_2024052997.1407155380711 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

thank you, I'm testing with the compilation of "xen-arm-builder." I'm tr= ying to put the image on my microsd there. I also added some options relate= d to the nand in the kernel, but I do not know if it will suffice.

I have not used mirage-xen-next yet. I learn about integration.

=C2=A0

=C2=A0

> Message du 04/08/14 13:28
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Anil Madhavapeddy" <anil@rec= oil.org>
> Copie =C3=A0 : "Gilles DALMAS" <gdalmas@wanadoo.fr= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
> On 3 August 2014 17:24, Thomas Leonard= <talex5@gmail.com> wrote:
> > On 3 August 2014 17:20, Ani= l Madhavapeddy <anil@recoil.org> wrote:
> >> On 3 Aug 2= 014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;>
> >> hi,
> >>
> >> I recen= tly compiled mirage for cubietruck.
> >>
> >> E= verything works fine, but the system is extremely slow.
> >><= br />> >> Hi Gilles,
> >>
> >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; >> the nature of the application that is slow?
> >><= br />> >> If it's networking, there's a known bug at the moment [1= ] due to a
> >> limitation on Xen 4.4/ARM that prevents multi= ple mapping of pages. Thomas
> >> Leonard has just applied a = backport to the SDCard image builder [2] that
> >> fixes this= issue in Xen itself, so we could remove the workaround now and
> &= gt;> hopefully get back to decent networking performance (is this correc= t,
> >> Thomas? I haven't had a chance to rebuild my own Cubi= e2 yet).
> >
> > Yes, I'll rebuild the binary images = at some point but for now you can
> > build from Git. With that,= you can revert back to the older
> > mirage-net-xen v1.1.1 to a= void the wait after sending each packet.
>
> Here are the = new images:
>
> http://blobs.openmirage.org/cubieboard2-xe= n-iso.tar.bz2
> http://blobs.openmirage.org/cubietruck-xen-iso.tar.= bz2
>
> Installation instructions are here:
>
> https://github.com/mirage/xen-arm-builder
>
> Remem= ber to use mirage-net-xen v1.1.1 as well, or it will still be slow:
&g= t;
> opam pin mirage-net-xen https://github.com/mirage/mirage-net-= xen.git#v1.1.1
>
>
> --
> Dr Thomas Leon= ard 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
>
------=_Part_11109_2024052997.1407155380711-- --===============7823928908729055352== 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 --===============7823928908729055352==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 13:03:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 13:03: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 1XEHvX-0003nx-Bv; Mon, 04 Aug 2014 13:03:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEHvV-0003np-U3 for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 13:03:46 +0000 Received: from [193.109.254.147:24254] by server-4.bemta-14.messagelabs.com id 3B/DD-23592-0B48FD35; Mon, 04 Aug 2014 13:03:44 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-6.tower-27.messagelabs.com!1407157423!13585397!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15730 invoked from network); 4 Aug 2014 13:03:43 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-6.tower-27.messagelabs.com with SMTP; 4 Aug 2014 13:03:43 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d02 with ME id ad3i1o00M11Dd4A03d3i8v; Mon, 04 Aug 2014 15:03:42 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 15:03:42 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 15:03:42 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard , Anil Madhavapeddy Message-ID: <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> In-Reply-To: References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7592534247170617092==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7592534247170617092== Content-Type: multipart/alternative; boundary="----=_Part_11953_961588162.1407157422724" ------=_Part_11953_961588162.1407157422724 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable apparently, the xen-arm-builder script solves the problem of slowness. even= without installing mirage-net-xen. > Message du 04/08/14 13:28 > De : "Thomas Leonard"=20 > A : "Anil Madhavapeddy"=20 > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 3 August 2014 17:24, Thomas Leonard wrote: > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > >> > >> hi, > >> > >> I recently compiled mirage for cubietruck. > >> > >> Everything works fine, but the system is extremely slow. > >> > >> Hi Gilles, > >> > >> Glad to hear you've got it up and running. Could you shed some light a= bout > >> the nature of the application that is slow? > >> > >> If it's networking, there's a known bug at the moment [1] due to a > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Tho= mas > >> Leonard has just applied a backport to the SDCard image builder [2] th= at > >> fixes this issue in Xen itself, so we could remove the workaround now = and > >> hopefully get back to decent networking performance (is this correct, > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > Yes, I'll rebuild the binary images at some point but for now you can > > build from Git. With that, you can revert back to the older > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. >=20 > Here are the new images: >=20 > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 >=20 > Installation instructions are here: >=20 > https://github.com/mirage/xen-arm-builder >=20 > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: >=20 > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1= .1 >=20 >=20 > --=20 > 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 > ------=_Part_11953_961588162.1407157422724 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

apparently, the xen-arm-builder script solves the problem of slowness. e= ven without installing mirage-net-xen.




> Message du 04/08/14 13:28
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Anil Madhavapeddy" <anil@rec= oil.org>
> Copie =C3=A0 : "Gilles DALMAS" <gdalmas@wanadoo.fr= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
> On 3 August 2014 17:24, Thomas Leonard= <talex5@gmail.com> wrote:
> > On 3 August 2014 17:20, Ani= l Madhavapeddy <anil@recoil.org> wrote:
> >> On 3 Aug 2= 014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;>
> >> hi,
> >>
> >> I recen= tly compiled mirage for cubietruck.
> >>
> >> E= verything works fine, but the system is extremely slow.
> >><= br />> >> Hi Gilles,
> >>
> >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; >> the nature of the application that is slow?
> >><= br />> >> If it's networking, there's a known bug at the moment [1= ] due to a
> >> limitation on Xen 4.4/ARM that prevents multi= ple mapping of pages. Thomas
> >> Leonard has just applied a = backport to the SDCard image builder [2] that
> >> fixes this= issue in Xen itself, so we could remove the workaround now and
> &= gt;> hopefully get back to decent networking performance (is this correc= t,
> >> Thomas? I haven't had a chance to rebuild my own Cubi= e2 yet).
> >
> > Yes, I'll rebuild the binary images = at some point but for now you can
> > build from Git. With that,= you can revert back to the older
> > mirage-net-xen v1.1.1 to a= void the wait after sending each packet.
>
> Here are the = new images:
>
> http://blobs.openmirage.org/cubieboard2-xe= n-iso.tar.bz2
> http://blobs.openmirage.org/cubietruck-xen-iso.tar.= bz2
>
> Installation instructions are here:
>
> https://github.com/mirage/xen-arm-builder
>
> Remem= ber to use mirage-net-xen v1.1.1 as well, or it will still be slow:
&g= t;
> opam pin mirage-net-xen https://github.com/mirage/mirage-net-= xen.git#v1.1.1
>
>
> --
> Dr Thomas Leon= ard 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
>
------=_Part_11953_961588162.1407157422724-- --===============7592534247170617092== 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 --===============7592534247170617092==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 13:03:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 13:03: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 1XEHvX-0003nx-Bv; Mon, 04 Aug 2014 13:03:47 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEHvV-0003np-U3 for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 13:03:46 +0000 Received: from [193.109.254.147:24254] by server-4.bemta-14.messagelabs.com id 3B/DD-23592-0B48FD35; Mon, 04 Aug 2014 13:03:44 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-6.tower-27.messagelabs.com!1407157423!13585397!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15730 invoked from network); 4 Aug 2014 13:03:43 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-6.tower-27.messagelabs.com with SMTP; 4 Aug 2014 13:03:43 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d02 with ME id ad3i1o00M11Dd4A03d3i8v; Mon, 04 Aug 2014 15:03:42 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 15:03:42 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 15:03:42 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard , Anil Madhavapeddy Message-ID: <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> In-Reply-To: References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7592534247170617092==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7592534247170617092== Content-Type: multipart/alternative; boundary="----=_Part_11953_961588162.1407157422724" ------=_Part_11953_961588162.1407157422724 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable apparently, the xen-arm-builder script solves the problem of slowness. even= without installing mirage-net-xen. > Message du 04/08/14 13:28 > De : "Thomas Leonard"=20 > A : "Anil Madhavapeddy"=20 > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 3 August 2014 17:24, Thomas Leonard wrote: > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > >> > >> hi, > >> > >> I recently compiled mirage for cubietruck. > >> > >> Everything works fine, but the system is extremely slow. > >> > >> Hi Gilles, > >> > >> Glad to hear you've got it up and running. Could you shed some light a= bout > >> the nature of the application that is slow? > >> > >> If it's networking, there's a known bug at the moment [1] due to a > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Tho= mas > >> Leonard has just applied a backport to the SDCard image builder [2] th= at > >> fixes this issue in Xen itself, so we could remove the workaround now = and > >> hopefully get back to decent networking performance (is this correct, > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > Yes, I'll rebuild the binary images at some point but for now you can > > build from Git. With that, you can revert back to the older > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. >=20 > Here are the new images: >=20 > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 >=20 > Installation instructions are here: >=20 > https://github.com/mirage/xen-arm-builder >=20 > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: >=20 > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1= .1 >=20 >=20 > --=20 > 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 > ------=_Part_11953_961588162.1407157422724 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

apparently, the xen-arm-builder script solves the problem of slowness. e= ven without installing mirage-net-xen.




> Message du 04/08/14 13:28
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Anil Madhavapeddy" <anil@rec= oil.org>
> Copie =C3=A0 : "Gilles DALMAS" <gdalmas@wanadoo.fr= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
> On 3 August 2014 17:24, Thomas Leonard= <talex5@gmail.com> wrote:
> > On 3 August 2014 17:20, Ani= l Madhavapeddy <anil@recoil.org> wrote:
> >> On 3 Aug 2= 014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;>
> >> hi,
> >>
> >> I recen= tly compiled mirage for cubietruck.
> >>
> >> E= verything works fine, but the system is extremely slow.
> >><= br />> >> Hi Gilles,
> >>
> >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; >> the nature of the application that is slow?
> >><= br />> >> If it's networking, there's a known bug at the moment [1= ] due to a
> >> limitation on Xen 4.4/ARM that prevents multi= ple mapping of pages. Thomas
> >> Leonard has just applied a = backport to the SDCard image builder [2] that
> >> fixes this= issue in Xen itself, so we could remove the workaround now and
> &= gt;> hopefully get back to decent networking performance (is this correc= t,
> >> Thomas? I haven't had a chance to rebuild my own Cubi= e2 yet).
> >
> > Yes, I'll rebuild the binary images = at some point but for now you can
> > build from Git. With that,= you can revert back to the older
> > mirage-net-xen v1.1.1 to a= void the wait after sending each packet.
>
> Here are the = new images:
>
> http://blobs.openmirage.org/cubieboard2-xe= n-iso.tar.bz2
> http://blobs.openmirage.org/cubietruck-xen-iso.tar.= bz2
>
> Installation instructions are here:
>
> https://github.com/mirage/xen-arm-builder
>
> Remem= ber to use mirage-net-xen v1.1.1 as well, or it will still be slow:
&g= t;
> opam pin mirage-net-xen https://github.com/mirage/mirage-net-= xen.git#v1.1.1
>
>
> --
> Dr Thomas Leon= ard 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
>
------=_Part_11953_961588162.1407157422724-- --===============7592534247170617092== 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 --===============7592534247170617092==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 13:40:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 13:40: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 1XEIUu-00062e-NS; Mon, 04 Aug 2014 13:40:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEIUs-000625-UQ for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 13:40:19 +0000 Received: from [85.158.139.211:49885] by server-12.bemta-5.messagelabs.com id 78/2D-22251-24D8FD35; Mon, 04 Aug 2014 13:40:18 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-12.tower-206.messagelabs.com!1407159617!11751512!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21688 invoked from network); 4 Aug 2014 13:40:17 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-12.tower-206.messagelabs.com with SMTP; 4 Aug 2014 13:40:17 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d38 with ME id adgG1o00N11Dd4A03dgGLo; Mon, 04 Aug 2014 15:40:16 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 15:40:16 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 15:40:16 +0200 (CEST) From: Gilles DALMAS To: mirageos-devel@lists.xenproject.org Message-ID: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] xpenology dsm domu on xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7873299372583059112==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7873299372583059112== Content-Type: multipart/alternative; boundary="----=_Part_12893_374556864.1407159616778" ------=_Part_12893_374556864.1407159616778 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I try to install the dsm of xpenology on xen but I do not control all the c= onfiguration xen command line. Is someone could help me to transcribe it: =C2=A0 - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB R= AM - Using HVM (Other install media, during Xen VM creation). - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3Df= alse` (Makes sure virt-what coretly recognizes Xen) - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/s= da1` (Using Debian Live distro) - Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` added `= vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6` - DSM 5.0 4458 installed after booting with grub menu item gnoboot.me =E2= =80=93> install/upgrade/downgrade 4458 =C2=A0 =C2=A0in command line ? =C2=A0 at least for the introduction of the working environment. (Disc creation, .= conf parameter file) ------=_Part_12893_374556864.1407159616778 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi,

I try to install the dsm of xpenology on xen but I do not control all th= e configuration xen command line. Is someone could help me to transcribe it= :

=C2=A0

- Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512M= B RAM
- Using HVM (Other install media, during Xen VM creation).
= - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3Df= alse` (Makes sure virt-what coretly recognizes Xen)
- gnoBoot image in= stalled using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/sda1` (Using Debian= Live distro)
- Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/m= enu_me.lst` added `vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6`
- DSM 5.0 44= 58 installed after booting with grub menu item gnoboot.me =E2=80=93> ins= tall/upgrade/downgrade 4458

=C2=A0

=C2=A0in command line ?

=C2=A0

at least for the introduction of the working environment. (Disc creation= , .conf parameter file)

------=_Part_12893_374556864.1407159616778-- --===============7873299372583059112== 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 --===============7873299372583059112==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 13:40:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 13:40: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 1XEIUu-00062e-NS; Mon, 04 Aug 2014 13:40:20 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEIUs-000625-UQ for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 13:40:19 +0000 Received: from [85.158.139.211:49885] by server-12.bemta-5.messagelabs.com id 78/2D-22251-24D8FD35; Mon, 04 Aug 2014 13:40:18 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-12.tower-206.messagelabs.com!1407159617!11751512!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21688 invoked from network); 4 Aug 2014 13:40:17 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-12.tower-206.messagelabs.com with SMTP; 4 Aug 2014 13:40:17 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d38 with ME id adgG1o00N11Dd4A03dgGLo; Mon, 04 Aug 2014 15:40:16 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 15:40:16 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 15:40:16 +0200 (CEST) From: Gilles DALMAS To: mirageos-devel@lists.xenproject.org Message-ID: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] xpenology dsm domu on xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7873299372583059112==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7873299372583059112== Content-Type: multipart/alternative; boundary="----=_Part_12893_374556864.1407159616778" ------=_Part_12893_374556864.1407159616778 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I try to install the dsm of xpenology on xen but I do not control all the c= onfiguration xen command line. Is someone could help me to transcribe it: =C2=A0 - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB R= AM - Using HVM (Other install media, during Xen VM creation). - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3Df= alse` (Makes sure virt-what coretly recognizes Xen) - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/s= da1` (Using Debian Live distro) - Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` added `= vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6` - DSM 5.0 4458 installed after booting with grub menu item gnoboot.me =E2= =80=93> install/upgrade/downgrade 4458 =C2=A0 =C2=A0in command line ? =C2=A0 at least for the introduction of the working environment. (Disc creation, .= conf parameter file) ------=_Part_12893_374556864.1407159616778 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hi,

I try to install the dsm of xpenology on xen but I do not control all th= e configuration xen command line. Is someone could help me to transcribe it= :

=C2=A0

- Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512M= B RAM
- Using HVM (Other install media, during Xen VM creation).
= - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3Df= alse` (Makes sure virt-what coretly recognizes Xen)
- gnoBoot image in= stalled using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/sda1` (Using Debian= Live distro)
- Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/m= enu_me.lst` added `vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6`
- DSM 5.0 44= 58 installed after booting with grub menu item gnoboot.me =E2=80=93> ins= tall/upgrade/downgrade 4458

=C2=A0

=C2=A0in command line ?

=C2=A0

at least for the introduction of the working environment. (Disc creation= , .conf parameter file)

------=_Part_12893_374556864.1407159616778-- --===============7873299372583059112== 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 --===============7873299372583059112==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 13:54:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 13:54: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 1XEIiT-0007a1-RI; Mon, 04 Aug 2014 13:54:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEIiT-0007Zf-29 for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 13:54:21 +0000 Received: from [85.158.139.211:40718] by server-7.bemta-5.messagelabs.com id 36/ED-30869-B809FD35; Mon, 04 Aug 2014 13:54:19 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-13.tower-206.messagelabs.com!1407160433!11788608!1 X-Originating-IP: [80.12.242.127] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30564 invoked from network); 4 Aug 2014 13:53:54 -0000 Received: from smtp05.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.127) by server-13.tower-206.messagelabs.com with SMTP; 4 Aug 2014 13:53:54 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d10 with ME id adtt1o00C11Dd4A03dttlR; Mon, 04 Aug 2014 15:53:53 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 15:53:53 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 15:53:53 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard , Anil Madhavapeddy Message-ID: <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> In-Reply-To: <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4011327587731861157==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4011327587731861157== Content-Type: multipart/alternative; boundary="----=_Part_13156_1435929451.1407160433403" ------=_Part_13156_1435929451.1407160433403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruck-D= ebian/blob/master/config/kernel.config.3.4.61 there is for example the line= CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the ke= rnel, how is it that this option does not appear in the following versions = of the kernel? if I add it manually in the config file, is it processed? > Message du 04/08/14 15:03 > De : "Gilles DALMAS"=20 > A : "Thomas Leonard" , "Anil Madhavapeddy"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > > apparently, the xen-arm-builder script solves the problem of slowness. ev= en without installing mirage-net-xen. > Message du 04/08/14 13:28 > De : "Thomas Leonard"=20 > A : "Anil Madhavapeddy"=20 > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 3 August 2014 17:24, Thomas Leonard wrote: > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > >> > >> hi, > >> > >> I recently compiled mirage for cubietruck. > >> > >> Everything works fine, but the system is extremely slow. > >> > >> Hi Gilles, > >> > >> Glad to hear you've got it up and running. Could you shed some light a= bout > >> the nature of the application that is slow? > >> > >> If it's networking, there's a known bug at the moment [1] due to a > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Tho= mas > >> Leonard has just applied a backport to the SDCard image builder [2] th= at > >> fixes this issue in Xen itself, so we could remove the workaround now = and > >> hopefully get back to decent networking performance (is this correct, > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > Yes, I'll rebuild the binary images at some point but for now you can > > build from Git. With that, you can revert back to the older > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. >=20 > Here are the new images: >=20 > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 >=20 > Installation instructions are here: >=20 > https://github.com/mirage/xen-arm-builder >=20 > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: >=20 > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1= .1 >=20 >=20 > --=20 > 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 ------=_Part_13156_1435929451.1407160433403 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruc= k-Debian/blob/master/config/kernel.config.3.4.61 there is for example the l= ine CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the= kernel, how is it that this option does not appear in the following versio= ns of the kernel? if I add it manually in the config file, is it processed?=




> Message du 04/08/14 15:03
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "Thomas Leonard" <talex5@gma= il.com>, "Anil Madhavapeddy" <anil@recoil.org>
> Copie =C3= =A0 : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
>

> apparently, the xen-arm-builder script solves the problem of slowne= ss. even without installing mirage-net-xen.




> Message du 04/08/14 13:28
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Anil Madhavapeddy" <anil@rec= oil.org>
> Copie =C3=A0 : "Gilles DALMAS" <gdalmas@wanadoo.fr= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
> On 3 August 2014 17:24, Thomas Leonard= <talex5@gmail.com> wrote:
> > On 3 August 2014 17:20, Ani= l Madhavapeddy <anil@recoil.org> wrote:
> >> On 3 Aug 2= 014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;>
> >> hi,
> >>
> >> I recen= tly compiled mirage for cubietruck.
> >>
> >> E= verything works fine, but the system is extremely slow.
> >><= br />> >> Hi Gilles,
> >>
> >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; >> the nature of the application that is slow?
> >><= br />> >> If it's networking, there's a known bug at the moment [1= ] due to a
> >> limitation on Xen 4.4/ARM that prevents multi= ple mapping of pages. Thomas
> >> Leonard has just applied a = backport to the SDCard image builder [2] that
> >> fixes this= issue in Xen itself, so we could remove the workaround now and
> &= gt;> hopefully get back to decent networking performance (is this correc= t,
> >> Thomas? I haven't had a chance to rebuild my own Cubi= e2 yet).
> >
> > Yes, I'll rebuild the binary images = at some point but for now you can
> > build from Git. With that,= you can revert back to the older
> > mirage-net-xen v1.1.1 to a= void the wait after sending each packet.
>
> Here are the = new images:
>
> http://blobs.openmirage.org/cubieboard2-xe= n-iso.tar.bz2
> http://blobs.openmirage.org/cubietruck-xen-iso.tar.= bz2
>
> Installation instructions are here:
>
> https://github.com/mirage/xen-arm-builder
>
> Remem= ber to use mirage-net-xen v1.1.1 as well, or it will still be slow:
&g= t;
> opam pin mirage-net-xen https://github.com/mirage/mirage-net-= xen.git#v1.1.1
>
>
> --
> Dr Thomas Leon= ard 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.xe= nproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mira= geos-devel

------=_Part_13156_1435929451.1407160433403-- --===============4011327587731861157== 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 --===============4011327587731861157==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 13:54:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 13:54: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 1XEIiT-0007a1-RI; Mon, 04 Aug 2014 13:54:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEIiT-0007Zf-29 for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 13:54:21 +0000 Received: from [85.158.139.211:40718] by server-7.bemta-5.messagelabs.com id 36/ED-30869-B809FD35; Mon, 04 Aug 2014 13:54:19 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-13.tower-206.messagelabs.com!1407160433!11788608!1 X-Originating-IP: [80.12.242.127] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30564 invoked from network); 4 Aug 2014 13:53:54 -0000 Received: from smtp05.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.127) by server-13.tower-206.messagelabs.com with SMTP; 4 Aug 2014 13:53:54 -0000 Received: from wwinf1p23 ([10.223.75.47]) by mwinf5d10 with ME id adtt1o00C11Dd4A03dttlR; Mon, 04 Aug 2014 15:53:53 +0200 X-ME-Helo: wwinf1p23 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Mon, 04 Aug 2014 15:53:53 +0200 X-ME-IP: 90.29.191.133 Date: Mon, 4 Aug 2014 15:53:53 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard , Anil Madhavapeddy Message-ID: <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> In-Reply-To: <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> MIME-Version: 1.0 X-Originating-IP: [90.29.191.133] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============4011327587731861157==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4011327587731861157== Content-Type: multipart/alternative; boundary="----=_Part_13156_1435929451.1407160433403" ------=_Part_13156_1435929451.1407160433403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruck-D= ebian/blob/master/config/kernel.config.3.4.61 there is for example the line= CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the ke= rnel, how is it that this option does not appear in the following versions = of the kernel? if I add it manually in the config file, is it processed? > Message du 04/08/14 15:03 > De : "Gilles DALMAS"=20 > A : "Thomas Leonard" , "Anil Madhavapeddy"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > > apparently, the xen-arm-builder script solves the problem of slowness. ev= en without installing mirage-net-xen. > Message du 04/08/14 13:28 > De : "Thomas Leonard"=20 > A : "Anil Madhavapeddy"=20 > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 3 August 2014 17:24, Thomas Leonard wrote: > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > >> > >> hi, > >> > >> I recently compiled mirage for cubietruck. > >> > >> Everything works fine, but the system is extremely slow. > >> > >> Hi Gilles, > >> > >> Glad to hear you've got it up and running. Could you shed some light a= bout > >> the nature of the application that is slow? > >> > >> If it's networking, there's a known bug at the moment [1] due to a > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. Tho= mas > >> Leonard has just applied a backport to the SDCard image builder [2] th= at > >> fixes this issue in Xen itself, so we could remove the workaround now = and > >> hopefully get back to decent networking performance (is this correct, > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > Yes, I'll rebuild the binary images at some point but for now you can > > build from Git. With that, you can revert back to the older > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. >=20 > Here are the new images: >=20 > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 >=20 > Installation instructions are here: >=20 > https://github.com/mirage/xen-arm-builder >=20 > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow: >=20 > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1.1= .1 >=20 >=20 > --=20 > 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 ------=_Part_13156_1435929451.1407160433403 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruc= k-Debian/blob/master/config/kernel.config.3.4.61 there is for example the l= ine CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the= kernel, how is it that this option does not appear in the following versio= ns of the kernel? if I add it manually in the config file, is it processed?=




> Message du 04/08/14 15:03
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "Thomas Leonard" <talex5@gma= il.com>, "Anil Madhavapeddy" <anil@recoil.org>
> Copie =C3= =A0 : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
>

> apparently, the xen-arm-builder script solves the problem of slowne= ss. even without installing mirage-net-xen.




> Message du 04/08/14 13:28
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Anil Madhavapeddy" <anil@rec= oil.org>
> Copie =C3=A0 : "Gilles DALMAS" <gdalmas@wanadoo.fr= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
> On 3 August 2014 17:24, Thomas Leonard= <talex5@gmail.com> wrote:
> > On 3 August 2014 17:20, Ani= l Madhavapeddy <anil@recoil.org> wrote:
> >> On 3 Aug 2= 014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;>
> >> hi,
> >>
> >> I recen= tly compiled mirage for cubietruck.
> >>
> >> E= verything works fine, but the system is extremely slow.
> >><= br />> >> Hi Gilles,
> >>
> >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; >> the nature of the application that is slow?
> >><= br />> >> If it's networking, there's a known bug at the moment [1= ] due to a
> >> limitation on Xen 4.4/ARM that prevents multi= ple mapping of pages. Thomas
> >> Leonard has just applied a = backport to the SDCard image builder [2] that
> >> fixes this= issue in Xen itself, so we could remove the workaround now and
> &= gt;> hopefully get back to decent networking performance (is this correc= t,
> >> Thomas? I haven't had a chance to rebuild my own Cubi= e2 yet).
> >
> > Yes, I'll rebuild the binary images = at some point but for now you can
> > build from Git. With that,= you can revert back to the older
> > mirage-net-xen v1.1.1 to a= void the wait after sending each packet.
>
> Here are the = new images:
>
> http://blobs.openmirage.org/cubieboard2-xe= n-iso.tar.bz2
> http://blobs.openmirage.org/cubietruck-xen-iso.tar.= bz2
>
> Installation instructions are here:
>
> https://github.com/mirage/xen-arm-builder
>
> Remem= ber to use mirage-net-xen v1.1.1 as well, or it will still be slow:
&g= t;
> opam pin mirage-net-xen https://github.com/mirage/mirage-net-= xen.git#v1.1.1
>
>
> --
> Dr Thomas Leon= ard 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.xe= nproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mira= geos-devel

------=_Part_13156_1435929451.1407160433403-- --===============4011327587731861157== 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 --===============4011327587731861157==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 18:51:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 18:51: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 1XENLU-0004Qp-Ur; Mon, 04 Aug 2014 18:50:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XENLT-0004Qg-QS for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 18:50:56 +0000 Received: from [85.158.137.68:2361] by server-16.bemta-3.messagelabs.com id 52/FB-14115-F06DFD35; Mon, 04 Aug 2014 18:50:55 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1407178237!11809849!1 X-Originating-IP: [209.85.214.174] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDg3NzggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30843 invoked from network); 4 Aug 2014 18:50:38 -0000 Received: from mail-ob0-f174.google.com (HELO mail-ob0-f174.google.com) (209.85.214.174) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Aug 2014 18:50:38 -0000 Received: by mail-ob0-f174.google.com with SMTP id vb8so4788654obc.19 for ; Mon, 04 Aug 2014 11:50:35 -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=WpNcKz+dqB4YjiyiofS54QuSug2hhjFn2Fo14d55zG4=; b=X6avUAQEZ1V346hYQc25V15SP/8m254CiqkdTQHrYLHGa9wTXkT/nh7lMLN+w7h1gt Be1cvlJ3Sj+4RZB6NXArpTeq/hoiH3TExLDzjmyT4dSKJ1UJhlveTQLTYbTsuPH8aDeL tSIO3oLzH8VcFnhbeW0XMUeCsuiR0lSs4FcFl8SmsJoIjfnFFuOKj9mJLJ4Kd84XwPqS tZOZFzno5Hv4ybIncP2UrjbIE//EtBB8IfpucrbMbBj4pzsa4KuiOZXeQys5/BiRkYbv RfX8k0hYp/pXkQsjBLWobPQrDCG6vbyOH1TMyjcx/TLIBI0lKTPuVRIBnm3HWgZ9lqBs we0w== MIME-Version: 1.0 X-Received: by 10.60.94.242 with SMTP id df18mr34796581oeb.57.1407178235260; Mon, 04 Aug 2014 11:50:35 -0700 (PDT) Received: by 10.202.197.146 with HTTP; Mon, 4 Aug 2014 11:50:35 -0700 (PDT) In-Reply-To: <53C81D1E.4020102@mehnert.org> References: <53C81D1E.4020102@mehnert.org> Date: Mon, 4 Aug 2014 11:50:35 -0700 Message-ID: From: Jyotsna Prakash To: Hannes Mehnert Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8507721453444188647==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8507721453444188647== Content-Type: multipart/alternative; boundary=089e01182870d934b804ffd236cb --089e01182870d934b804ffd236cb Content-Type: text/plain; charset=UTF-8 Hello, I've written a blog post about the EC2 image bundling process, and what I have left to do. The short of it is: - There is something wrong with the method I am using to turn xen kernels into images. The script, which I originally obtained from the mirage docs ( http://openmirage.org/docs/xen-boot), was working earlier this summer. I may have accidentally deleted the line that generates an initrd. The original script - I am running shell command with OCaml's `Unix.open_process_in`. I need to figure out why the command is not giving consistent results... about 1 out of 10 times it will produce the correct digest. (A SHA1 digest of the input image after it is compressed and encrypted.) The shell command is openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h -S --owner 0 --group 0 -C /tmp mymirage.img | tee /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc And Hannes, thanks for your help! I was able to use nocrypto and ocaml-x509 to extract RSA keys and encrypt. I will look into replacing cryptokit with ocaml-sha. Best, Jyotsna On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi Jyotsna, > > On 07/17/2014 19:48, Jyotsna Prakash wrote: > > For my GSoC project I've been working on OCaml bindings to the EC2 > > API. The code is at https://github.com/moonlightdrive/ocaml-ec2 > > Awesome! > > > I've yet to launch a Mirage-backed VM without using the Amazon's > > CLI tools. The process involves producing an xml manifest > > describing an image; the manifest contains fields of RSA encrypted > > data. Problem is, I don't have any way to take my public keys (pem > > files) and turn them into `Cryptokit.RSA.key`s. > > AFAICS you're only using SHA256 from Cryptokit so far -- you might > want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that. > > Also, David wrote ocaml-nocrypto > (https://github.com/mirleft/ocaml-nocrypto) and we further developed > ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can > parse pem to get a certificate > (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) > or a private key (RSA) > https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 > (example usage: > https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) > > What do you need to do with the RSA key? The nocrypto API is at > https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli > > > Cheers, > > Hannes > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (FreeBSD) > > iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI > JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ > xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM > eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU > 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d > PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW > Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k > pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG > AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p > XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s > 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz > pgdhpVDaP3Ocu+kRpFEB > =zzgd > -----END PGP SIGNATURE----- > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e01182870d934b804ffd236cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I've written a blog post about the = EC2 image bundling process, and what I have left to do. The short of it is:=

- There is something wrong with the method I am using to turn xen kerne= ls into images. The script, which I originally obtained from the mirage doc= s (http://openmirage.org/do= cs/xen-boot), was working earlier this summer. I may have accidentally = deleted the line that generates an initrd. The original script

- I am running shell command with OCaml's `Unix.open_process_i= n`. I need to figure out why the command is not giving consistent results..= . about 1 out of 10 times it will produce the correct digest. (A SHA1 diges= t of the input image after it is compressed and encrypted.)
The shell command is
=C2=A0 openssl sha1 < /tmp/ec2-bundle-image-dige= st-pipe-10174 & tar -c -h -S --owner 0 --group 0 -C /tmp mymirage.img |= tee /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e -ae= s-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv bbbbbbbbbbbbbbbbbbbbbbbbb= bbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc

And Hannes, thanks for your help! I was able to use nocrypto= and ocaml-x509 to extract RSA keys and encrypt. I will look into replacing= cryptokit with ocaml-sha.

Best,
Jyotsna


O= n Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert <hannes@mehnert.org&g= t; wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 19:48, Jyotsna Prakash wrote:
> For my GSoC project I've been working on OCaml bindings to the EC2=
> API. The code is at https://github.com/moonlightdrive/ocaml-ec2

Awesome!

> I've yet to launch a Mirage-backed VM without using the Amazon'= ;s
> CLI tools. The process involves producing an xml manifest
> describing an image; the manifest contains fields of RSA encrypted
> data. Problem is, I don't have any way to take my public keys (pem=
> files) and turn them into `Cryptokit.RSA.key`s.

AFAICS you're only using SHA256 from Cryptokit so far -- you migh= t
want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that.

Also, David wrote ocaml-nocrypto
(ht= tps://github.com/mirleft/ocaml-nocrypto) and we further developed
ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can
parse pem to get a certificate
(https://github.com/mirleft/ocaml-x509/blob/master/li= b/x509.mli#L18)
or a private key (RSA)
https://github.com/mirleft/ocaml-x509/blob/master/lib= /x509.mli#L30
(example usage:
https://github.com/mirleft/ocaml-tls/blob/master/lw= t/x509_lwt.ml#L49)

What do you need to do with the RSA key? The nocrypto API is at
https://github.com/mirleft/ocaml-nocrypto/blob/master/= src/rsa.mli


Cheers,

Hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM
eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU
7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d
PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END PGP SIGNATURE-----

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

--089e01182870d934b804ffd236cb-- --===============8507721453444188647== 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 --===============8507721453444188647==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 18:51:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 18:51: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 1XENLU-0004Qp-Ur; Mon, 04 Aug 2014 18:50:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XENLT-0004Qg-QS for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 18:50:56 +0000 Received: from [85.158.137.68:2361] by server-16.bemta-3.messagelabs.com id 52/FB-14115-F06DFD35; Mon, 04 Aug 2014 18:50:55 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-8.tower-31.messagelabs.com!1407178237!11809849!1 X-Originating-IP: [209.85.214.174] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNDg3NzggKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30843 invoked from network); 4 Aug 2014 18:50:38 -0000 Received: from mail-ob0-f174.google.com (HELO mail-ob0-f174.google.com) (209.85.214.174) by server-8.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 4 Aug 2014 18:50:38 -0000 Received: by mail-ob0-f174.google.com with SMTP id vb8so4788654obc.19 for ; Mon, 04 Aug 2014 11:50:35 -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=WpNcKz+dqB4YjiyiofS54QuSug2hhjFn2Fo14d55zG4=; b=X6avUAQEZ1V346hYQc25V15SP/8m254CiqkdTQHrYLHGa9wTXkT/nh7lMLN+w7h1gt Be1cvlJ3Sj+4RZB6NXArpTeq/hoiH3TExLDzjmyT4dSKJ1UJhlveTQLTYbTsuPH8aDeL tSIO3oLzH8VcFnhbeW0XMUeCsuiR0lSs4FcFl8SmsJoIjfnFFuOKj9mJLJ4Kd84XwPqS tZOZFzno5Hv4ybIncP2UrjbIE//EtBB8IfpucrbMbBj4pzsa4KuiOZXeQys5/BiRkYbv RfX8k0hYp/pXkQsjBLWobPQrDCG6vbyOH1TMyjcx/TLIBI0lKTPuVRIBnm3HWgZ9lqBs we0w== MIME-Version: 1.0 X-Received: by 10.60.94.242 with SMTP id df18mr34796581oeb.57.1407178235260; Mon, 04 Aug 2014 11:50:35 -0700 (PDT) Received: by 10.202.197.146 with HTTP; Mon, 4 Aug 2014 11:50:35 -0700 (PDT) In-Reply-To: <53C81D1E.4020102@mehnert.org> References: <53C81D1E.4020102@mehnert.org> Date: Mon, 4 Aug 2014 11:50:35 -0700 Message-ID: From: Jyotsna Prakash To: Hannes Mehnert Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8507721453444188647==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8507721453444188647== Content-Type: multipart/alternative; boundary=089e01182870d934b804ffd236cb --089e01182870d934b804ffd236cb Content-Type: text/plain; charset=UTF-8 Hello, I've written a blog post about the EC2 image bundling process, and what I have left to do. The short of it is: - There is something wrong with the method I am using to turn xen kernels into images. The script, which I originally obtained from the mirage docs ( http://openmirage.org/docs/xen-boot), was working earlier this summer. I may have accidentally deleted the line that generates an initrd. The original script - I am running shell command with OCaml's `Unix.open_process_in`. I need to figure out why the command is not giving consistent results... about 1 out of 10 times it will produce the correct digest. (A SHA1 digest of the input image after it is compressed and encrypted.) The shell command is openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h -S --owner 0 --group 0 -C /tmp mymirage.img | tee /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc And Hannes, thanks for your help! I was able to use nocrypto and ocaml-x509 to extract RSA keys and encrypt. I will look into replacing cryptokit with ocaml-sha. Best, Jyotsna On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA384 > > Hi Jyotsna, > > On 07/17/2014 19:48, Jyotsna Prakash wrote: > > For my GSoC project I've been working on OCaml bindings to the EC2 > > API. The code is at https://github.com/moonlightdrive/ocaml-ec2 > > Awesome! > > > I've yet to launch a Mirage-backed VM without using the Amazon's > > CLI tools. The process involves producing an xml manifest > > describing an image; the manifest contains fields of RSA encrypted > > data. Problem is, I don't have any way to take my public keys (pem > > files) and turn them into `Cryptokit.RSA.key`s. > > AFAICS you're only using SHA256 from Cryptokit so far -- you might > want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that. > > Also, David wrote ocaml-nocrypto > (https://github.com/mirleft/ocaml-nocrypto) and we further developed > ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can > parse pem to get a certificate > (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) > or a private key (RSA) > https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 > (example usage: > https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) > > What do you need to do with the RSA key? The nocrypto API is at > https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli > > > Cheers, > > Hannes > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (FreeBSD) > > iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI > JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ > xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM > eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU > 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d > PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW > Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k > pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG > AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p > XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s > 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz > pgdhpVDaP3Ocu+kRpFEB > =zzgd > -----END PGP SIGNATURE----- > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e01182870d934b804ffd236cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

I've written a blog post about the = EC2 image bundling process, and what I have left to do. The short of it is:=

- There is something wrong with the method I am using to turn xen kerne= ls into images. The script, which I originally obtained from the mirage doc= s (http://openmirage.org/do= cs/xen-boot), was working earlier this summer. I may have accidentally = deleted the line that generates an initrd. The original script

- I am running shell command with OCaml's `Unix.open_process_i= n`. I need to figure out why the command is not giving consistent results..= . about 1 out of 10 times it will produce the correct digest. (A SHA1 diges= t of the input image after it is compressed and encrypted.)
The shell command is
=C2=A0 openssl sha1 < /tmp/ec2-bundle-image-dige= st-pipe-10174 & tar -c -h -S --owner 0 --group 0 -C /tmp mymirage.img |= tee /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e -ae= s-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv bbbbbbbbbbbbbbbbbbbbbbbbb= bbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc

And Hannes, thanks for your help! I was able to use nocrypto= and ocaml-x509 to extract RSA keys and encrypt. I will look into replacing= cryptokit with ocaml-sha.

Best,
Jyotsna


O= n Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert <hannes@mehnert.org&g= t; wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 19:48, Jyotsna Prakash wrote:
> For my GSoC project I've been working on OCaml bindings to the EC2=
> API. The code is at https://github.com/moonlightdrive/ocaml-ec2

Awesome!

> I've yet to launch a Mirage-backed VM without using the Amazon'= ;s
> CLI tools. The process involves producing an xml manifest
> describing an image; the manifest contains fields of RSA encrypted
> data. Problem is, I don't have any way to take my public keys (pem=
> files) and turn them into `Cryptokit.RSA.key`s.

AFAICS you're only using SHA256 from Cryptokit so far -- you migh= t
want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that.

Also, David wrote ocaml-nocrypto
(ht= tps://github.com/mirleft/ocaml-nocrypto) and we further developed
ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can
parse pem to get a certificate
(https://github.com/mirleft/ocaml-x509/blob/master/li= b/x509.mli#L18)
or a private key (RSA)
https://github.com/mirleft/ocaml-x509/blob/master/lib= /x509.mli#L30
(example usage:
https://github.com/mirleft/ocaml-tls/blob/master/lw= t/x509_lwt.ml#L49)

What do you need to do with the RSA key? The nocrypto API is at
https://github.com/mirleft/ocaml-nocrypto/blob/master/= src/rsa.mli


Cheers,

Hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM
eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU
7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d
PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END PGP SIGNATURE-----

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

--089e01182870d934b804ffd236cb-- --===============8507721453444188647== 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 --===============8507721453444188647==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 18:53:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 18:53: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 1XENNa-0004VA-A0; Mon, 04 Aug 2014 18:53:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XENNZ-0004V3-Gn for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 18:53:05 +0000 Received: from [193.109.254.147:46582] by server-15.bemta-14.messagelabs.com id 52/E2-30948-096DFD35; Mon, 04 Aug 2014 18:53:04 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1407178369!13678209!1 X-Originating-IP: [209.85.218.43] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTQyMTcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21108 invoked from network); 4 Aug 2014 18:52:50 -0000 Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Aug 2014 18:52:50 -0000 Received: by mail-oi0-f43.google.com with SMTP id u20so4860403oif.16 for ; Mon, 04 Aug 2014 11:52: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 :content-type; bh=bWPJ0LuNUoU0KKg4yupbsyiD23v0hUFhJ/3A70hqVOE=; b=W5jguK/UJZM7nbza+Zk/O5gQb1QM1YqL5J9WYqgl95NVJZGkwaALwHDKnL1KAdbijK JHKSn7EQj+m5FXQb91K762lCcHDUIdOGotskeTUONJIj/SI2vjTV7roqCcU3/Dl/Zpfn 2DNxow/xhawbGskuITU23VfENY5L1ACfTqeGOZomKyiPXQOEJKuyN2QoBMssz4012Jxd ZtNdORcnYki/20PFwMry06yO9axnndwAv7wjyFlGUU3rlP0ChJrIAh6/N+fq5K4zo5VD +71/+m/SfADXANySE/Noh5O13JghCjjzJLnbgR3rtD5Sx0j6mBnAATwprms/Q96GKMs1 CY1w== MIME-Version: 1.0 X-Received: by 10.182.29.234 with SMTP id n10mr35436079obh.67.1407178368313; Mon, 04 Aug 2014 11:52:48 -0700 (PDT) Received: by 10.202.197.146 with HTTP; Mon, 4 Aug 2014 11:52:48 -0700 (PDT) In-Reply-To: References: <53C81D1E.4020102@mehnert.org> Date: Mon, 4 Aug 2014 11:52:48 -0700 Message-ID: From: Jyotsna Prakash To: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0115211025517060884==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0115211025517060884== Content-Type: multipart/alternative; boundary=001a11c2bbe8c76f2504ffd23eb7 --001a11c2bbe8c76f2504ffd23eb7 Content-Type: text/plain; charset=UTF-8 Sorry, half my sentence disappeared! - There is something wrong with the method I am using to turn xen kernels into images. The script, which I originally obtained from the mirage docs ( http://openmirage.org/docs/xen-boot), was working earlier this summer. I may have accidentally deleted the line that generates an initrd. The original script is, linked from the mirage docs, is missing. On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash wrote: > Hello, > > I've written a blog post > about > the EC2 image bundling process, and what I have left to do. The short of it > is: > > - There is something wrong with the method I am using to turn xen kernels > into images. The script, which I originally obtained from the mirage docs ( > http://openmirage.org/docs/xen-boot), was working earlier this summer. I > may have accidentally deleted the line that generates an initrd. The > original script > > - I am running shell command with OCaml's `Unix.open_process_in`. I need > to figure out why the command is not giving consistent results... about 1 > out of 10 times it will produce the correct digest. (A SHA1 digest of the > input image after it is compressed and encrypted.) > The shell command is > openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h -S > --owner 0 --group 0 -C /tmp mymirage.img | tee > /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e > -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv > bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc > > And Hannes, thanks for your help! I was able to use nocrypto and > ocaml-x509 to extract RSA keys and encrypt. I will look into replacing > cryptokit with ocaml-sha. > > Best, > Jyotsna > > > On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA384 >> >> Hi Jyotsna, >> >> On 07/17/2014 19:48, Jyotsna Prakash wrote: >> > For my GSoC project I've been working on OCaml bindings to the EC2 >> > API. The code is at https://github.com/moonlightdrive/ocaml-ec2 >> >> Awesome! >> >> > I've yet to launch a Mirage-backed VM without using the Amazon's >> > CLI tools. The process involves producing an xml manifest >> > describing an image; the manifest contains fields of RSA encrypted >> > data. Problem is, I don't have any way to take my public keys (pem >> > files) and turn them into `Cryptokit.RSA.key`s. >> >> AFAICS you're only using SHA256 from Cryptokit so far -- you might >> want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that. >> >> Also, David wrote ocaml-nocrypto >> (https://github.com/mirleft/ocaml-nocrypto) and we further developed >> ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can >> parse pem to get a certificate >> (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) >> or a private key (RSA) >> https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 >> (example usage: >> https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) >> >> What do you need to do with the RSA key? The nocrypto API is at >> https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli >> >> >> Cheers, >> >> Hannes >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.22 (FreeBSD) >> >> iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI >> JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ >> xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM >> eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU >> 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d >> PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW >> Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k >> pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG >> AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p >> XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s >> 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz >> pgdhpVDaP3Ocu+kRpFEB >> =zzgd >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > --001a11c2bbe8c76f2504ffd23eb7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sorry, half my sentence disappeared!
- There is so= mething wrong with the method I am using to turn xen kernels into images. T= he script, which I originally obtained from the mirage docs (http://openmirage.org/docs/xen-boot),= was working earlier this summer. I may have accidentally deleted the line = that generates an initrd. The original script is, linked from the mirage do= cs, is missing.


O= n Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash <jyotsna.prakash@g= mail.com> wrote:
Hello,

I've writ= ten a blog post about the EC2 image bundling process= , and what I have left to do. The short of it is:

- There is something wrong with the method I am using to turn xen kerne= ls into images. The script, which I originally obtained from the mirage doc= s (http:/= /openmirage.org/docs/xen-boot), was working earlier this summer. I may = have accidentally deleted the line that generates an initrd. The original s= cript

- I am running shell command with OCaml's `Unix.open_process_i= n`. I need to figure out why the command is not giving consistent results..= . about 1 out of 10 times it will produce the correct digest. (A SHA1 diges= t of the input image after it is compressed and encrypted.)
The shell command is
=C2=A0 openssl sha1 < /tmp/ec2-bundle-image-dige= st-pipe-10174 & tar -c -h -S --owner 0 --group 0 -C /tmp mymirage.img |= tee /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e -ae= s-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv bbbbbbbbbbbbbbbbbbbbbbbbb= bbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc

And Hannes, thanks for your help! I was able to use nocrypto= and ocaml-x509 to extract RSA keys and encrypt. I will look into replacing= cryptokit with ocaml-sha.

Best,
Jyotsna


On Thu, Jul 17, 2014 at 11:59 AM, Ha= nnes Mehnert <hannes@mehnert.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 19:48, Jyotsna Prakash wrote:
> For my GSoC project I've been working on OCaml bindings to the EC2=
> API. The code is at https://github.com/moonlightdrive/ocaml-ec2

Awesome!

> I've yet to launch a Mirage-backed VM without using the Amazon'= ;s
> CLI tools. The process involves producing an xml manifest
> describing an image; the manifest contains fields of RSA encrypted
> data. Problem is, I don't have any way to take my public keys (pem=
> files) and turn them into `Cryptokit.RSA.key`s.

AFAICS you're only using SHA256 from Cryptokit so far -- you migh= t
want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that.

Also, David wrote ocaml-nocrypto
(ht= tps://github.com/mirleft/ocaml-nocrypto) and we further developed
ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can
parse pem to get a certificate
(https://github.com/mirleft/ocaml-x509/blob/master/li= b/x509.mli#L18)
or a private key (RSA)
https://github.com/mirleft/ocaml-x509/blob/master/lib= /x509.mli#L30
(example usage:
https://github.com/mirleft/ocaml-tls/blob/master/lw= t/x509_lwt.ml#L49)

What do you need to do with the RSA key? The nocrypto API is at
https://github.com/mirleft/ocaml-nocrypto/blob/master/= src/rsa.mli


Cheers,

Hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM
eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU
7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d
PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END PGP SIGNATURE-----

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


--001a11c2bbe8c76f2504ffd23eb7-- --===============0115211025517060884== 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 --===============0115211025517060884==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 18:53:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 18:53: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 1XENNa-0004VA-A0; Mon, 04 Aug 2014 18:53:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XENNZ-0004V3-Gn for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 18:53:05 +0000 Received: from [193.109.254.147:46582] by server-15.bemta-14.messagelabs.com id 52/E2-30948-096DFD35; Mon, 04 Aug 2014 18:53:04 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-14.tower-27.messagelabs.com!1407178369!13678209!1 X-Originating-IP: [209.85.218.43] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_8, RCVD_BY_IP, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTQyMTcgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21108 invoked from network); 4 Aug 2014 18:52:50 -0000 Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by server-14.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 4 Aug 2014 18:52:50 -0000 Received: by mail-oi0-f43.google.com with SMTP id u20so4860403oif.16 for ; Mon, 04 Aug 2014 11:52: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 :content-type; bh=bWPJ0LuNUoU0KKg4yupbsyiD23v0hUFhJ/3A70hqVOE=; b=W5jguK/UJZM7nbza+Zk/O5gQb1QM1YqL5J9WYqgl95NVJZGkwaALwHDKnL1KAdbijK JHKSn7EQj+m5FXQb91K762lCcHDUIdOGotskeTUONJIj/SI2vjTV7roqCcU3/Dl/Zpfn 2DNxow/xhawbGskuITU23VfENY5L1ACfTqeGOZomKyiPXQOEJKuyN2QoBMssz4012Jxd ZtNdORcnYki/20PFwMry06yO9axnndwAv7wjyFlGUU3rlP0ChJrIAh6/N+fq5K4zo5VD +71/+m/SfADXANySE/Noh5O13JghCjjzJLnbgR3rtD5Sx0j6mBnAATwprms/Q96GKMs1 CY1w== MIME-Version: 1.0 X-Received: by 10.182.29.234 with SMTP id n10mr35436079obh.67.1407178368313; Mon, 04 Aug 2014 11:52:48 -0700 (PDT) Received: by 10.202.197.146 with HTTP; Mon, 4 Aug 2014 11:52:48 -0700 (PDT) In-Reply-To: References: <53C81D1E.4020102@mehnert.org> Date: Mon, 4 Aug 2014 11:52:48 -0700 Message-ID: From: Jyotsna Prakash To: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0115211025517060884==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0115211025517060884== Content-Type: multipart/alternative; boundary=001a11c2bbe8c76f2504ffd23eb7 --001a11c2bbe8c76f2504ffd23eb7 Content-Type: text/plain; charset=UTF-8 Sorry, half my sentence disappeared! - There is something wrong with the method I am using to turn xen kernels into images. The script, which I originally obtained from the mirage docs ( http://openmirage.org/docs/xen-boot), was working earlier this summer. I may have accidentally deleted the line that generates an initrd. The original script is, linked from the mirage docs, is missing. On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash wrote: > Hello, > > I've written a blog post > about > the EC2 image bundling process, and what I have left to do. The short of it > is: > > - There is something wrong with the method I am using to turn xen kernels > into images. The script, which I originally obtained from the mirage docs ( > http://openmirage.org/docs/xen-boot), was working earlier this summer. I > may have accidentally deleted the line that generates an initrd. The > original script > > - I am running shell command with OCaml's `Unix.open_process_in`. I need > to figure out why the command is not giving consistent results... about 1 > out of 10 times it will produce the correct digest. (A SHA1 digest of the > input image after it is compressed and encrypted.) > The shell command is > openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h -S > --owner 0 --group 0 -C /tmp mymirage.img | tee > /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e > -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv > bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc > > And Hannes, thanks for your help! I was able to use nocrypto and > ocaml-x509 to extract RSA keys and encrypt. I will look into replacing > cryptokit with ocaml-sha. > > Best, > Jyotsna > > > On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA384 >> >> Hi Jyotsna, >> >> On 07/17/2014 19:48, Jyotsna Prakash wrote: >> > For my GSoC project I've been working on OCaml bindings to the EC2 >> > API. The code is at https://github.com/moonlightdrive/ocaml-ec2 >> >> Awesome! >> >> > I've yet to launch a Mirage-backed VM without using the Amazon's >> > CLI tools. The process involves producing an xml manifest >> > describing an image; the manifest contains fields of RSA encrypted >> > data. Problem is, I don't have any way to take my public keys (pem >> > files) and turn them into `Cryptokit.RSA.key`s. >> >> AFAICS you're only using SHA256 from Cryptokit so far -- you might >> want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that. >> >> Also, David wrote ocaml-nocrypto >> (https://github.com/mirleft/ocaml-nocrypto) and we further developed >> ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can >> parse pem to get a certificate >> (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) >> or a private key (RSA) >> https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 >> (example usage: >> https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) >> >> What do you need to do with the RSA key? The nocrypto API is at >> https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli >> >> >> Cheers, >> >> Hannes >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.22 (FreeBSD) >> >> iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI >> JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ >> xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM >> eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU >> 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d >> PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW >> Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k >> pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG >> AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p >> XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s >> 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz >> pgdhpVDaP3Ocu+kRpFEB >> =zzgd >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > --001a11c2bbe8c76f2504ffd23eb7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Sorry, half my sentence disappeared!
- There is so= mething wrong with the method I am using to turn xen kernels into images. T= he script, which I originally obtained from the mirage docs (http://openmirage.org/docs/xen-boot),= was working earlier this summer. I may have accidentally deleted the line = that generates an initrd. The original script is, linked from the mirage do= cs, is missing.


O= n Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash <jyotsna.prakash@g= mail.com> wrote:
Hello,

I've writ= ten a blog post about the EC2 image bundling process= , and what I have left to do. The short of it is:

- There is something wrong with the method I am using to turn xen kerne= ls into images. The script, which I originally obtained from the mirage doc= s (http:/= /openmirage.org/docs/xen-boot), was working earlier this summer. I may = have accidentally deleted the line that generates an initrd. The original s= cript

- I am running shell command with OCaml's `Unix.open_process_i= n`. I need to figure out why the command is not giving consistent results..= . about 1 out of 10 times it will produce the correct digest. (A SHA1 diges= t of the input image after it is compressed and encrypted.)
The shell command is
=C2=A0 openssl sha1 < /tmp/ec2-bundle-image-dige= st-pipe-10174 & tar -c -h -S --owner 0 --group 0 -C /tmp mymirage.img |= tee /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e -ae= s-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv bbbbbbbbbbbbbbbbbbbbbbbbb= bbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc

And Hannes, thanks for your help! I was able to use nocrypto= and ocaml-x509 to extract RSA keys and encrypt. I will look into replacing= cryptokit with ocaml-sha.

Best,
Jyotsna


On Thu, Jul 17, 2014 at 11:59 AM, Ha= nnes Mehnert <hannes@mehnert.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 19:48, Jyotsna Prakash wrote:
> For my GSoC project I've been working on OCaml bindings to the EC2=
> API. The code is at https://github.com/moonlightdrive/ocaml-ec2

Awesome!

> I've yet to launch a Mirage-backed VM without using the Amazon'= ;s
> CLI tools. The process involves producing an xml manifest
> describing an image; the manifest contains fields of RSA encrypted
> data. Problem is, I don't have any way to take my public keys (pem=
> files) and turn them into `Cryptokit.RSA.key`s.

AFAICS you're only using SHA256 from Cryptokit so far -- you migh= t
want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that.

Also, David wrote ocaml-nocrypto
(ht= tps://github.com/mirleft/ocaml-nocrypto) and we further developed
ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can
parse pem to get a certificate
(https://github.com/mirleft/ocaml-x509/blob/master/li= b/x509.mli#L18)
or a private key (RSA)
https://github.com/mirleft/ocaml-x509/blob/master/lib= /x509.mli#L30
(example usage:
https://github.com/mirleft/ocaml-tls/blob/master/lw= t/x509_lwt.ml#L49)

What do you need to do with the RSA key? The nocrypto API is at
https://github.com/mirleft/ocaml-nocrypto/blob/master/= src/rsa.mli


Cheers,

Hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM
eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU
7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d
PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END PGP SIGNATURE-----

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


--001a11c2bbe8c76f2504ffd23eb7-- --===============0115211025517060884== 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 --===============0115211025517060884==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 21:58:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 21:58:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEQHB-0007Dm-Ay; Mon, 04 Aug 2014 21:58:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEQH9-0007Dh-Nr for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 21:58:39 +0000 Received: from [193.109.254.147:17858] by server-8.bemta-14.messagelabs.com id 5A/3F-07074-E0200E35; Mon, 04 Aug 2014 21:58:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1407189516!13657528!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 25721 invoked from network); 4 Aug 2014 21:58:36 -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; 4 Aug 2014 21:58:36 -0000 Received: (qmail 18430 invoked by uid 634); 4 Aug 2014 21:58:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 04 Aug 2014 22:58:32 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> Date: Mon, 4 Aug 2014 22:58:30 +0100 Message-Id: <973F6395-6B7A-4CC9-8780-F9094CCCAE2F@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> To: Gilles DALMAS 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 os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0171696391066578902==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0171696391066578902== Content-Type: multipart/alternative; boundary="Apple-Mail=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04" --Apple-Mail=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 There are several forks of the Linux kernel, and this one is probably = the Linux-Sunxi branch that adds support into a branch. Our = xen-arm-builder script is now using the upstream Linux kernel that has = several (but not all) of the Sunxi-specific functionality integrated = into it. =20 See http://linux-sunxi.org/Linux_mainlining_effort for more information = on this. -anil On 4 Aug 2014, at 14:53, Gilles DALMAS wrote: > In terms of the nand, on page: = https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kerne= l.config.3.4.61 there is for example the line = CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the = kernel, how is it that this option does not appear in the following = versions of the kernel? if I add it manually in the config file, is it = processed? >=20 >=20 >=20 >=20 >=20 > > Message du 04/08/14 15:03 > > De : "Gilles DALMAS" > > A : "Thomas Leonard" , "Anil Madhavapeddy" = > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > > > apparently, the xen-arm-builder script solves the problem of = slowness. even without installing mirage-net-xen. >=20 >=20 >=20 >=20 >=20 > > Message du 04/08/14 13:28 > > De : "Thomas Leonard" > > A : "Anil Madhavapeddy" > > Copie =E0 : "Gilles DALMAS" , = "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 3 August 2014 17:24, Thomas Leonard wrote: > > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > > >> On 3 Aug 2014, at 16:34, Gilles DALMAS = wrote: > > >> > > >> hi, > > >> > > >> I recently compiled mirage for cubietruck. > > >> > > >> Everything works fine, but the system is extremely slow. > > >> > > >> Hi Gilles, > > >> > > >> Glad to hear you've got it up and running. Could you shed some = light about > > >> the nature of the application that is slow? > > >> > > >> If it's networking, there's a known bug at the moment [1] due to = a > > >> limitation on Xen 4.4/ARM that prevents multiple mapping of = pages. Thomas > > >> Leonard has just applied a backport to the SDCard image builder = [2] that > > >> fixes this issue in Xen itself, so we could remove the workaround = now and > > >> hopefully get back to decent networking performance (is this = correct, > > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > > > Yes, I'll rebuild the binary images at some point but for now you = can > > > build from Git. With that, you can revert back to the older > > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. > >=20 > > Here are the new images: > >=20 > > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 > >=20 > > Installation instructions are here: > >=20 > > https://github.com/mirage/xen-arm-builder > >=20 > > Remember to use mirage-net-xen v1.1.1 as well, or it will still be = slow: > >=20 > > opam pin mirage-net-xen = https://github.com/mirage/mirage-net-xen.git#v1.1.1 > >=20 > >=20 > > --=20 > > 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 > > >=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=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 There = are several forks of the Linux kernel, and this one is probably the = Linux-Sunxi branch that adds support into a branch.  Our = xen-arm-builder script is now using the upstream Linux kernel that has = several (but not all) of the Sunxi-specific functionality integrated = into it.  

See http://linux-sunxi= .org/Linux_mainlining_effort for more information on = this.

-anil

On 4 Aug = 2014, at 14:53, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruck-Debian= /blob/master/config/kernel.config.3.4.61 there is for example the = line CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of = the kernel, how is it that this option does not appear in the following = versions of the kernel? if I add it manually in the config file, is it = processed?




> Message du 04/08/14 15:03
> De : "Gilles = DALMAS" <gdalmas@wanadoo.fr>
> A = : "Thomas Leonard" <talex5@gmail.com>, "Anil = Madhavapeddy" <anil@recoil.org>
> Copie =E0 = : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] mirage os on = cubietruck nand detection
>
>

> apparently, the xen-arm-builder script solves the problem of = slowness. even without installing mirage-net-xen.


=

> Message du 04/08/14 13:28
> De : "Thomas = Leonard" <talex5@gmail.com>
> A : = "Anil Madhavapeddy" <anil@recoil.org>
> Copie =E0 = : "Gilles DALMAS" <gdalmas@wanadoo.fr>, "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] mirage os on = cubietruck nand detection
>
> On 3 August 2014 17:24, = Thomas Leonard <talex5@gmail.com> wrote:
> = > On 3 August 2014 17:20, Anil Madhavapeddy <anil@recoil.org> wrote:
> = >> On 3 Aug 2014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> >>
> >> hi,
> >>
> = >> I recently compiled mirage for cubietruck.
> = >>
> >> Everything works fine, but the system is = extremely slow.
> >>
> >> Hi Gilles,
> = >>
> >> Glad to hear you've got it up and running. = Could you shed some light about
> >> the nature of the = application that is slow?
> >>
> >> If it's = networking, there's a known bug at the moment [1] due to a
> = >> limitation on Xen 4.4/ARM that prevents multiple mapping of = pages. Thomas
> >> Leonard has just applied a backport to = the SDCard image builder [2] that
> >> fixes this issue in = Xen itself, so we could remove the workaround now and
> >> = hopefully get back to decent networking performance (is this = correct,
> >> Thomas? I haven't had a chance to rebuild my = own Cubie2 yet).
> >
> > Yes, I'll rebuild the binary = images at some point but for now you can
> > build from Git. = With that, you can revert back to the older
> > mirage-net-xen = v1.1.1 to avoid the wait after sending each packet.
>
> = Here are the new images:
>
> http://bl= obs.openmirage.org/cubieboard2-xen-iso.tar.bz2
> http://blo= bs.openmirage.org/cubietruck-xen-iso.tar.bz2
>
> = Installation instructions are here:
>
> https://github.com/mira= ge/xen-arm-builder
>
> Remember to use mirage-net-xen = v1.1.1 as well, or it will still be slow:
>
> opam pin = mirage-net-xen https://githu= b.com/mirage/mirage-net-xen.git#v1.1.1
>
>
> -- =
> 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.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

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

= --Apple-Mail=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04-- --===============0171696391066578902== 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 --===============0171696391066578902==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 04 21:58:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 04 Aug 2014 21:58:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEQHB-0007Dm-Ay; Mon, 04 Aug 2014 21:58:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEQH9-0007Dh-Nr for mirageos-devel@lists.xenproject.org; Mon, 04 Aug 2014 21:58:39 +0000 Received: from [193.109.254.147:17858] by server-8.bemta-14.messagelabs.com id 5A/3F-07074-E0200E35; Mon, 04 Aug 2014 21:58:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1407189516!13657528!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 25721 invoked from network); 4 Aug 2014 21:58:36 -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; 4 Aug 2014 21:58:36 -0000 Received: (qmail 18430 invoked by uid 634); 4 Aug 2014 21:58:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 04 Aug 2014 22:58:32 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> Date: Mon, 4 Aug 2014 22:58:30 +0100 Message-Id: <973F6395-6B7A-4CC9-8780-F9094CCCAE2F@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> To: Gilles DALMAS 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 os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============0171696391066578902==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0171696391066578902== Content-Type: multipart/alternative; boundary="Apple-Mail=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04" --Apple-Mail=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 There are several forks of the Linux kernel, and this one is probably = the Linux-Sunxi branch that adds support into a branch. Our = xen-arm-builder script is now using the upstream Linux kernel that has = several (but not all) of the Sunxi-specific functionality integrated = into it. =20 See http://linux-sunxi.org/Linux_mainlining_effort for more information = on this. -anil On 4 Aug 2014, at 14:53, Gilles DALMAS wrote: > In terms of the nand, on page: = https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kerne= l.config.3.4.61 there is for example the line = CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the = kernel, how is it that this option does not appear in the following = versions of the kernel? if I add it manually in the config file, is it = processed? >=20 >=20 >=20 >=20 >=20 > > Message du 04/08/14 15:03 > > De : "Gilles DALMAS" > > A : "Thomas Leonard" , "Anil Madhavapeddy" = > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > > > apparently, the xen-arm-builder script solves the problem of = slowness. even without installing mirage-net-xen. >=20 >=20 >=20 >=20 >=20 > > Message du 04/08/14 13:28 > > De : "Thomas Leonard" > > A : "Anil Madhavapeddy" > > Copie =E0 : "Gilles DALMAS" , = "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 3 August 2014 17:24, Thomas Leonard wrote: > > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > > >> On 3 Aug 2014, at 16:34, Gilles DALMAS = wrote: > > >> > > >> hi, > > >> > > >> I recently compiled mirage for cubietruck. > > >> > > >> Everything works fine, but the system is extremely slow. > > >> > > >> Hi Gilles, > > >> > > >> Glad to hear you've got it up and running. Could you shed some = light about > > >> the nature of the application that is slow? > > >> > > >> If it's networking, there's a known bug at the moment [1] due to = a > > >> limitation on Xen 4.4/ARM that prevents multiple mapping of = pages. Thomas > > >> Leonard has just applied a backport to the SDCard image builder = [2] that > > >> fixes this issue in Xen itself, so we could remove the workaround = now and > > >> hopefully get back to decent networking performance (is this = correct, > > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > > > Yes, I'll rebuild the binary images at some point but for now you = can > > > build from Git. With that, you can revert back to the older > > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. > >=20 > > Here are the new images: > >=20 > > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 > >=20 > > Installation instructions are here: > >=20 > > https://github.com/mirage/xen-arm-builder > >=20 > > Remember to use mirage-net-xen v1.1.1 as well, or it will still be = slow: > >=20 > > opam pin mirage-net-xen = https://github.com/mirage/mirage-net-xen.git#v1.1.1 > >=20 > >=20 > > --=20 > > 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 > > >=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=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 There = are several forks of the Linux kernel, and this one is probably the = Linux-Sunxi branch that adds support into a branch.  Our = xen-arm-builder script is now using the upstream Linux kernel that has = several (but not all) of the Sunxi-specific functionality integrated = into it.  

See http://linux-sunxi= .org/Linux_mainlining_effort for more information on = this.

-anil

On 4 Aug = 2014, at 14:53, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruck-Debian= /blob/master/config/kernel.config.3.4.61 there is for example the = line CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of = the kernel, how is it that this option does not appear in the following = versions of the kernel? if I add it manually in the config file, is it = processed?




> Message du 04/08/14 15:03
> De : "Gilles = DALMAS" <gdalmas@wanadoo.fr>
> A = : "Thomas Leonard" <talex5@gmail.com>, "Anil = Madhavapeddy" <anil@recoil.org>
> Copie =E0 = : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] mirage os on = cubietruck nand detection
>
>

> apparently, the xen-arm-builder script solves the problem of = slowness. even without installing mirage-net-xen.


=

> Message du 04/08/14 13:28
> De : "Thomas = Leonard" <talex5@gmail.com>
> A : = "Anil Madhavapeddy" <anil@recoil.org>
> Copie =E0 = : "Gilles DALMAS" <gdalmas@wanadoo.fr>, "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] mirage os on = cubietruck nand detection
>
> On 3 August 2014 17:24, = Thomas Leonard <talex5@gmail.com> wrote:
> = > On 3 August 2014 17:20, Anil Madhavapeddy <anil@recoil.org> wrote:
> = >> On 3 Aug 2014, at 16:34, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> >>
> >> hi,
> >>
> = >> I recently compiled mirage for cubietruck.
> = >>
> >> Everything works fine, but the system is = extremely slow.
> >>
> >> Hi Gilles,
> = >>
> >> Glad to hear you've got it up and running. = Could you shed some light about
> >> the nature of the = application that is slow?
> >>
> >> If it's = networking, there's a known bug at the moment [1] due to a
> = >> limitation on Xen 4.4/ARM that prevents multiple mapping of = pages. Thomas
> >> Leonard has just applied a backport to = the SDCard image builder [2] that
> >> fixes this issue in = Xen itself, so we could remove the workaround now and
> >> = hopefully get back to decent networking performance (is this = correct,
> >> Thomas? I haven't had a chance to rebuild my = own Cubie2 yet).
> >
> > Yes, I'll rebuild the binary = images at some point but for now you can
> > build from Git. = With that, you can revert back to the older
> > mirage-net-xen = v1.1.1 to avoid the wait after sending each packet.
>
> = Here are the new images:
>
> http://bl= obs.openmirage.org/cubieboard2-xen-iso.tar.bz2
> http://blo= bs.openmirage.org/cubietruck-xen-iso.tar.bz2
>
> = Installation instructions are here:
>
> https://github.com/mira= ge/xen-arm-builder
>
> Remember to use mirage-net-xen = v1.1.1 as well, or it will still be slow:
>
> opam pin = mirage-net-xen https://githu= b.com/mirage/mirage-net-xen.git#v1.1.1
>
>
> -- =
> 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.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

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

= --Apple-Mail=_7A3E0DA7-D35A-4954-9AE2-75AABDAB5F04-- --===============0171696391066578902== 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 --===============0171696391066578902==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 07:44:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 07:44: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 1XEZPp-00030t-Pn; Tue, 05 Aug 2014 07:44:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEZPo-00030n-8z for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 07:44:12 +0000 Received: from [85.158.143.35:52292] by server-3.bemta-4.messagelabs.com id 7C/BD-06192-B4B80E35; Tue, 05 Aug 2014 07:44:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1407224650!13500546!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21822 invoked from network); 5 Aug 2014 07:44:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 5 Aug 2014 07:44:10 -0000 Received: (qmail 8227 invoked by uid 634); 5 Aug 2014 07:44:10 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from dab-far1-h-83-10.dab.02.net (HELO [10.4.196.112]) (82.132.223.248) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 05 Aug 2014 08:44:09 +0100 References: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> Mime-Version: 1.0 (1.0) In-Reply-To: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> Message-Id: <7627A3FE-8878-41AD-9BAF-DD5FBC31ABDE@recoil.org> X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Tue, 5 Aug 2014 08:43:59 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xpenology dsm domu 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="===============7956640088614514103==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7956640088614514103== Content-Type: multipart/alternative; boundary=Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89 Content-Transfer-Encoding: 7bit --Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable This might be more usefully sent to the xen-users list where many appliances= like this are discussed. I'm not sure what your question is here: is someth= ing not working? -anil > On 4 Aug 2014, at 14:40, Gilles DALMAS wrote: >=20 > Hi, >=20 > I try to install the dsm of xpenology on xen but I do not control all the c= onfiguration xen command line. Is someone could help me to transcribe it: >=20 > =20 >=20 > - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB R= AM > - Using HVM (Other install media, during Xen VM creation). > - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3D= false` (Makes sure virt-what coretly recognizes Xen) > - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/= sda1` (Using Debian Live distro) > - Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` added `= vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6` > - DSM 5.0 4458 installed after booting with grub menu item gnoboot.me =E2=80= =93> install/upgrade/downgrade 4458 >=20 > =20 >=20 > in command line ? >=20 > =20 >=20 > at least for the introduction of the working environment. (Disc creation, .= conf parameter file) >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
This might be more usefully sent to th= e xen-users list where many appliances like this are discussed. I'm not sure= what your question is here: is something not working?

<= div>-anil

On 4 Aug 2014, at 14:40, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

<= blockquote type=3D"cite">

Hi,

I try to install the dsm of xpenology on xen but I do not control all the= configuration xen command line. Is someone could help me to transcribe it:<= /p>

 

- Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB= RAM
- Using HVM (Other install media, during Xen VM creation).
- Disa= bled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3Dfalse` (= Makes sure virt-what coretly recognizes Xen)
- gnoBoot image installed us= ing `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/sda1` (Using Debian Live distr= o)
- Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` ad= ded `vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6`
- DSM 5.0 4458 installed afte= r booting with grub menu item gnoboot.me =E2= =80=93> install/upgrade/downgrade 4458

 

 in command line ?

 

at least for the introduction of the working environment. (Disc creation,= .conf parameter file)

= _______________________________________________
Mirage= OS-devel mailing list
MirageOS-devel@lists.xenproject.org
= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
= --Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89-- --===============7956640088614514103== 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 --===============7956640088614514103==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 07:44:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 07:44: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 1XEZPp-00030t-Pn; Tue, 05 Aug 2014 07:44:13 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEZPo-00030n-8z for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 07:44:12 +0000 Received: from [85.158.143.35:52292] by server-3.bemta-4.messagelabs.com id 7C/BD-06192-B4B80E35; Tue, 05 Aug 2014 07:44:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1407224650!13500546!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21822 invoked from network); 5 Aug 2014 07:44:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 5 Aug 2014 07:44:10 -0000 Received: (qmail 8227 invoked by uid 634); 5 Aug 2014 07:44:10 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from dab-far1-h-83-10.dab.02.net (HELO [10.4.196.112]) (82.132.223.248) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 05 Aug 2014 08:44:09 +0100 References: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> Mime-Version: 1.0 (1.0) In-Reply-To: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> Message-Id: <7627A3FE-8878-41AD-9BAF-DD5FBC31ABDE@recoil.org> X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Tue, 5 Aug 2014 08:43:59 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xpenology dsm domu 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="===============7956640088614514103==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7956640088614514103== Content-Type: multipart/alternative; boundary=Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89 Content-Transfer-Encoding: 7bit --Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable This might be more usefully sent to the xen-users list where many appliances= like this are discussed. I'm not sure what your question is here: is someth= ing not working? -anil > On 4 Aug 2014, at 14:40, Gilles DALMAS wrote: >=20 > Hi, >=20 > I try to install the dsm of xpenology on xen but I do not control all the c= onfiguration xen command line. Is someone could help me to transcribe it: >=20 > =20 >=20 > - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB R= AM > - Using HVM (Other install media, during Xen VM creation). > - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3D= false` (Makes sure virt-what coretly recognizes Xen) > - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/= sda1` (Using Debian Live distro) > - Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` added `= vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6` > - DSM 5.0 4458 installed after booting with grub menu item gnoboot.me =E2=80= =93> install/upgrade/downgrade 4458 >=20 > =20 >=20 > in command line ? >=20 > =20 >=20 > at least for the introduction of the working environment. (Disc creation, .= conf parameter file) >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
This might be more usefully sent to th= e xen-users list where many appliances like this are discussed. I'm not sure= what your question is here: is something not working?

<= div>-anil

On 4 Aug 2014, at 14:40, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

<= blockquote type=3D"cite">

Hi,

I try to install the dsm of xpenology on xen but I do not control all the= configuration xen command line. Is someone could help me to transcribe it:<= /p>

 

- Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB= RAM
- Using HVM (Other install media, during Xen VM creation).
- Disa= bled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian=3Dfalse` (= Makes sure virt-what coretly recognizes Xen)
- gnoBoot image installed us= ing `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev/sda1` (Using Debian Live distr= o)
- Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` ad= ded `vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6`
- DSM 5.0 4458 installed afte= r booting with grub menu item gnoboot.me =E2= =80=93> install/upgrade/downgrade 4458

 

 in command line ?

 

at least for the introduction of the working environment. (Disc creation,= .conf parameter file)

= _______________________________________________
Mirage= OS-devel mailing list
MirageOS-devel@lists.xenproject.org
= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
= --Apple-Mail-A43E86F5-1529-498C-B179-D0351CE85E89-- --===============7956640088614514103== 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 --===============7956640088614514103==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 08:32:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 08:32: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 1XEaAN-0004ju-OT; Tue, 05 Aug 2014 08:32:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEaAM-0004jo-Ny for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 08:32:18 +0000 Received: from [85.158.143.35:35654] by server-2.bemta-4.messagelabs.com id 8E/65-04525-19690E35; Tue, 05 Aug 2014 08:32:17 +0000 X-Env-Sender: vb@luminar.eu.org X-Msg-Ref: server-10.tower-21.messagelabs.com!1407227527!13512984!1 X-Originating-IP: [94.23.24.152] 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 8509 invoked from network); 5 Aug 2014 08:32:17 -0000 Received: from luminar.eu.org (HELO luminar.eu.org) (94.23.24.152) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Aug 2014 08:32:17 -0000 Received: from [IPv6:2001:41d0:fc9c:c500:48e8:d311:dad1:73fd] (unknown [IPv6:2001:41d0:fc9c:c500:48e8:d311:dad1:73fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by luminar.eu.org (Postfix) with ESMTPSA id 38C9360375 for ; Tue, 5 Aug 2014 10:32:06 +0200 (CEST) Message-ID: <53E09685.7030304@luminar.eu.org> Date: Tue, 05 Aug 2014 10:32:05 +0200 From: "Vincent B." 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: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> In-Reply-To: <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> X-Enigmail-Version: 1.6 Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04/08/2014 15:53, Gilles DALMAS wrote: > In terms of the nand, on page: > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kernel.config.3.4.61 > there is for example the line CONFIG_SUNXI_NAND_PARTITION = y and this is the > 3.4.61 version of the kernel, how is it that this option does not appear in the > following versions of the kernel? if I add it manually in the config file, is it > processed? > There is no sunxi NAND support yet for the mainline linux Kernel. Work is ongoing, though. Vincent _______________________________________________ MirageOS-devel 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 Aug 05 08:32:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 08:32: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 1XEaAN-0004ju-OT; Tue, 05 Aug 2014 08:32:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEaAM-0004jo-Ny for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 08:32:18 +0000 Received: from [85.158.143.35:35654] by server-2.bemta-4.messagelabs.com id 8E/65-04525-19690E35; Tue, 05 Aug 2014 08:32:17 +0000 X-Env-Sender: vb@luminar.eu.org X-Msg-Ref: server-10.tower-21.messagelabs.com!1407227527!13512984!1 X-Originating-IP: [94.23.24.152] 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 8509 invoked from network); 5 Aug 2014 08:32:17 -0000 Received: from luminar.eu.org (HELO luminar.eu.org) (94.23.24.152) by server-10.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Aug 2014 08:32:17 -0000 Received: from [IPv6:2001:41d0:fc9c:c500:48e8:d311:dad1:73fd] (unknown [IPv6:2001:41d0:fc9c:c500:48e8:d311:dad1:73fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by luminar.eu.org (Postfix) with ESMTPSA id 38C9360375 for ; Tue, 5 Aug 2014 10:32:06 +0200 (CEST) Message-ID: <53E09685.7030304@luminar.eu.org> Date: Tue, 05 Aug 2014 10:32:05 +0200 From: "Vincent B." 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: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> In-Reply-To: <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> X-Enigmail-Version: 1.6 Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 04/08/2014 15:53, Gilles DALMAS wrote: > In terms of the nand, on page: > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kernel.config.3.4.61 > there is for example the line CONFIG_SUNXI_NAND_PARTITION = y and this is the > 3.4.61 version of the kernel, how is it that this option does not appear in the > following versions of the kernel? if I add it manually in the config file, is it > processed? > There is no sunxi NAND support yet for the mainline linux Kernel. Work is ongoing, though. Vincent _______________________________________________ MirageOS-devel 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 Aug 05 09:06:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 09:06: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 1XEah0-00077J-Hl; Tue, 05 Aug 2014 09:06:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEagy-00077E-QZ for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 09:06:01 +0000 Received: from [85.158.139.211:61966] by server-12.bemta-5.messagelabs.com id 36/A2-22251-87E90E35; Tue, 05 Aug 2014 09:06:00 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1407229544!11944510!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_8,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNjI3NzIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5497 invoked from network); 5 Aug 2014 09:05:44 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Aug 2014 09:05:44 -0000 Received: by mail-wg0-f47.google.com with SMTP id b13so654503wgh.30 for ; Tue, 05 Aug 2014 02:05: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 :message-id:references:to; bh=9dwSLOvZlUToHLcOFs/p9N7xYrHnEOKMAlotj76rFWw=; b=tPyg5OP1XDdcC3R6GvWYuwRQnqHggN37p+wwt+aGhgHP2qwEQXHMG1TZmBk3vWbqgC 8VvZXDg9KWxBYtTMH81+dzbyxr7I4wcrVYy1G9Y9pCHGqIra/gAvoKFQkJ2iDtmpi0Ra eNTkb8yKtpDxvDiJ1NFxrp6BPCThhKUEvjbjFcK8XX+mjfYXB2gqN3srMuiOtraPlGYd gEOXMlqYakO8mZYgwryOkJPdXx0yFZaRIzHjnbm0i3xrxsnnYSCBMTlTfifTYraVFtJX 3L5n3ZkZ6usQLvzkFgf+yggiY5quU6+LfSQGoImuF97LOM5Bk6IeN/E+9tF0gIwNwybR /dkQ== X-Received: by 10.180.99.65 with SMTP id eo1mr4880231wib.12.1407229544185; Tue, 05 Aug 2014 02:05:44 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id sa4sm2741061wjb.45.2014.08.05.02.05.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 02:05:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 5 Aug 2014 10:05:38 +0100 Message-Id: <5DB9916D-1757-493B-8B94-FC03C237957D@gazagnaire.org> References: <53C81D1E.4020102@mehnert.org> To: Jyotsna Prakash X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3498545350660590002==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3498545350660590002== Content-Type: multipart/alternative; boundary="Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B" --Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii mirari is deprecated, you should use mirage/mirage So the initial script is there = https://raw.githubusercontent.com/mirage/mirage/master/scripts/ec2.sh On 4 Aug 2014, at 19:52, Jyotsna Prakash = wrote: > Sorry, half my sentence disappeared! > - There is something wrong with the method I am using to turn xen = kernels > into images. The script, which I originally obtained from the mirage = docs ( > http://openmirage.org/docs/xen-boot), was working earlier this summer. = I > may have accidentally deleted the line that generates an initrd. The > original script is, linked from the mirage docs, is missing. >=20 >=20 > On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash = > wrote: >=20 >> Hello, >>=20 >> I've written a blog post >> = about >> the EC2 image bundling process, and what I have left to do. The short = of it >> is: >>=20 >> - There is something wrong with the method I am using to turn xen = kernels >> into images. The script, which I originally obtained from the mirage = docs ( >> http://openmirage.org/docs/xen-boot), was working earlier this = summer. I >> may have accidentally deleted the line that generates an initrd. The >> original script >>=20 >> - I am running shell command with OCaml's `Unix.open_process_in`. I = need >> to figure out why the command is not giving consistent results... = about 1 >> out of 10 times it will produce the correct digest. (A SHA1 digest of = the >> input image after it is compressed and encrypted.) >> The shell command is >> openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h = -S >> --owner 0 --group 0 -C /tmp mymirage.img | tee >> /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e >> -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv >> bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc >>=20 >> And Hannes, thanks for your help! I was able to use nocrypto and >> ocaml-x509 to extract RSA keys and encrypt. I will look into = replacing >> cryptokit with ocaml-sha. >>=20 >> Best, >> Jyotsna >>=20 >>=20 >> On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert >> wrote: >>=20 >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA384 >>>=20 >>> Hi Jyotsna, >>>=20 >>> On 07/17/2014 19:48, Jyotsna Prakash wrote: >>>> For my GSoC project I've been working on OCaml bindings to the EC2 >>>> API. The code is at https://github.com/moonlightdrive/ocaml-ec2 >>>=20 >>> Awesome! >>>=20 >>>> I've yet to launch a Mirage-backed VM without using the Amazon's >>>> CLI tools. The process involves producing an xml manifest >>>> describing an image; the manifest contains fields of RSA encrypted >>>> data. Problem is, I don't have any way to take my public keys (pem >>>> files) and turn them into `Cryptokit.RSA.key`s. >>>=20 >>> AFAICS you're only using SHA256 from Cryptokit so far -- you might >>> want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for = that. >>>=20 >>> Also, David wrote ocaml-nocrypto >>> (https://github.com/mirleft/ocaml-nocrypto) and we further developed >>> ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can >>> parse pem to get a certificate >>> (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) >>> or a private key (RSA) >>> https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 >>> (example usage: >>> = https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) >>>=20 >>> What do you need to do with the RSA key? The nocrypto API is at >>> https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli >>>=20 >>>=20 >>> Cheers, >>>=20 >>> Hannes >>>=20 >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.22 (FreeBSD) >>>=20 >>> iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI >>> JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ >>> xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM >>> eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU >>> 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d >>> PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW >>> Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k >>> pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG >>> AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p >>> XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s >>> 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz >>> pgdhpVDaP3Ocu+kRpFEB >>> =3Dzzgd >>> -----END PGP SIGNATURE----- >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>=20 >>=20 >>=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii mirari = is deprecated, you should use mirage/mirage



On 4 Aug 2014, at 19:52, = Jyotsna Prakash <jyotsna.prakash@gmail.com>= ; wrote:

Sorry, half my sentence disappeared!
- There is = something wrong with the method I am using to turn xen kernels
into = images. The script, which I originally obtained from the mirage docs = (
http://openmirage.org/docs/xe= n-boot), was working earlier this summer. I
may have accidentally = deleted the line that generates an initrd. The
original script is, = linked from the mirage docs, is missing.


On Mon, Aug 4, 2014 = at 11:50 AM, Jyotsna Prakash <jyotsna.prakash@gmail.com>= ;
wrote:

Hello,

I've written = a blog post
<h= ttp://1000hippos.wordpress.com/2014/08/04/ec2-bundling-images/> = about
the EC2 image bundling process, and what I have left to do. The = short of it
is:

- There is something wrong with the method I = am using to turn xen kernels
into images. The script, which I = originally obtained from the mirage docs (
http://openmirage.org/docs/xe= n-boot), was working earlier this summer. I
may have accidentally = deleted the line that generates an initrd. The
original = script

- I am running shell command with OCaml's = `Unix.open_process_in`. I need
to figure out why the command is not = giving consistent results... about 1
out of 10 times it will produce = the correct digest. (A SHA1 digest of the
input image after it is = compressed and encrypted.)
The shell command is
 openssl = sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h = -S
--owner 0 --group 0 -C /tmp mymirage.img | = tee
/tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc = -e
-aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa = -iv
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > = ec2_tmp/mymirage.img.tar.gz.enc

And Hannes, thanks for your help! = I was able to use nocrypto and
ocaml-x509 to extract RSA keys and = encrypt. I will look into replacing
cryptokit with = ocaml-sha.

Best,
Jyotsna


On Thu, Jul 17, 2014 at = 11:59 AM, Hannes Mehnert <hannes@mehnert.org>
wrote:
-----BEGIN PGP SIGNED = MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 = 19:48, Jyotsna Prakash wrote:
For my GSoC = project I've been working on OCaml bindings to the EC2
API. The code = is at https://github.com/mo= onlightdrive/ocaml-ec2

Awesome!

I've yet to launch a Mirage-backed VM without using the = Amazon's
CLI tools. The process involves producing an xml = manifest
describing an image; the manifest contains fields of RSA = encrypted
data. Problem is, I don't have any way to take my public = keys (pem
files) and turn them into = `Cryptokit.RSA.key`s.

AFAICS you're only using = SHA256 from Cryptokit so far -- you might
want to use ocaml-sha (https://github.com/vincent= hz/ocaml-sha) for that.

Also, David wrote = ocaml-nocrypto
(https://github.com/mirl= eft/ocaml-nocrypto) and we further developed
ocaml-x509 (https://github.com/mirleft= /ocaml-x509/) where you can
parse pem to get a certificate
(https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18)<= br>or a private key (RSA)
https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30(example = usage:
https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml= #L49)

What do you need to do with the RSA key? The nocrypto API = is = at
https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli

Cheers,

Hannes

-----BEGIN PGP = SIGNATURE-----
Version: GnuPG v2.0.22 = (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0td= vUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1= /
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM
e= XD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU
7iq6fsN= uLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d
PMSoQQtWTEGrf= GyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw2pZ2tDbOkwDcIH= tb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9ktW996QAPdhKg= ck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCDGao/JGBaG+= 2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLY= UlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKme= bl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END PGP = SIGNATURE-----

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

= --Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B-- --===============3498545350660590002== 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 --===============3498545350660590002==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 09:06:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 09:06: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 1XEah0-00077J-Hl; Tue, 05 Aug 2014 09:06:02 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEagy-00077E-QZ for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 09:06:01 +0000 Received: from [85.158.139.211:61966] by server-12.bemta-5.messagelabs.com id 36/A2-22251-87E90E35; Tue, 05 Aug 2014 09:06:00 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-4.tower-206.messagelabs.com!1407229544!11944510!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_8,spamassassin: ,async_handler: YXN5bmNfZGVsYXk6IDcwNjI3NzIgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5497 invoked from network); 5 Aug 2014 09:05:44 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-4.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 5 Aug 2014 09:05:44 -0000 Received: by mail-wg0-f47.google.com with SMTP id b13so654503wgh.30 for ; Tue, 05 Aug 2014 02:05: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 :message-id:references:to; bh=9dwSLOvZlUToHLcOFs/p9N7xYrHnEOKMAlotj76rFWw=; b=tPyg5OP1XDdcC3R6GvWYuwRQnqHggN37p+wwt+aGhgHP2qwEQXHMG1TZmBk3vWbqgC 8VvZXDg9KWxBYtTMH81+dzbyxr7I4wcrVYy1G9Y9pCHGqIra/gAvoKFQkJ2iDtmpi0Ra eNTkb8yKtpDxvDiJ1NFxrp6BPCThhKUEvjbjFcK8XX+mjfYXB2gqN3srMuiOtraPlGYd gEOXMlqYakO8mZYgwryOkJPdXx0yFZaRIzHjnbm0i3xrxsnnYSCBMTlTfifTYraVFtJX 3L5n3ZkZ6usQLvzkFgf+yggiY5quU6+LfSQGoImuF97LOM5Bk6IeN/E+9tF0gIwNwybR /dkQ== X-Received: by 10.180.99.65 with SMTP id eo1mr4880231wib.12.1407229544185; Tue, 05 Aug 2014 02:05:44 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id sa4sm2741061wjb.45.2014.08.05.02.05.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 02:05:43 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 5 Aug 2014 10:05:38 +0100 Message-Id: <5DB9916D-1757-493B-8B94-FC03C237957D@gazagnaire.org> References: <53C81D1E.4020102@mehnert.org> To: Jyotsna Prakash X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3498545350660590002==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3498545350660590002== Content-Type: multipart/alternative; boundary="Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B" --Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii mirari is deprecated, you should use mirage/mirage So the initial script is there = https://raw.githubusercontent.com/mirage/mirage/master/scripts/ec2.sh On 4 Aug 2014, at 19:52, Jyotsna Prakash = wrote: > Sorry, half my sentence disappeared! > - There is something wrong with the method I am using to turn xen = kernels > into images. The script, which I originally obtained from the mirage = docs ( > http://openmirage.org/docs/xen-boot), was working earlier this summer. = I > may have accidentally deleted the line that generates an initrd. The > original script is, linked from the mirage docs, is missing. >=20 >=20 > On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash = > wrote: >=20 >> Hello, >>=20 >> I've written a blog post >> = about >> the EC2 image bundling process, and what I have left to do. The short = of it >> is: >>=20 >> - There is something wrong with the method I am using to turn xen = kernels >> into images. The script, which I originally obtained from the mirage = docs ( >> http://openmirage.org/docs/xen-boot), was working earlier this = summer. I >> may have accidentally deleted the line that generates an initrd. The >> original script >>=20 >> - I am running shell command with OCaml's `Unix.open_process_in`. I = need >> to figure out why the command is not giving consistent results... = about 1 >> out of 10 times it will produce the correct digest. (A SHA1 digest of = the >> input image after it is compressed and encrypted.) >> The shell command is >> openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h = -S >> --owner 0 --group 0 -C /tmp mymirage.img | tee >> /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e >> -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv >> bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc >>=20 >> And Hannes, thanks for your help! I was able to use nocrypto and >> ocaml-x509 to extract RSA keys and encrypt. I will look into = replacing >> cryptokit with ocaml-sha. >>=20 >> Best, >> Jyotsna >>=20 >>=20 >> On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert >> wrote: >>=20 >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA384 >>>=20 >>> Hi Jyotsna, >>>=20 >>> On 07/17/2014 19:48, Jyotsna Prakash wrote: >>>> For my GSoC project I've been working on OCaml bindings to the EC2 >>>> API. The code is at https://github.com/moonlightdrive/ocaml-ec2 >>>=20 >>> Awesome! >>>=20 >>>> I've yet to launch a Mirage-backed VM without using the Amazon's >>>> CLI tools. The process involves producing an xml manifest >>>> describing an image; the manifest contains fields of RSA encrypted >>>> data. Problem is, I don't have any way to take my public keys (pem >>>> files) and turn them into `Cryptokit.RSA.key`s. >>>=20 >>> AFAICS you're only using SHA256 from Cryptokit so far -- you might >>> want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for = that. >>>=20 >>> Also, David wrote ocaml-nocrypto >>> (https://github.com/mirleft/ocaml-nocrypto) and we further developed >>> ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can >>> parse pem to get a certificate >>> (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) >>> or a private key (RSA) >>> https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 >>> (example usage: >>> = https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) >>>=20 >>> What do you need to do with the RSA key? The nocrypto API is at >>> https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli >>>=20 >>>=20 >>> Cheers, >>>=20 >>> Hannes >>>=20 >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.22 (FreeBSD) >>>=20 >>> iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI >>> JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ >>> xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM >>> eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU >>> 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d >>> PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW >>> Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k >>> pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG >>> AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p >>> XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s >>> 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz >>> pgdhpVDaP3Ocu+kRpFEB >>> =3Dzzgd >>> -----END PGP SIGNATURE----- >>>=20 >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>=20 >>=20 >>=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii mirari = is deprecated, you should use mirage/mirage



On 4 Aug 2014, at 19:52, = Jyotsna Prakash <jyotsna.prakash@gmail.com>= ; wrote:

Sorry, half my sentence disappeared!
- There is = something wrong with the method I am using to turn xen kernels
into = images. The script, which I originally obtained from the mirage docs = (
http://openmirage.org/docs/xe= n-boot), was working earlier this summer. I
may have accidentally = deleted the line that generates an initrd. The
original script is, = linked from the mirage docs, is missing.


On Mon, Aug 4, 2014 = at 11:50 AM, Jyotsna Prakash <jyotsna.prakash@gmail.com>= ;
wrote:

Hello,

I've written = a blog post
<h= ttp://1000hippos.wordpress.com/2014/08/04/ec2-bundling-images/> = about
the EC2 image bundling process, and what I have left to do. The = short of it
is:

- There is something wrong with the method I = am using to turn xen kernels
into images. The script, which I = originally obtained from the mirage docs (
http://openmirage.org/docs/xe= n-boot), was working earlier this summer. I
may have accidentally = deleted the line that generates an initrd. The
original = script

- I am running shell command with OCaml's = `Unix.open_process_in`. I need
to figure out why the command is not = giving consistent results... about 1
out of 10 times it will produce = the correct digest. (A SHA1 digest of the
input image after it is = compressed and encrypted.)
The shell command is
 openssl = sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h = -S
--owner 0 --group 0 -C /tmp mymirage.img | = tee
/tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc = -e
-aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa = -iv
bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > = ec2_tmp/mymirage.img.tar.gz.enc

And Hannes, thanks for your help! = I was able to use nocrypto and
ocaml-x509 to extract RSA keys and = encrypt. I will look into replacing
cryptokit with = ocaml-sha.

Best,
Jyotsna


On Thu, Jul 17, 2014 at = 11:59 AM, Hannes Mehnert <hannes@mehnert.org>
wrote:
-----BEGIN PGP SIGNED = MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 = 19:48, Jyotsna Prakash wrote:
For my GSoC = project I've been working on OCaml bindings to the EC2
API. The code = is at https://github.com/mo= onlightdrive/ocaml-ec2

Awesome!

I've yet to launch a Mirage-backed VM without using the = Amazon's
CLI tools. The process involves producing an xml = manifest
describing an image; the manifest contains fields of RSA = encrypted
data. Problem is, I don't have any way to take my public = keys (pem
files) and turn them into = `Cryptokit.RSA.key`s.

AFAICS you're only using = SHA256 from Cryptokit so far -- you might
want to use ocaml-sha (https://github.com/vincent= hz/ocaml-sha) for that.

Also, David wrote = ocaml-nocrypto
(https://github.com/mirl= eft/ocaml-nocrypto) and we further developed
ocaml-x509 (https://github.com/mirleft= /ocaml-x509/) where you can
parse pem to get a certificate
(https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18)<= br>or a private key (RSA)
https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30(example = usage:
https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml= #L49)

What do you need to do with the RSA key? The nocrypto API = is = at
https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli

Cheers,

Hannes

-----BEGIN PGP = SIGNATURE-----
Version: GnuPG v2.0.22 = (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0td= vUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1= /
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM
e= XD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU
7iq6fsN= uLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d
PMSoQQtWTEGrf= GyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw2pZ2tDbOkwDcIH= tb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9ktW996QAPdhKg= ck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCDGao/JGBaG+= 2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLY= UlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKme= bl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END PGP = SIGNATURE-----

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

= --Apple-Mail=_28F778C9-B797-45F9-9C20-9CBFDA06FD6B-- --===============3498545350660590002== 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 --===============3498545350660590002==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 09:52:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 09:52: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 1XEbPf-0000rM-5Q; Tue, 05 Aug 2014 09:52:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEbPd-0000rE-9j for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 09:52:09 +0000 Received: from [193.109.254.147:6163] by server-3.bemta-14.messagelabs.com id E9/C3-23707-849A0E35; Tue, 05 Aug 2014 09:52:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-27.messagelabs.com!1407232313!13786213!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTA5MTUgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9308 invoked from network); 5 Aug 2014 09:51:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-27.messagelabs.com with SMTP; 5 Aug 2014 09:51:53 -0000 Received: (qmail 22059 invoked by uid 634); 5 Aug 2014 09:51:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from dab-far1-h-12-1.dab.02.net (HELO [10.8.89.160]) (82.132.220.144) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 05 Aug 2014 10:51:51 +0100 References: <53C81D1E.4020102@mehnert.org> <5DB9916D-1757-493B-8B94-FC03C237957D@gazagnaire.org> Mime-Version: 1.0 (1.0) In-Reply-To: <5DB9916D-1757-493B-8B94-FC03C237957D@gazagnaire.org> Message-Id: <28D08564-1751-47EB-9FFF-6CCC8B7FE8D7@recoil.org> X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Tue, 5 Aug 2014 10:51:44 +0100 To: Thomas Gazagnaire X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2516816130796257334==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2516816130796257334== Content-Type: multipart/alternative; boundary=Apple-Mail-2CBEEE59-20BC-41F4-BCB1-7E161B12373C Content-Transfer-Encoding: 7bit --Apple-Mail-2CBEEE59-20BC-41F4-BCB1-7E161B12373C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable That's a very comprehensive blog post Jyotsna! It would be good to verify i= f the ec2.sh script below works using the CLI tools and modern Mirage kernel= s. Mindy has had this working on her blog (see http://www.somerandomidiot.co= m/blog/2014/03/24/arriving-at-the-mirage/) and I've booted several test kern= els (but haven't touched my EC2 CLI setup for years so it might not be usefu= l). Once that works, we can start bisecting the issues in your bindings (which s= eem to be really really close to working!) Anil=20 > On 5 Aug 2014, at 10:05, Thomas Gazagnaire wrote: >=20 > mirari is deprecated, you should use mirage/mirage >=20 > So the initial script is there https://raw.githubusercontent.com/mirage/mi= rage/master/scripts/ec2.sh >=20 >=20 >> On 4 Aug 2014, at 19:52, Jyotsna Prakash wrot= e: >>=20 >> Sorry, half my sentence disappeared! >> - There is something wrong with the method I am using to turn xen kernels= >> into images. The script, which I originally obtained from the mirage docs= ( >> http://openmirage.org/docs/xen-boot), was working earlier this summer. I >> may have accidentally deleted the line that generates an initrd. The >> original script is, linked from the mirage docs, is missing. >>=20 >>=20 >> On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash >> wrote: >>=20 >>> Hello, >>>=20 >>> I've written a blog post >>> about >>> the EC2 image bundling process, and what I have left to do. The short of= it >>> is: >>>=20 >>> - There is something wrong with the method I am using to turn xen kernel= s >>> into images. The script, which I originally obtained from the mirage doc= s ( >>> http://openmirage.org/docs/xen-boot), was working earlier this summer. I= >>> may have accidentally deleted the line that generates an initrd. The >>> original script >>>=20 >>> - I am running shell command with OCaml's `Unix.open_process_in`. I need= >>> to figure out why the command is not giving consistent results... about 1= >>> out of 10 times it will produce the correct digest. (A SHA1 digest of th= e >>> input image after it is compressed and encrypted.) >>> The shell command is >>> openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h -S >>> --owner 0 --group 0 -C /tmp mymirage.img | tee >>> /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e >>> -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv >>> bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc >>>=20 >>> And Hannes, thanks for your help! I was able to use nocrypto and >>> ocaml-x509 to extract RSA keys and encrypt. I will look into replacing >>> cryptokit with ocaml-sha. >>>=20 >>> Best, >>> Jyotsna >>>=20 >>>=20 >>> On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert >>> wrote: >>>=20 >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA384 >>>>=20 >>>> Hi Jyotsna, >>>>=20 >>>>> On 07/17/2014 19:48, Jyotsna Prakash wrote: >>>>> For my GSoC project I've been working on OCaml bindings to the EC2 >>>>> API. The code is at https://github.com/moonlightdrive/ocaml-ec2 >>>>=20 >>>> Awesome! >>>>=20 >>>>> I've yet to launch a Mirage-backed VM without using the Amazon's >>>>> CLI tools. The process involves producing an xml manifest >>>>> describing an image; the manifest contains fields of RSA encrypted >>>>> data. Problem is, I don't have any way to take my public keys (pem >>>>> files) and turn them into `Cryptokit.RSA.key`s. >>>>=20 >>>> AFAICS you're only using SHA256 from Cryptokit so far -- you might >>>> want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that= . >>>>=20 >>>> Also, David wrote ocaml-nocrypto >>>> (https://github.com/mirleft/ocaml-nocrypto) and we further developed >>>> ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can >>>> parse pem to get a certificate >>>> (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) >>>> or a private key (RSA) >>>> https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 >>>> (example usage: >>>> https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) >>>>=20 >>>> What do you need to do with the RSA key? The nocrypto API is at >>>> https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli >>>>=20 >>>>=20 >>>> Cheers, >>>>=20 >>>> Hannes >>>>=20 >>>> -----BEGIN PGP SIGNATURE----- >>>> Version: GnuPG v2.0.22 (FreeBSD) >>>>=20 >>>> iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI >>>> JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ >>>> xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM >>>> eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU >>>> 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d >>>> PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW >>>> Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k >>>> pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG >>>> AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p >>>> XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s >>>> 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz >>>> pgdhpVDaP3Ocu+kRpFEB >>>> =3Dzzgd >>>> -----END PGP SIGNATURE----- >>>>=20 >>>> _______________________________________________ >>>> 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-2CBEEE59-20BC-41F4-BCB1-7E161B12373C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
That's a very comprehensive blog post J= yotsna!  It would be good to verify if the ec2.sh script below works us= ing the CLI tools and modern Mirage kernels. Mindy has had this working on h= er blog (see http://www.somerandomidiot.com/blog/2014/03/24/arri= ving-at-the-mirage/) and I've booted several test kernels (but haven't t= ouched my EC2 CLI setup for years so it might not be useful).

=
Once that works, we can start bisecting the issues in your bindin= gs (which seem to be really really close to working!)

Anil 

On 5 Aug 2014, at 10:05, Thomas Gazagnaire <<= a href=3D"mailto:thomas@gazagnaire.org">thomas@gazagnaire.org> wrote:=

mirari is deprecated, you should= use mirage/mirage

So the initial script is there https://raw.githubusercontent.com/mirage/mirage/master/scripts/ec2.sh


On 4 Aug 2014, at 19:52, Jyotsna Pr= akash <jyotsna.prakash@gmail= .com> wrote:

Sorry, half my sentence disappeared!
- There is something w= rong with the method I am using to turn xen kernels
into images. The scri= pt, which I originally obtained from the mirage docs (
http://openmirage.org/docs/xen-boot), was w= orking earlier this summer. I
may have accidentally deleted the line that= generates an initrd. The
original script is, linked from the mirage docs= , is missing.


On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash &l= t;jyotsna.prakash@gmail.com= >
wrote:

Hello,

I've written a= blog post
<http://1000hippos.wordpress.com/2014/08/04/ec2-bundling-im= ages/> about
the EC2 image bundling process, and what I have left t= o do. The short of it
is:

- There is something wrong with the meth= od I am using to turn xen kernels
into images. The script, which I origin= ally obtained from the mirage docs (
http://openmirage.org/docs/xen-boot), was working earlier th= is summer. I
may have accidentally deleted the line that generates an ini= trd. The
original script

- I am running shell command with OCaml's= `Unix.open_process_in`. I need
to figure out why the command is not givi= ng consistent results... about 1
out of 10 times it will produce the corr= ect digest. (A SHA1 digest of the
input image after it is compressed and e= ncrypted.)
The shell command is
 openssl sha1 < /tmp/ec2-bund= le-image-digest-pipe-10174 & tar -c -h -S
--owner 0 --group 0 -C /tmp= mymirage.img | tee
/tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | o= penssl enc -e
-aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv
bbb= bbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc

An= d Hannes, thanks for your help! I was able to use nocrypto and
ocaml-x509= to extract RSA keys and encrypt. I will look into replacing
cryptokit wi= th ocaml-sha.

Best,
Jyotsna


On Thu, Jul 17, 2014 at 11:= 59 AM, Hannes Mehnert <hannes@mehne= rt.org>
wrote:

-----BEGIN PGP SIG= NED MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 19:= 48, Jyotsna Prakash wrote:
For my GSoC project I= 've been working on OCaml bindings to the EC2
API. The code is at https://github.com/moonligh= tdrive/ocaml-ec2

Awesome!

I've yet to launch a Mirage-backed VM without using the Amazon's
C= LI tools. The process involves producing an xml manifest
describing an im= age; the manifest contains fields of RSA encrypted
data. Problem is, I do= n't have any way to take my public keys (pem
files) and turn them into `C= ryptokit.RSA.key`s.

AFAICS you're only using SHA256 from= Cryptokit so far -- you might
want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) f= or that.

Also, David wrote ocaml-nocrypto
(https://github.com/mirleft/ocaml-nocrypto= ) and we further developed
ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you canparse pem to get a certificate
(https://github.com/mirleft/ocaml-x50= 9/blob/master/lib/x509.mli#L18)
or a private key (RSA)
https://= github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30
(example u= sage:
https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.= ml#L49)

What do you need to do with the RSA key? The nocrypto API= is at
https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.ml= i


Cheers,

Hannes

-----BEGIN PGP SIGNATURE-----<= br>Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjff= Cjuns8P/AnRdjFMIcs0PA0tdvUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3D= paqB+qPLESB094hS9Fqds1/
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4Nu= tcV1OTBRi9ysOVM
eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3Z= rOXpJYU
7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d<= br>PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw= 2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9k= tW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCD= Gao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4= bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjC= huYKmebl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END P= GP SIGNATURE-----

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


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

__________________= _____________________________
MirageOS-devel mailing list
MirageO= S-devel@lists.xenproject.org
http://lists.xenproject= .org/cgi-bin/mailman/listinfo/mirageos-devel
= --Apple-Mail-2CBEEE59-20BC-41F4-BCB1-7E161B12373C-- --===============2516816130796257334== 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 --===============2516816130796257334==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 09:52:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 09:52: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 1XEbPf-0000rM-5Q; Tue, 05 Aug 2014 09:52:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEbPd-0000rE-9j for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 09:52:09 +0000 Received: from [193.109.254.147:6163] by server-3.bemta-14.messagelabs.com id E9/C3-23707-849A0E35; Tue, 05 Aug 2014 09:52:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-27.messagelabs.com!1407232313!13786213!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MIME_QP_LONG_LINE, ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTA5MTUgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9308 invoked from network); 5 Aug 2014 09:51:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-27.messagelabs.com with SMTP; 5 Aug 2014 09:51:53 -0000 Received: (qmail 22059 invoked by uid 634); 5 Aug 2014 09:51:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from dab-far1-h-12-1.dab.02.net (HELO [10.8.89.160]) (82.132.220.144) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 05 Aug 2014 10:51:51 +0100 References: <53C81D1E.4020102@mehnert.org> <5DB9916D-1757-493B-8B94-FC03C237957D@gazagnaire.org> Mime-Version: 1.0 (1.0) In-Reply-To: <5DB9916D-1757-493B-8B94-FC03C237957D@gazagnaire.org> Message-Id: <28D08564-1751-47EB-9FFF-6CCC8B7FE8D7@recoil.org> X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Tue, 5 Aug 2014 10:51:44 +0100 To: Thomas Gazagnaire X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] OCaml bindings for EC2 API X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2516816130796257334==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2516816130796257334== Content-Type: multipart/alternative; boundary=Apple-Mail-2CBEEE59-20BC-41F4-BCB1-7E161B12373C Content-Transfer-Encoding: 7bit --Apple-Mail-2CBEEE59-20BC-41F4-BCB1-7E161B12373C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable That's a very comprehensive blog post Jyotsna! It would be good to verify i= f the ec2.sh script below works using the CLI tools and modern Mirage kernel= s. Mindy has had this working on her blog (see http://www.somerandomidiot.co= m/blog/2014/03/24/arriving-at-the-mirage/) and I've booted several test kern= els (but haven't touched my EC2 CLI setup for years so it might not be usefu= l). Once that works, we can start bisecting the issues in your bindings (which s= eem to be really really close to working!) Anil=20 > On 5 Aug 2014, at 10:05, Thomas Gazagnaire wrote: >=20 > mirari is deprecated, you should use mirage/mirage >=20 > So the initial script is there https://raw.githubusercontent.com/mirage/mi= rage/master/scripts/ec2.sh >=20 >=20 >> On 4 Aug 2014, at 19:52, Jyotsna Prakash wrot= e: >>=20 >> Sorry, half my sentence disappeared! >> - There is something wrong with the method I am using to turn xen kernels= >> into images. The script, which I originally obtained from the mirage docs= ( >> http://openmirage.org/docs/xen-boot), was working earlier this summer. I >> may have accidentally deleted the line that generates an initrd. The >> original script is, linked from the mirage docs, is missing. >>=20 >>=20 >> On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash >> wrote: >>=20 >>> Hello, >>>=20 >>> I've written a blog post >>> about >>> the EC2 image bundling process, and what I have left to do. The short of= it >>> is: >>>=20 >>> - There is something wrong with the method I am using to turn xen kernel= s >>> into images. The script, which I originally obtained from the mirage doc= s ( >>> http://openmirage.org/docs/xen-boot), was working earlier this summer. I= >>> may have accidentally deleted the line that generates an initrd. The >>> original script >>>=20 >>> - I am running shell command with OCaml's `Unix.open_process_in`. I need= >>> to figure out why the command is not giving consistent results... about 1= >>> out of 10 times it will produce the correct digest. (A SHA1 digest of th= e >>> input image after it is compressed and encrypted.) >>> The shell command is >>> openssl sha1 < /tmp/ec2-bundle-image-digest-pipe-10174 & tar -c -h -S >>> --owner 0 --group 0 -C /tmp mymirage.img | tee >>> /tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | openssl enc -e >>> -aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv >>> bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc >>>=20 >>> And Hannes, thanks for your help! I was able to use nocrypto and >>> ocaml-x509 to extract RSA keys and encrypt. I will look into replacing >>> cryptokit with ocaml-sha. >>>=20 >>> Best, >>> Jyotsna >>>=20 >>>=20 >>> On Thu, Jul 17, 2014 at 11:59 AM, Hannes Mehnert >>> wrote: >>>=20 >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA384 >>>>=20 >>>> Hi Jyotsna, >>>>=20 >>>>> On 07/17/2014 19:48, Jyotsna Prakash wrote: >>>>> For my GSoC project I've been working on OCaml bindings to the EC2 >>>>> API. The code is at https://github.com/moonlightdrive/ocaml-ec2 >>>>=20 >>>> Awesome! >>>>=20 >>>>> I've yet to launch a Mirage-backed VM without using the Amazon's >>>>> CLI tools. The process involves producing an xml manifest >>>>> describing an image; the manifest contains fields of RSA encrypted >>>>> data. Problem is, I don't have any way to take my public keys (pem >>>>> files) and turn them into `Cryptokit.RSA.key`s. >>>>=20 >>>> AFAICS you're only using SHA256 from Cryptokit so far -- you might >>>> want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) for that= . >>>>=20 >>>> Also, David wrote ocaml-nocrypto >>>> (https://github.com/mirleft/ocaml-nocrypto) and we further developed >>>> ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you can >>>> parse pem to get a certificate >>>> (https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L18) >>>> or a private key (RSA) >>>> https://github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30 >>>> (example usage: >>>> https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.ml#L49) >>>>=20 >>>> What do you need to do with the RSA key? The nocrypto API is at >>>> https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.mli >>>>=20 >>>>=20 >>>> Cheers, >>>>=20 >>>> Hannes >>>>=20 >>>> -----BEGIN PGP SIGNATURE----- >>>> Version: GnuPG v2.0.22 (FreeBSD) >>>>=20 >>>> iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjffCjuns8P/AnRdjFMIcs0PA0tdvUVuNDI >>>> JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3DpaqB+qPLESB094hS9Fqds1/ >>>> xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4NutcV1OTBRi9ysOVM >>>> eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3ZrOXpJYU >>>> 7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d >>>> PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW >>>> Eq9vw2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k >>>> pJoENKXAcap9ktW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG >>>> AP6SUCU6JzhJfoloTnfCDGao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p >>>> XHakfCuiMjAvk8WPBjhZXMi9ce0O4bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s >>>> 8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjChuYKmebl0EpsAN+h+p7S5YoQJYz >>>> pgdhpVDaP3Ocu+kRpFEB >>>> =3Dzzgd >>>> -----END PGP SIGNATURE----- >>>>=20 >>>> _______________________________________________ >>>> 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-2CBEEE59-20BC-41F4-BCB1-7E161B12373C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
That's a very comprehensive blog post J= yotsna!  It would be good to verify if the ec2.sh script below works us= ing the CLI tools and modern Mirage kernels. Mindy has had this working on h= er blog (see http://www.somerandomidiot.com/blog/2014/03/24/arri= ving-at-the-mirage/) and I've booted several test kernels (but haven't t= ouched my EC2 CLI setup for years so it might not be useful).

=
Once that works, we can start bisecting the issues in your bindin= gs (which seem to be really really close to working!)

Anil 

On 5 Aug 2014, at 10:05, Thomas Gazagnaire <<= a href=3D"mailto:thomas@gazagnaire.org">thomas@gazagnaire.org> wrote:=

mirari is deprecated, you should= use mirage/mirage

So the initial script is there https://raw.githubusercontent.com/mirage/mirage/master/scripts/ec2.sh


On 4 Aug 2014, at 19:52, Jyotsna Pr= akash <jyotsna.prakash@gmail= .com> wrote:

Sorry, half my sentence disappeared!
- There is something w= rong with the method I am using to turn xen kernels
into images. The scri= pt, which I originally obtained from the mirage docs (
http://openmirage.org/docs/xen-boot), was w= orking earlier this summer. I
may have accidentally deleted the line that= generates an initrd. The
original script is, linked from the mirage docs= , is missing.


On Mon, Aug 4, 2014 at 11:50 AM, Jyotsna Prakash &l= t;jyotsna.prakash@gmail.com= >
wrote:

Hello,

I've written a= blog post
<http://1000hippos.wordpress.com/2014/08/04/ec2-bundling-im= ages/> about
the EC2 image bundling process, and what I have left t= o do. The short of it
is:

- There is something wrong with the meth= od I am using to turn xen kernels
into images. The script, which I origin= ally obtained from the mirage docs (
http://openmirage.org/docs/xen-boot), was working earlier th= is summer. I
may have accidentally deleted the line that generates an ini= trd. The
original script

- I am running shell command with OCaml's= `Unix.open_process_in`. I need
to figure out why the command is not givi= ng consistent results... about 1
out of 10 times it will produce the corr= ect digest. (A SHA1 digest of the
input image after it is compressed and e= ncrypted.)
The shell command is
 openssl sha1 < /tmp/ec2-bund= le-image-digest-pipe-10174 & tar -c -h -S
--owner 0 --group 0 -C /tmp= mymirage.img | tee
/tmp/ec2-bundle-image-digest-pipe-10174 | gzip -9 | o= penssl enc -e
-aes-128-cbc -K aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa -iv
bbb= bbbbbbbbbbbbbbbbbbbbbbbbbbbbb > ec2_tmp/mymirage.img.tar.gz.enc

An= d Hannes, thanks for your help! I was able to use nocrypto and
ocaml-x509= to extract RSA keys and encrypt. I will look into replacing
cryptokit wi= th ocaml-sha.

Best,
Jyotsna


On Thu, Jul 17, 2014 at 11:= 59 AM, Hannes Mehnert <hannes@mehne= rt.org>
wrote:

-----BEGIN PGP SIG= NED MESSAGE-----
Hash: SHA384

Hi Jyotsna,

On 07/17/2014 19:= 48, Jyotsna Prakash wrote:
For my GSoC project I= 've been working on OCaml bindings to the EC2
API. The code is at https://github.com/moonligh= tdrive/ocaml-ec2

Awesome!

I've yet to launch a Mirage-backed VM without using the Amazon's
C= LI tools. The process involves producing an xml manifest
describing an im= age; the manifest contains fields of RSA encrypted
data. Problem is, I do= n't have any way to take my public keys (pem
files) and turn them into `C= ryptokit.RSA.key`s.

AFAICS you're only using SHA256 from= Cryptokit so far -- you might
want to use ocaml-sha (https://github.com/vincenthz/ocaml-sha) f= or that.

Also, David wrote ocaml-nocrypto
(https://github.com/mirleft/ocaml-nocrypto= ) and we further developed
ocaml-x509 (https://github.com/mirleft/ocaml-x509/) where you canparse pem to get a certificate
(https://github.com/mirleft/ocaml-x50= 9/blob/master/lib/x509.mli#L18)
or a private key (RSA)
https://= github.com/mirleft/ocaml-x509/blob/master/lib/x509.mli#L30
(example u= sage:
https://github.com/mirleft/ocaml-tls/blob/master/lwt/x509_lwt.= ml#L49)

What do you need to do with the RSA key? The nocrypto API= is at
https://github.com/mirleft/ocaml-nocrypto/blob/master/src/rsa.ml= i


Cheers,

Hannes

-----BEGIN PGP SIGNATURE-----<= br>Version: GnuPG v2.0.22 (FreeBSD)

iQIcBAEBCQAGBQJTyB0eAAoJELyJZYjff= Cjuns8P/AnRdjFMIcs0PA0tdvUVuNDI
JbViUzCvhyQbDQYdVpLLoub/BZAz6A2WrVbHOuJ3D= paqB+qPLESB094hS9Fqds1/
xy20RthXkZwKOFYRKJ8flHBaRqaZV/ffXCb3qpEOpo8RrN4Nu= tcV1OTBRi9ysOVM
eXD2qbLUq6CqAzenks3r8G7Rkk1uzKcu2pxixDygx60EU8JPBw0m50j3Z= rOXpJYU
7iq6fsNuLYV4NyvZYizkLROL/6G0sfYTLjnPWmR5hAXypjqt1Ad5n1VYhq3oEt8d<= br>PMSoQQtWTEGrfGyxKDQQfo0feQ2r5/lsqDVXcuCZhWDrguBDId08zc1tnmCej7EW
Eq9vw= 2pZ2tDbOkwDcIHtb/ACuNjXSP1XmP/1VcWSCHly8mSnLkbCKE6Nkz4e345k
pJoENKXAcap9k= tW996QAPdhKgck/sVVQOxEZ3BkFMThL2pjrw6v6RRCJq3nNCroG
AP6SUCU6JzhJfoloTnfCD= Gao/JGBaG+2vq1fTArXhc7WHPd1OLuC+lAlxScoLJ4p
XHakfCuiMjAvk8WPBjhZXMi9ce0O4= bv5CSFLYUlT5+H1XcXTpmibc5M3KxKdk25s
8WreBAVLdshBaOaOOcr8GOqgTxMrgIb6uipjC= huYKmebl0EpsAN+h+p7S5YoQJYz
pgdhpVDaP3Ocu+kRpFEB
=3Dzzgd
-----END P= GP SIGNATURE-----

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


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

__________________= _____________________________
MirageOS-devel mailing list
MirageO= S-devel@lists.xenproject.org
http://lists.xenproject= .org/cgi-bin/mailman/listinfo/mirageos-devel
= --Apple-Mail-2CBEEE59-20BC-41F4-BCB1-7E161B12373C-- --===============2516816130796257334== 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 --===============2516816130796257334==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:16:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:16:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEbnQ-0001wx-GU; Tue, 05 Aug 2014 10:16:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEbnP-0001wh-Fb for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:16:43 +0000 Received: from [85.158.139.211:10397] by server-2.bemta-5.messagelabs.com id 17/9C-31832-A0FA0E35; Tue, 05 Aug 2014 10:16:42 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-11.tower-206.messagelabs.com!1407233802!7806695!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10801 invoked from network); 5 Aug 2014 10:16:42 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Aug 2014 10:16:42 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-152-76.eduroam.wireless.private.cam.ac.uk ([172.17.152.76]:59863) 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 1XEbnN-0000V1-lt (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 05 Aug 2014 11:16:41 +0100 From: Amir Chaudhry Message-Id: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> Date: Tue, 5 Aug 2014 11:16:43 +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, Thursday 7th 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 Dear all, The Mirage call will take place on *Thursday 7th* at 4pm BST (== GMT + 1). Note the change of day for this week (again)! If you have points you'd like to discuss, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: +1 (213) 493-0008 Thanks, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:16:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:16:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEbnQ-0001wx-GU; Tue, 05 Aug 2014 10:16:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEbnP-0001wh-Fb for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:16:43 +0000 Received: from [85.158.139.211:10397] by server-2.bemta-5.messagelabs.com id 17/9C-31832-A0FA0E35; Tue, 05 Aug 2014 10:16:42 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-11.tower-206.messagelabs.com!1407233802!7806695!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.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10801 invoked from network); 5 Aug 2014 10:16:42 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-11.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Aug 2014 10:16:42 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-152-76.eduroam.wireless.private.cam.ac.uk ([172.17.152.76]:59863) 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 1XEbnN-0000V1-lt (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 05 Aug 2014 11:16:41 +0100 From: Amir Chaudhry Message-Id: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> Date: Tue, 5 Aug 2014 11:16:43 +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, Thursday 7th 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 Dear all, The Mirage call will take place on *Thursday 7th* at 4pm BST (== GMT + 1). Note the change of day for this week (again)! If you have points you'd like to discuss, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: +1 (213) 493-0008 Thanks, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:43:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:43:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcD1-0002wH-K6; Tue, 05 Aug 2014 10:43:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcD0-0002wC-7A for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:43:10 +0000 Received: from [193.109.254.147:53782] by server-10.bemta-14.messagelabs.com id FD/26-06615-D35B0E35; Tue, 05 Aug 2014 10:43:09 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-27.messagelabs.com!1407235385!13727512!1 X-Originating-IP: [80.12.242.129] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16157 invoked from network); 5 Aug 2014 10:43:05 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-3.tower-27.messagelabs.com with SMTP; 5 Aug 2014 10:43:05 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d65 with ME id ayj51o00W13qAZm03yj5V5; Tue, 05 Aug 2014 12:43:05 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 12:43:05 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 12:43:05 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1149091954.7224.1407235385400.JavaMail.www@wwinf1c25> In-Reply-To: <973F6395-6B7A-4CC9-8780-F9094CCCAE2F@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <973F6395-6B7A-4CC9-8780-F9094CCCAE2F@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~||~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6774558513720904505==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6774558513720904505== Content-Type: multipart/alternative; boundary="----=_Part_7223_215238386.1407235385393" ------=_Part_7223_215238386.1407235385393 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i found this page on sunxi linux mainlining : https://groups.google.com/for= um/#!searchin/linux-sunxi/boris/linux-sunxi/s3lBb01I0Js/Bem2X1wKPa4J and i = will try to inspire me. 3.14 r4 branch of linux would suffice for xen ?=20 > Message du 04/08/14 23:58 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "Thomas Leonard" , "mirageos-devel@lists.xenproject.org"= =20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 >There are several forks of the Linux kernel, and this one is probably the = Linux-Sunxi branch that adds support into a branch. =C2=A0Our xen-arm-build= er script is now using the upstream Linux kernel that has several (but not = all) of the Sunxi-specific functionality integrated into it. =C2=A0 > See=C2=A0http://linux-sunxi.org/Linux_mainlining_effort=C2=A0for more infor= mation on this. > -anil > On 4 Aug 2014, at 14:53, Gilles DALMAS wrote: > In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruck= -Debian/blob/master/config/kernel.config.3.4.61 there is for example the li= ne CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the = kernel, how is it that this option does not appear in the following version= s of the kernel? if I add it manually in the config file, is it processed? >=20 >=20 >=20 >=20 > > Message du 04/08/14 15:03 > > De : "Gilles DALMAS"=20 > > A : "Thomas Leonard" , "Anil Madhavapeddy"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > > > apparently, the xen-arm-builder script solves the problem of slowness. = even without installing mirage-net-xen. >=20 >=20 >=20 >=20 > > Message du 04/08/14 13:28 > > De : "Thomas Leonard"=20 > > A : "Anil Madhavapeddy"=20 > > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"= =20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 3 August 2014 17:24, Thomas Leonard wrote: > > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > > >> > > >> hi, > > >> > > >> I recently compiled mirage for cubietruck. > > >> > > >> Everything works fine, but the system is extremely slow. > > >> > > >> Hi Gilles, > > >> > > >> Glad to hear you've got it up and running. Could you shed some light= about > > >> the nature of the application that is slow? > > >> > > >> If it's networking, there's a known bug at the moment [1] due to a > > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. T= homas > > >> Leonard has just applied a backport to the SDCard image builder [2] = that > > >> fixes this issue in Xen itself, so we could remove the workaround no= w and > > >> hopefully get back to decent networking performance (is this correct= , > > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > > > Yes, I'll rebuild the binary images at some point but for now you can > > > build from Git. With that, you can revert back to the older > > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. > >=20 > > Here are the new images: > >=20 > > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 > >=20 > > Installation instructions are here: > >=20 > > https://github.com/mirage/xen-arm-builder > >=20 > > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow= : > >=20 > > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1= .1.1 > >=20 > >=20 > > --=20 > > 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 > > >=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 > > ------=_Part_7223_215238386.1407235385393 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

i found this page on sunxi linux mainlining : https://groups.google.com/= forum/#!searchin/linux-sunxi/boris/linux-sunxi/s3lBb01I0Js/Bem2X1wKPa4J and= i will try to inspire me. 3.14 r4 branch of linux would suffice for xen ? =



> Message du 04/08/14 23:58
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "Thomas Leonard" <talex5@gmail.com= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
>There are several forks of the = Linux kernel, and this one is probably the Linux-Sunxi branch that adds sup= port into a branch. =C2=A0Our xen-arm-builder script is now using the upstr= eam Linux kernel that has several (but not all) of the Sunxi-specific funct= ionality integrated into it. =C2=A0

>
See=C2=A0ht= tp://linux-sunxi.org/Linux_mainlining_effort=C2=A0for more information = on this.

>
-anil

>
On 4 Aug 2014, at 14:53, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> In terms of the nand, on page: https://g= ithub.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kernel.config.3= .4.61 there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y a= nd this is the 3.4.61 version of the kernel, how is it that this option doe= s not appear in the following versions of the kernel? if I add it manually = in the config file, is it processed?
>
>
>
= >
>

> Message du 04/08/14 15:03
> > De : "Gilles = DALMAS" <gdalmas@wanadoo.fr>= ;
> > A : "Thomas Leonard" <talex5@gmail.com>, "Anil Madhavapeddy" <anil@recoil.org>
> > Copie =C3=A0 : "mirageos-devel@lists.xenpro= ject.org" <mi= rageos-devel@lists.xenproject.org>
> > Objet : Re: [Mirag= eOS-devel] mirage os on cubietruck nand detection
> >
>= >

> > apparently, the xen-arm-builder script solves the problem of s= lowness. even without installing mirage-net-xen.
>
>
>
>
>

> Message du 04/08/14 13:28
> > De : "Thomas = Leonard" <talex5@gmail.com>> > A : "Anil Madhavapeddy" <anil@recoil.org>
> > Copie =C3=A0 : "Gilles DALMAS" <= ;gdalmas@wanadoo.fr>, "mirageos-devel@lists.xenpro= ject.org" <mi= rageos-devel@lists.xenproject.org>
> > Objet : Re: [Mirag= eOS-devel] mirage os on cubietruck nand detection
> >
>= > On 3 August 2014 17:24, Thomas Leonard <talex5@gmail.com> wrote:
> > > On 3 August 2= 014 17:20, Anil Madhavapeddy <anil@re= coil.org> wrote:
> > >> On 3 Aug 2014, at 16:34, Gi= lles DALMAS <gdalmas@wanadoo.fr> wrote:
> > >>
> > >> hi,
> = > >>
> > >> I recently compiled mirage for cubiet= ruck.
> > >>
> > >> Everything works fine= , but the system is extremely slow.
> > >>
> > = >> Hi Gilles,
> > >>
> > >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; > >> the nature of the application that is slow?
> >= >>
> > >> If it's networking, there's a known bug a= t the moment [1] due to a
> > >> limitation on Xen 4.4/ARM= that prevents multiple mapping of pages. Thomas
> > >> Le= onard has just applied a backport to the SDCard image builder [2] that
> > >> fixes this issue in Xen itself, so we could remove the = workaround now and
> > >> hopefully get back to decent net= working performance (is this correct,
> > >> Thomas? I hav= en't had a chance to rebuild my own Cubie2 yet).
> > >
&= gt; > > Yes, I'll rebuild the binary images at some point but for now= you can
> > > build from Git. With that, you can revert back= to the older
> > > mirage-net-xen v1.1.1 to avoid the wait a= fter sending each packet.
> >
> > Here are the new i= mages:
> >
> > http://blobs.openmirage.org/cubieboard2-xen-= iso.tar.bz2
> > http://blobs.openmirage.org/cubietruck-xen-iso.tar.b= z2
> >
> > Installation instructions are here:> >
> > https://github.com/mirage/xen-arm-builder
> >
> > Remember to use mirage-net-xen v1.1.1 as well, or it will still = be slow:
> >
> > opam pin mirage-net-xen https://github.com/mir= age/mirage-net-xen.git#v1.1.1
> >
> >
>= > --
> > 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@lis= ts.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>
>
_______________________________________________
> MirageOS-devel ma= iling list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.= org/cgi-bin/mailman/listinfo/mirageos-devel
>

>
------=_Part_7223_215238386.1407235385393-- --===============6774558513720904505== 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 --===============6774558513720904505==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:43:13 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:43:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcD1-0002wH-K6; Tue, 05 Aug 2014 10:43:11 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcD0-0002wC-7A for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:43:10 +0000 Received: from [193.109.254.147:53782] by server-10.bemta-14.messagelabs.com id FD/26-06615-D35B0E35; Tue, 05 Aug 2014 10:43:09 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-27.messagelabs.com!1407235385!13727512!1 X-Originating-IP: [80.12.242.129] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16157 invoked from network); 5 Aug 2014 10:43:05 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-3.tower-27.messagelabs.com with SMTP; 5 Aug 2014 10:43:05 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d65 with ME id ayj51o00W13qAZm03yj5V5; Tue, 05 Aug 2014 12:43:05 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 12:43:05 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 12:43:05 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1149091954.7224.1407235385400.JavaMail.www@wwinf1c25> In-Reply-To: <973F6395-6B7A-4CC9-8780-F9094CCCAE2F@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <973F6395-6B7A-4CC9-8780-F9094CCCAE2F@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~||~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6774558513720904505==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6774558513720904505== Content-Type: multipart/alternative; boundary="----=_Part_7223_215238386.1407235385393" ------=_Part_7223_215238386.1407235385393 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i found this page on sunxi linux mainlining : https://groups.google.com/for= um/#!searchin/linux-sunxi/boris/linux-sunxi/s3lBb01I0Js/Bem2X1wKPa4J and i = will try to inspire me. 3.14 r4 branch of linux would suffice for xen ?=20 > Message du 04/08/14 23:58 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "Thomas Leonard" , "mirageos-devel@lists.xenproject.org"= =20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 >There are several forks of the Linux kernel, and this one is probably the = Linux-Sunxi branch that adds support into a branch. =C2=A0Our xen-arm-build= er script is now using the upstream Linux kernel that has several (but not = all) of the Sunxi-specific functionality integrated into it. =C2=A0 > See=C2=A0http://linux-sunxi.org/Linux_mainlining_effort=C2=A0for more infor= mation on this. > -anil > On 4 Aug 2014, at 14:53, Gilles DALMAS wrote: > In terms of the nand, on page: https://github.com/igorpecovnik/Cubietruck= -Debian/blob/master/config/kernel.config.3.4.61 there is for example the li= ne CONFIG_SUNXI_NAND_PARTITION =3D y and this is the 3.4.61 version of the = kernel, how is it that this option does not appear in the following version= s of the kernel? if I add it manually in the config file, is it processed? >=20 >=20 >=20 >=20 > > Message du 04/08/14 15:03 > > De : "Gilles DALMAS"=20 > > A : "Thomas Leonard" , "Anil Madhavapeddy"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > > > apparently, the xen-arm-builder script solves the problem of slowness. = even without installing mirage-net-xen. >=20 >=20 >=20 >=20 > > Message du 04/08/14 13:28 > > De : "Thomas Leonard"=20 > > A : "Anil Madhavapeddy"=20 > > Copie =C3=A0 : "Gilles DALMAS" , "mirageos-devel@lists.xenproject.org"= =20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 3 August 2014 17:24, Thomas Leonard wrote: > > > On 3 August 2014 17:20, Anil Madhavapeddy wrote: > > >> On 3 Aug 2014, at 16:34, Gilles DALMAS wrote: > > >> > > >> hi, > > >> > > >> I recently compiled mirage for cubietruck. > > >> > > >> Everything works fine, but the system is extremely slow. > > >> > > >> Hi Gilles, > > >> > > >> Glad to hear you've got it up and running. Could you shed some light= about > > >> the nature of the application that is slow? > > >> > > >> If it's networking, there's a known bug at the moment [1] due to a > > >> limitation on Xen 4.4/ARM that prevents multiple mapping of pages. T= homas > > >> Leonard has just applied a backport to the SDCard image builder [2] = that > > >> fixes this issue in Xen itself, so we could remove the workaround no= w and > > >> hopefully get back to decent networking performance (is this correct= , > > >> Thomas? I haven't had a chance to rebuild my own Cubie2 yet). > > > > > > Yes, I'll rebuild the binary images at some point but for now you can > > > build from Git. With that, you can revert back to the older > > > mirage-net-xen v1.1.1 to avoid the wait after sending each packet. > >=20 > > Here are the new images: > >=20 > > http://blobs.openmirage.org/cubieboard2-xen-iso.tar.bz2 > > http://blobs.openmirage.org/cubietruck-xen-iso.tar.bz2 > >=20 > > Installation instructions are here: > >=20 > > https://github.com/mirage/xen-arm-builder > >=20 > > Remember to use mirage-net-xen v1.1.1 as well, or it will still be slow= : > >=20 > > opam pin mirage-net-xen https://github.com/mirage/mirage-net-xen.git#v1= .1.1 > >=20 > >=20 > > --=20 > > 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 > > >=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 > > ------=_Part_7223_215238386.1407235385393 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

i found this page on sunxi linux mainlining : https://groups.google.com/= forum/#!searchin/linux-sunxi/boris/linux-sunxi/s3lBb01I0Js/Bem2X1wKPa4J and= i will try to inspire me. 3.14 r4 branch of linux would suffice for xen ? =



> Message du 04/08/14 23:58
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "Thomas Leonard" <talex5@gmail.com= >, "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> Objet : Re: [MirageOS-devel] mirage os on cubietruck= nand detection
>
>There are several forks of the = Linux kernel, and this one is probably the Linux-Sunxi branch that adds sup= port into a branch. =C2=A0Our xen-arm-builder script is now using the upstr= eam Linux kernel that has several (but not all) of the Sunxi-specific funct= ionality integrated into it. =C2=A0

>
See=C2=A0ht= tp://linux-sunxi.org/Linux_mainlining_effort=C2=A0for more information = on this.

>
-anil

>
On 4 Aug 2014, at 14:53, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> In terms of the nand, on page: https://g= ithub.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kernel.config.3= .4.61 there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y a= nd this is the 3.4.61 version of the kernel, how is it that this option doe= s not appear in the following versions of the kernel? if I add it manually = in the config file, is it processed?
>
>
>
= >
>

> Message du 04/08/14 15:03
> > De : "Gilles = DALMAS" <gdalmas@wanadoo.fr>= ;
> > A : "Thomas Leonard" <talex5@gmail.com>, "Anil Madhavapeddy" <anil@recoil.org>
> > Copie =C3=A0 : "mirageos-devel@lists.xenpro= ject.org" <mi= rageos-devel@lists.xenproject.org>
> > Objet : Re: [Mirag= eOS-devel] mirage os on cubietruck nand detection
> >
>= >

> > apparently, the xen-arm-builder script solves the problem of s= lowness. even without installing mirage-net-xen.
>
>
>
>
>

> Message du 04/08/14 13:28
> > De : "Thomas = Leonard" <talex5@gmail.com>> > A : "Anil Madhavapeddy" <anil@recoil.org>
> > Copie =C3=A0 : "Gilles DALMAS" <= ;gdalmas@wanadoo.fr>, "mirageos-devel@lists.xenpro= ject.org" <mi= rageos-devel@lists.xenproject.org>
> > Objet : Re: [Mirag= eOS-devel] mirage os on cubietruck nand detection
> >
>= > On 3 August 2014 17:24, Thomas Leonard <talex5@gmail.com> wrote:
> > > On 3 August 2= 014 17:20, Anil Madhavapeddy <anil@re= coil.org> wrote:
> > >> On 3 Aug 2014, at 16:34, Gi= lles DALMAS <gdalmas@wanadoo.fr> wrote:
> > >>
> > >> hi,
> = > >>
> > >> I recently compiled mirage for cubiet= ruck.
> > >>
> > >> Everything works fine= , but the system is extremely slow.
> > >>
> > = >> Hi Gilles,
> > >>
> > >> Glad to= hear you've got it up and running. Could you shed some light about
&g= t; > >> the nature of the application that is slow?
> >= >>
> > >> If it's networking, there's a known bug a= t the moment [1] due to a
> > >> limitation on Xen 4.4/ARM= that prevents multiple mapping of pages. Thomas
> > >> Le= onard has just applied a backport to the SDCard image builder [2] that
> > >> fixes this issue in Xen itself, so we could remove the = workaround now and
> > >> hopefully get back to decent net= working performance (is this correct,
> > >> Thomas? I hav= en't had a chance to rebuild my own Cubie2 yet).
> > >
&= gt; > > Yes, I'll rebuild the binary images at some point but for now= you can
> > > build from Git. With that, you can revert back= to the older
> > > mirage-net-xen v1.1.1 to avoid the wait a= fter sending each packet.
> >
> > Here are the new i= mages:
> >
> > http://blobs.openmirage.org/cubieboard2-xen-= iso.tar.bz2
> > http://blobs.openmirage.org/cubietruck-xen-iso.tar.b= z2
> >
> > Installation instructions are here:> >
> > https://github.com/mirage/xen-arm-builder
> >
> > Remember to use mirage-net-xen v1.1.1 as well, or it will still = be slow:
> >
> > opam pin mirage-net-xen https://github.com/mir= age/mirage-net-xen.git#v1.1.1
> >
> >
>= > --
> > 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@lis= ts.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman= /listinfo/mirageos-devel
>
>
_______________________________________________
> MirageOS-devel ma= iling list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.= org/cgi-bin/mailman/listinfo/mirageos-devel
>

>
------=_Part_7223_215238386.1407235385393-- --===============6774558513720904505== 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 --===============6774558513720904505==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:46:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:46: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 1XEcFu-0002y4-W6; Tue, 05 Aug 2014 10:46:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcFt-0002xz-Or for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:46:09 +0000 Received: from [85.158.143.35:54545] by server-1.bemta-4.messagelabs.com id FE/44-05872-1F5B0E35; Tue, 05 Aug 2014 10:46:09 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-12.tower-21.messagelabs.com!1407235567!13532950!1 X-Originating-IP: [80.12.242.129] 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 27307 invoked from network); 5 Aug 2014 10:46:08 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-12.tower-21.messagelabs.com with SMTP; 5 Aug 2014 10:46:08 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d14 with ME id aym71o00b13qAZm03ym722; Tue, 05 Aug 2014 12:46:07 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 12:46:07 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 12:46:07 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1607740719.7260.1407235567473.JavaMail.www@wwinf1c25> In-Reply-To: <7627A3FE-8878-41AD-9BAF-DD5FBC31ABDE@recoil.org> References: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> <7627A3FE-8878-41AD-9BAF-DD5FBC31ABDE@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xpenology dsm domu on xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2158213684625605679==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2158213684625605679== Content-Type: multipart/alternative; boundary="----=_Part_7259_822443773.1407235567465" ------=_Part_7259_822443773.1407235567465 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ok no problem, I did not know this list existed. > Message du 05/08/14 09:44 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] xpenology dsm domu on xen >=20 > This might be more usefully sent to the xen-users list where many appliance= s like this are discussed. I'm not sure what your question is here: is some= thing not working? > -anil > On 4 Aug 2014, at 14:40, Gilles DALMAS wrote: >=20 > > Hi, > I try to install the dsm of xpenology on xen but I do not control all the= configuration xen command line. Is someone could help me to transcribe it: > =C2=A0 > - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB= RAM > - Using HVM (Other install media, during Xen VM creation). > - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian= =3Dfalse` (Makes sure virt-what coretly recognizes Xen) > - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev= /sda1` (Using Debian Live distro) > - Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` added= `vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6` > - DSM 5.0 4458 installed after booting with grub menu item gnoboot.me =E2= =80=93> install/upgrade/downgrade 4458 > =C2=A0 > =C2=A0in command line ? > =C2=A0 > at least for the introduction of the working environment. (Disc creation,= .conf parameter file) _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ------=_Part_7259_822443773.1407235567465 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


ok no problem, I did not know this list existed.


> Message du 05/08/14 09:44
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] xpenology dsm domu on xen
>
>
This might be more usefully sent to the xen-users list where many appl= iances like this are discussed. I'm not sure what your question is here: is= something not working?

>
-anil

> On 4 Aug 2014, at 14:40, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> Hi,

> I try to install the dsm of xpenology on xen but I do not control a= ll the configuration xen command line. Is someone could help me to transcri= be it:

> =C2=A0

> - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU,= 512MB RAM
> - Using HVM (Other install media, during Xen VM creati= on).
> - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platfo= rm:viridian=3Dfalse` (Makes sure virt-what coretly recognizes Xen)
>= ; - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev= /sda1` (Using Debian Live distro)
> - Modified `/boot/grub/menu_alp= ha.lst` and `/boot/grub/menu_me.lst` added `vga=3D0=C3=97318 sn=3DB3JN00=E2= =80=A6`
> - DSM 5.0 4458 installed after booting with grub menu ite= m gnoboot.me =E2=80=93> install/upgrad= e/downgrade 4458

> =C2=A0

> =C2=A0in command line ?

> =C2=A0

> at least for the introduction of the working environment. (Disc cre= ation, .conf parameter file)

_______________________________________________
>= MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/= listinfo/mirageos-devel
>
------=_Part_7259_822443773.1407235567465-- --===============2158213684625605679== 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 --===============2158213684625605679==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:46:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:46: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 1XEcFu-0002y4-W6; Tue, 05 Aug 2014 10:46:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcFt-0002xz-Or for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:46:09 +0000 Received: from [85.158.143.35:54545] by server-1.bemta-4.messagelabs.com id FE/44-05872-1F5B0E35; Tue, 05 Aug 2014 10:46:09 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-12.tower-21.messagelabs.com!1407235567!13532950!1 X-Originating-IP: [80.12.242.129] 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 27307 invoked from network); 5 Aug 2014 10:46:08 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-12.tower-21.messagelabs.com with SMTP; 5 Aug 2014 10:46:08 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d14 with ME id aym71o00b13qAZm03ym722; Tue, 05 Aug 2014 12:46:07 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 12:46:07 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 12:46:07 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1607740719.7260.1407235567473.JavaMail.www@wwinf1c25> In-Reply-To: <7627A3FE-8878-41AD-9BAF-DD5FBC31ABDE@recoil.org> References: <902643891.12894.1407159616781.JavaMail.www@wwinf1p23> <7627A3FE-8878-41AD-9BAF-DD5FBC31ABDE@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] xpenology dsm domu on xen X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2158213684625605679==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2158213684625605679== Content-Type: multipart/alternative; boundary="----=_Part_7259_822443773.1407235567465" ------=_Part_7259_822443773.1407235567465 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ok no problem, I did not know this list existed. > Message du 05/08/14 09:44 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] xpenology dsm domu on xen >=20 > This might be more usefully sent to the xen-users list where many appliance= s like this are discussed. I'm not sure what your question is here: is some= thing not working? > -anil > On 4 Aug 2014, at 14:40, Gilles DALMAS wrote: >=20 > > Hi, > I try to install the dsm of xpenology on xen but I do not control all the= configuration xen command line. Is someone could help me to transcribe it: > =C2=A0 > - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU, 512MB= RAM > - Using HVM (Other install media, during Xen VM creation). > - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platform:viridian= =3Dfalse` (Makes sure virt-what coretly recognizes Xen) > - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev= /sda1` (Using Debian Live distro) > - Modified `/boot/grub/menu_alpha.lst` and `/boot/grub/menu_me.lst` added= `vga=3D0=C3=97318 sn=3DB3JN00=E2=80=A6` > - DSM 5.0 4458 installed after booting with grub menu item gnoboot.me =E2= =80=93> install/upgrade/downgrade 4458 > =C2=A0 > =C2=A0in command line ? > =C2=A0 > at least for the introduction of the working environment. (Disc creation,= .conf parameter file) _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ------=_Part_7259_822443773.1407235567465 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


ok no problem, I did not know this list existed.


> Message du 05/08/14 09:44
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] xpenology dsm domu on xen
>
>
This might be more usefully sent to the xen-users list where many appl= iances like this are discussed. I'm not sure what your question is here: is= something not working?

>
-anil

> On 4 Aug 2014, at 14:40, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> Hi,

> I try to install the dsm of xpenology on xen but I do not control a= ll the configuration xen command line. Is someone could help me to transcri= be it:

> =C2=A0

> - Using 32MB primary boot disk, and 8GB second system disk, 2 VCPU,= 512MB RAM
> - Using HVM (Other install media, during Xen VM creati= on).
> - Disabled viridian `xe vm-param-set uuid=3D=E2=80=A6 platfo= rm:viridian=3Dfalse` (Makes sure virt-what coretly recognizes Xen)
>= ; - gnoBoot image installed using `dd if=3Dgnoboot-alpha-vfat.img of=3D/dev= /sda1` (Using Debian Live distro)
> - Modified `/boot/grub/menu_alp= ha.lst` and `/boot/grub/menu_me.lst` added `vga=3D0=C3=97318 sn=3DB3JN00=E2= =80=A6`
> - DSM 5.0 4458 installed after booting with grub menu ite= m gnoboot.me =E2=80=93> install/upgrad= e/downgrade 4458

> =C2=A0

> =C2=A0in command line ?

> =C2=A0

> at least for the introduction of the working environment. (Disc cre= ation, .conf parameter file)

_______________________________________________
>= MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/= listinfo/mirageos-devel
>
------=_Part_7259_822443773.1407235567465-- --===============2158213684625605679== 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 --===============2158213684625605679==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:52:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:52: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 1XEcLg-00035q-MJ; Tue, 05 Aug 2014 10:52:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcLf-00035i-EP for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:52:07 +0000 Received: from [85.158.139.211:33542] by server-7.bemta-5.messagelabs.com id 2D/07-30869-657B0E35; Tue, 05 Aug 2014 10:52:06 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-8.tower-206.messagelabs.com!1407235925!11930710!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16807 invoked from network); 5 Aug 2014 10:52:06 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-8.tower-206.messagelabs.com with SMTP; 5 Aug 2014 10:52:06 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d02 with ME id ays51o00P13qAZm03ys5YU; Tue, 05 Aug 2014 12:52:05 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 12:52:05 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 12:52:05 +0200 (CEST) From: Gilles DALMAS To: "Vincent B." , mirageos-devel@lists.xenproject.org Message-ID: <745431699.7388.1407235925581.JavaMail.www@wwinf1c25> In-Reply-To: <53E09685.7030304@luminar.eu.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-REPLYTO: |~| Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3694366837115432051==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3694366837115432051== Content-Type: multipart/alternative; boundary="----=_Part_7387_1605769764.1407235925574" ------=_Part_7387_1605769764.1407235925574 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable However, Cubian and other images, provided on the site of cubietech, handle= s very well this feature. I'm going to ask this question on their website to find out what changes th= ey made to manage the nand. =C2=A0 =C2=A0 > Message du 05/08/14 10:32 > De : "Vincent B."=20 > A : mirageos-devel@lists.xenproject.org > Copie =C3=A0 :=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 04/08/2014 15:53, Gilles DALMAS wrote: > > In terms of the nand, on page: > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61 > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and thi= s is the > > 3.4.61 version of the kernel, how is it that this option does not appea= r in the > > following versions of the kernel? if I add it manually in the config fi= le, is it > > processed? > >=20 >=20 > There is no sunxi NAND support yet for the mainline linux Kernel. Work is > ongoing, though. >=20 > Vincent >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ------=_Part_7387_1605769764.1407235925574 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

However, Cubian and other images, provided on the site of cubietech, han= dles very well this feature.
I'm going to ask this question on their = website to find out what changes they made to manage the nand.

=C2=A0

=C2=A0

> Message du 05/08/14 10:32
> De : "Vincent B." = <vb@luminar.eu.org>
> A : mirageos-devel@lists.xenproject.org=
> Copie =C3=A0 :
> Objet : Re: [MirageOS-devel] mirage os= on cubietruck nand detection
>
> On 04/08/2014 15:53, Gil= les DALMAS wrote:
> > In terms of the nand, on page:
> &= gt; https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61
> > there is for example the line CONFIG_SUNX= I_NAND_PARTITION =3D y and this is the
> > 3.4.61 version of the= kernel, how is it that this option does not appear in the
> > f= ollowing versions of the kernel? if I add it manually in the config file, i= s it
> > processed?
> >
>
> There i= s no sunxi NAND support yet for the mainline linux Kernel. Work is
>= ; ongoing, though.
>
> Vincent
>
> ______= _________________________________________
> MirageOS-devel mailing = list
> MirageOS-devel@lists.xenproject.org
> http://lists.x= enproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> ------=_Part_7387_1605769764.1407235925574-- --===============3694366837115432051== 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 --===============3694366837115432051==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 10:52:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 10:52: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 1XEcLg-00035q-MJ; Tue, 05 Aug 2014 10:52:08 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcLf-00035i-EP for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 10:52:07 +0000 Received: from [85.158.139.211:33542] by server-7.bemta-5.messagelabs.com id 2D/07-30869-657B0E35; Tue, 05 Aug 2014 10:52:06 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-8.tower-206.messagelabs.com!1407235925!11930710!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16807 invoked from network); 5 Aug 2014 10:52:06 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-8.tower-206.messagelabs.com with SMTP; 5 Aug 2014 10:52:06 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d02 with ME id ays51o00P13qAZm03ys5YU; Tue, 05 Aug 2014 12:52:05 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 12:52:05 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 12:52:05 +0200 (CEST) From: Gilles DALMAS To: "Vincent B." , mirageos-devel@lists.xenproject.org Message-ID: <745431699.7388.1407235925581.JavaMail.www@wwinf1c25> In-Reply-To: <53E09685.7030304@luminar.eu.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-REPLYTO: |~| Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3694366837115432051==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3694366837115432051== Content-Type: multipart/alternative; boundary="----=_Part_7387_1605769764.1407235925574" ------=_Part_7387_1605769764.1407235925574 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable However, Cubian and other images, provided on the site of cubietech, handle= s very well this feature. I'm going to ask this question on their website to find out what changes th= ey made to manage the nand. =C2=A0 =C2=A0 > Message du 05/08/14 10:32 > De : "Vincent B."=20 > A : mirageos-devel@lists.xenproject.org > Copie =C3=A0 :=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 04/08/2014 15:53, Gilles DALMAS wrote: > > In terms of the nand, on page: > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61 > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and thi= s is the > > 3.4.61 version of the kernel, how is it that this option does not appea= r in the > > following versions of the kernel? if I add it manually in the config fi= le, is it > > processed? > >=20 >=20 > There is no sunxi NAND support yet for the mainline linux Kernel. Work is > ongoing, though. >=20 > Vincent >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ------=_Part_7387_1605769764.1407235925574 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

However, Cubian and other images, provided on the site of cubietech, han= dles very well this feature.
I'm going to ask this question on their = website to find out what changes they made to manage the nand.

=C2=A0

=C2=A0

> Message du 05/08/14 10:32
> De : "Vincent B." = <vb@luminar.eu.org>
> A : mirageos-devel@lists.xenproject.org=
> Copie =C3=A0 :
> Objet : Re: [MirageOS-devel] mirage os= on cubietruck nand detection
>
> On 04/08/2014 15:53, Gil= les DALMAS wrote:
> > In terms of the nand, on page:
> &= gt; https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61
> > there is for example the line CONFIG_SUNX= I_NAND_PARTITION =3D y and this is the
> > 3.4.61 version of the= kernel, how is it that this option does not appear in the
> > f= ollowing versions of the kernel? if I add it manually in the config file, i= s it
> > processed?
> >
>
> There i= s no sunxi NAND support yet for the mainline linux Kernel. Work is
>= ; ongoing, though.
>
> Vincent
>
> ______= _________________________________________
> MirageOS-devel mailing = list
> MirageOS-devel@lists.xenproject.org
> http://lists.x= enproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> ------=_Part_7387_1605769764.1407235925574-- --===============3694366837115432051== 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 --===============3694366837115432051==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 11:12:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 11:12: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 1XEcf3-0003so-Cd; Tue, 05 Aug 2014 11:12:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcf1-0003sf-Mw for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 11:12:07 +0000 Received: from [85.158.143.35:18729] by server-1.bemta-4.messagelabs.com id 81/D3-05872-70CB0E35; Tue, 05 Aug 2014 11:12:07 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1407237125!13499952!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27327 invoked from network); 5 Aug 2014 11:12:05 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-21.messagelabs.com with SMTP; 5 Aug 2014 11:12:05 -0000 Received: (qmail 31552 invoked by uid 634); 5 Aug 2014 11:12:05 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from dab-glb1-h-33-7.dab.02.net (HELO [10.4.17.51]) (82.132.218.187) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 05 Aug 2014 12:12:01 +0100 References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> <745431699.7388.1407235925581.JavaMail.www@wwinf1c25> Mime-Version: 1.0 (1.0) In-Reply-To: <745431699.7388.1407235925581.JavaMail.www@wwinf1c25> Message-Id: X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Tue, 5 Aug 2014 12:11:53 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6715952620667924275==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6715952620667924275== Content-Type: multipart/alternative; boundary=Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446 Content-Transfer-Encoding: 7bit --Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable They all use a forked kernel. Given how new Xen ARM is, I'd be surprised if a= n old 3.4 dom0 branch worked without issue. It's probably easier to forward p= ort the NAND support to the 3.17 Linux tree. > On 5 Aug 2014, at 11:52, Gilles DALMAS wrote: >=20 > However, Cubian and other images, provided on the site of cubietech, handl= es very well this feature. > I'm going to ask this question on their website to find out what changes t= hey made to manage the nand. >=20 > =20 >=20 > =20 >=20 > > Message du 05/08/14 10:32 > > De : "Vincent B." > > A : mirageos-devel@lists.xenproject.org > > Copie =C3=A0 :=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 04/08/2014 15:53, Gilles DALMAS wrote: > > > In terms of the nand, on page: > > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/k= ernel.config.3.4.61 > > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and th= is is the > > > 3.4.61 version of the kernel, how is it that this option does not appe= ar in the > > > following versions of the kernel? if I add it manually in the config f= ile, is it > > > processed? > > >=20 > >=20 > > There is no sunxi NAND support yet for the mainline linux Kernel. Work i= s > > ongoing, though. > >=20 > > Vincent > >=20 > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
They all use a forked kernel. Given ho= w new Xen ARM is, I'd be surprised if an old 3.4 dom0 branch worked without i= ssue. It's probably easier to forward port the NAND support to the 3.17 Linu= x tree.

On 5 Aug 2014, at 11:52, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

However, Cubian and other images, provided o= n the site of cubietech, handles very well this feature.
I'm going to as= k this question on their website to find out what changes they made to manag= e the nand.

 

 

> Message du 05/08/14 10:32
> De : "Vincent B." <= vb@luminar.eu.org>
> A : <= a href=3D"mailto:mirageos-devel@lists.xenproject.org">mirageos-devel@lists.x= enproject.org
> Copie =C3=A0 :
> Objet : Re: [MirageOS-deve= l] mirage os on cubietruck nand detection
>
> On 04/08/2014 15:= 53, Gilles DALMAS wrote:
> > In terms of the nand, on page:
>= > https://github.com/igorpecovnik/Cubietruck-D= ebian/blob/master/config/kernel.config.3.4.61
> > there is for e= xample the line CONFIG_SUNXI_NAND_PARTITION =3D y and this is the
> &g= t; 3.4.61 version of the kernel, how is it that this option does not appear i= n the
> > following versions of the kernel? if I add it manually in= the config file, is it
> > processed?
> >
>
&g= t; There is no sunxi NAND support yet for the mainline linux Kernel. Work is=
> ongoing, though.
>
> Vincent
>
> ________= _______________________________________
> MirageOS-devel mailing list<= br>> MirageOS-deve= l@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/m= ailman/listinfo/mirageos-devel
>
<= blockquote type=3D"cite">
________________________________________= _______
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject= .org
http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel
= --Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446-- --===============6715952620667924275== 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 --===============6715952620667924275==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 11:12:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 11:12: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 1XEcf3-0003so-Cd; Tue, 05 Aug 2014 11:12:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEcf1-0003sf-Mw for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 11:12:07 +0000 Received: from [85.158.143.35:18729] by server-1.bemta-4.messagelabs.com id 81/D3-05872-70CB0E35; Tue, 05 Aug 2014 11:12:07 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1407237125!13499952!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.8 required=7.0 tests=HTML_40_50,HTML_MESSAGE, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27327 invoked from network); 5 Aug 2014 11:12:05 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-21.messagelabs.com with SMTP; 5 Aug 2014 11:12:05 -0000 Received: (qmail 31552 invoked by uid 634); 5 Aug 2014 11:12:05 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from dab-glb1-h-33-7.dab.02.net (HELO [10.4.17.51]) (82.132.218.187) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 05 Aug 2014 12:12:01 +0100 References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> <745431699.7388.1407235925581.JavaMail.www@wwinf1c25> Mime-Version: 1.0 (1.0) In-Reply-To: <745431699.7388.1407235925581.JavaMail.www@wwinf1c25> Message-Id: X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Tue, 5 Aug 2014 12:11:53 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6715952620667924275==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6715952620667924275== Content-Type: multipart/alternative; boundary=Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446 Content-Transfer-Encoding: 7bit --Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable They all use a forked kernel. Given how new Xen ARM is, I'd be surprised if a= n old 3.4 dom0 branch worked without issue. It's probably easier to forward p= ort the NAND support to the 3.17 Linux tree. > On 5 Aug 2014, at 11:52, Gilles DALMAS wrote: >=20 > However, Cubian and other images, provided on the site of cubietech, handl= es very well this feature. > I'm going to ask this question on their website to find out what changes t= hey made to manage the nand. >=20 > =20 >=20 > =20 >=20 > > Message du 05/08/14 10:32 > > De : "Vincent B." > > A : mirageos-devel@lists.xenproject.org > > Copie =C3=A0 :=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 04/08/2014 15:53, Gilles DALMAS wrote: > > > In terms of the nand, on page: > > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/k= ernel.config.3.4.61 > > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and th= is is the > > > 3.4.61 version of the kernel, how is it that this option does not appe= ar in the > > > following versions of the kernel? if I add it manually in the config f= ile, is it > > > processed? > > >=20 > >=20 > > There is no sunxi NAND support yet for the mainline linux Kernel. Work i= s > > ongoing, though. > >=20 > > Vincent > >=20 > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
They all use a forked kernel. Given ho= w new Xen ARM is, I'd be surprised if an old 3.4 dom0 branch worked without i= ssue. It's probably easier to forward port the NAND support to the 3.17 Linu= x tree.

On 5 Aug 2014, at 11:52, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

However, Cubian and other images, provided o= n the site of cubietech, handles very well this feature.
I'm going to as= k this question on their website to find out what changes they made to manag= e the nand.

 

 

> Message du 05/08/14 10:32
> De : "Vincent B." <= vb@luminar.eu.org>
> A : <= a href=3D"mailto:mirageos-devel@lists.xenproject.org">mirageos-devel@lists.x= enproject.org
> Copie =C3=A0 :
> Objet : Re: [MirageOS-deve= l] mirage os on cubietruck nand detection
>
> On 04/08/2014 15:= 53, Gilles DALMAS wrote:
> > In terms of the nand, on page:
>= > https://github.com/igorpecovnik/Cubietruck-D= ebian/blob/master/config/kernel.config.3.4.61
> > there is for e= xample the line CONFIG_SUNXI_NAND_PARTITION =3D y and this is the
> &g= t; 3.4.61 version of the kernel, how is it that this option does not appear i= n the
> > following versions of the kernel? if I add it manually in= the config file, is it
> > processed?
> >
>
&g= t; There is no sunxi NAND support yet for the mainline linux Kernel. Work is=
> ongoing, though.
>
> Vincent
>
> ________= _______________________________________
> MirageOS-devel mailing list<= br>> MirageOS-deve= l@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/m= ailman/listinfo/mirageos-devel
>
<= blockquote type=3D"cite">
________________________________________= _______
MirageOS-devel mailing list
MirageOS-devel@lists.xenproject= .org
http://lists.xenproject.org/cgi-bin/mailman/lis= tinfo/mirageos-devel
= --Apple-Mail-5763AE4D-49EF-403B-BF35-8AD3DF6ED446-- --===============6715952620667924275== 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 --===============6715952620667924275==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 14:52:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 14:52: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 1XEg5y-0006PU-IY; Tue, 05 Aug 2014 14:52:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEg5x-0006PM-1c for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 14:52:09 +0000 Received: from [85.158.139.211:41059] by server-1.bemta-5.messagelabs.com id 47/FC-17892-89FE0E35; Tue, 05 Aug 2014 14:52:08 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-13.tower-206.messagelabs.com!1407250327!12033470!1 X-Originating-IP: [80.12.242.129] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10075 invoked from network); 5 Aug 2014 14:52:07 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-13.tower-206.messagelabs.com with SMTP; 5 Aug 2014 14:52:07 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d30 with ME id b2s71o00L13qAZm032s7iu; Tue, 05 Aug 2014 16:52:07 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 16:52:07 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 16:52:07 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <1185649976.12333.1407250327495.JavaMail.www@wwinf1c25> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] iptables into xen-arm-builder X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1751528422558302902==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1751528422558302902== Content-Type: multipart/alternative; boundary="----=_Part_12332_1150284610.1407250327495" ------=_Part_12332_1150284610.1407250327495 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hello, Je pense qu'il ya un probl=C3=A8me avec iptables dans votre script. certain= es options sont d=C3=A9sactiv=C3=A9es dans le fichier de configuration:. NE= TFILTER .... donc, le module iptables ne fonctionne pas correctement. ------=_Part_12332_1150284610.1407250327495 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

hello,

Je pense qu'il ya un probl=C3=A8me avec iptables dans votre script. cert= aines options sont d=C3=A9sactiv=C3=A9es dans le fichier de configuration:.= NETFILTER .... donc, le module iptables ne fonctionne pas correctement. ------=_Part_12332_1150284610.1407250327495-- --===============1751528422558302902== 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 --===============1751528422558302902==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 14:52:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 14:52: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 1XEg5y-0006PU-IY; Tue, 05 Aug 2014 14:52:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEg5x-0006PM-1c for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 14:52:09 +0000 Received: from [85.158.139.211:41059] by server-1.bemta-5.messagelabs.com id 47/FC-17892-89FE0E35; Tue, 05 Aug 2014 14:52:08 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-13.tower-206.messagelabs.com!1407250327!12033470!1 X-Originating-IP: [80.12.242.129] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10075 invoked from network); 5 Aug 2014 14:52:07 -0000 Received: from smtp07.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.129) by server-13.tower-206.messagelabs.com with SMTP; 5 Aug 2014 14:52:07 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d30 with ME id b2s71o00L13qAZm032s7iu; Tue, 05 Aug 2014 16:52:07 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 16:52:07 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 16:52:07 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <1185649976.12333.1407250327495.JavaMail.www@wwinf1c25> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] iptables into xen-arm-builder X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1751528422558302902==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1751528422558302902== Content-Type: multipart/alternative; boundary="----=_Part_12332_1150284610.1407250327495" ------=_Part_12332_1150284610.1407250327495 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hello, Je pense qu'il ya un probl=C3=A8me avec iptables dans votre script. certain= es options sont d=C3=A9sactiv=C3=A9es dans le fichier de configuration:. NE= TFILTER .... donc, le module iptables ne fonctionne pas correctement. ------=_Part_12332_1150284610.1407250327495 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

hello,

Je pense qu'il ya un probl=C3=A8me avec iptables dans votre script. cert= aines options sont d=C3=A9sactiv=C3=A9es dans le fichier de configuration:.= NETFILTER .... donc, le module iptables ne fonctionne pas correctement. ------=_Part_12332_1150284610.1407250327495-- --===============1751528422558302902== 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 --===============1751528422558302902==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 14:53:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 14:53: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 1XEg7I-0006SK-Oc; Tue, 05 Aug 2014 14:53:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEg7G-0006SF-Vg for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 14:53:31 +0000 Received: from [85.158.137.68:18301] by server-11.bemta-3.messagelabs.com id 09/E2-04507-9EFE0E35; Tue, 05 Aug 2014 14:53:29 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-14.tower-31.messagelabs.com!1407250409!9550296!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27545 invoked from network); 5 Aug 2014 14:53:29 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-14.tower-31.messagelabs.com with SMTP; 5 Aug 2014 14:53:29 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d36 with ME id b2tU1o00F13qAZm032tUkB; Tue, 05 Aug 2014 16:53:28 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 16:53:28 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 16:53:28 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <620953433.12363.1407250408850.JavaMail.www@wwinf1c25> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] iptables into xen-arm-builder X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8417709155167614607==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8417709155167614607== Content-Type: multipart/alternative; boundary="----=_Part_12362_455037200.1407250408843" ------=_Part_12362_455037200.1407250408843 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sorry, i think there is a problem with iptables into your script. some options are disabled into the .config file : NETFILTER ...., therefore, iptables module doesn't work correctly. ------=_Part_12362_455037200.1407250408843 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

sorry,

i think there is a problem with iptables into your script. some options are disabled into the .config file : NETFILTER ...., therefore, iptables module doesn't work correctly.

------=_Part_12362_455037200.1407250408843-- --===============8417709155167614607== 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 --===============8417709155167614607==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 14:53:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 14:53: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 1XEg7I-0006SK-Oc; Tue, 05 Aug 2014 14:53:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEg7G-0006SF-Vg for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 14:53:31 +0000 Received: from [85.158.137.68:18301] by server-11.bemta-3.messagelabs.com id 09/E2-04507-9EFE0E35; Tue, 05 Aug 2014 14:53:29 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-14.tower-31.messagelabs.com!1407250409!9550296!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27545 invoked from network); 5 Aug 2014 14:53:29 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-14.tower-31.messagelabs.com with SMTP; 5 Aug 2014 14:53:29 -0000 Received: from wwinf1c25 ([10.223.79.49]) by mwinf5d36 with ME id b2tU1o00F13qAZm032tUkB; Tue, 05 Aug 2014 16:53:28 +0200 X-ME-Helo: wwinf1c25 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Tue, 05 Aug 2014 16:53:28 +0200 X-ME-IP: 90.15.1.71 Date: Tue, 5 Aug 2014 16:53:28 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <620953433.12363.1407250408850.JavaMail.www@wwinf1c25> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] iptables into xen-arm-builder X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8417709155167614607==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8417709155167614607== Content-Type: multipart/alternative; boundary="----=_Part_12362_455037200.1407250408843" ------=_Part_12362_455037200.1407250408843 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sorry, i think there is a problem with iptables into your script. some options are disabled into the .config file : NETFILTER ...., therefore, iptables module doesn't work correctly. ------=_Part_12362_455037200.1407250408843 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

sorry,

i think there is a problem with iptables into your script. some options are disabled into the .config file : NETFILTER ...., therefore, iptables module doesn't work correctly.

------=_Part_12362_455037200.1407250408843-- --===============8417709155167614607== 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 --===============8417709155167614607==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 15:27:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 15:27:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEgeO-0007gM-S7; Tue, 05 Aug 2014 15:27:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEgeN-0007gF-0I for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 15:27:43 +0000 Received: from [85.158.137.68:55619] by server-4.bemta-3.messagelabs.com id D1/1B-18709-EE7F0E35; Tue, 05 Aug 2014 15:27:42 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-8.tower-31.messagelabs.com!1407252461!12012542!1 X-Originating-IP: [93.159.202.52] 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 14396 invoked from network); 5 Aug 2014 15:27:41 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-8.tower-31.messagelabs.com with SMTP; 5 Aug 2014 15:27:41 -0000 Received: (qmail 29967 invoked from network); 5 Aug 2014 15:25:45 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 5 Aug 2014 15:25:45 -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 27703-07 for ; Tue, 5 Aug 2014 16:25:37 +0100 (BST) Received: (qmail 29770 invoked by uid 599); 5 Aug 2014 15:25: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; Tue, 05 Aug 2014 16:25:37 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp4.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XEgcK-00053u-DD for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:25:36 +0100 Message-ID: <53E0F76F.4080303@nottingham.ac.uk> Date: Tue, 05 Aug 2014 16:25:35 +0100 From: Masoud Koleini 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-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Subject: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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, I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? Thanks. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 15:27:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 15:27:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEgeO-0007gM-S7; Tue, 05 Aug 2014 15:27:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEgeN-0007gF-0I for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 15:27:43 +0000 Received: from [85.158.137.68:55619] by server-4.bemta-3.messagelabs.com id D1/1B-18709-EE7F0E35; Tue, 05 Aug 2014 15:27:42 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-8.tower-31.messagelabs.com!1407252461!12012542!1 X-Originating-IP: [93.159.202.52] 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 14396 invoked from network); 5 Aug 2014 15:27:41 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-8.tower-31.messagelabs.com with SMTP; 5 Aug 2014 15:27:41 -0000 Received: (qmail 29967 invoked from network); 5 Aug 2014 15:25:45 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 5 Aug 2014 15:25:45 -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 27703-07 for ; Tue, 5 Aug 2014 16:25:37 +0100 (BST) Received: (qmail 29770 invoked by uid 599); 5 Aug 2014 15:25: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; Tue, 05 Aug 2014 16:25:37 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp4.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XEgcK-00053u-DD for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:25:36 +0100 Message-ID: <53E0F76F.4080303@nottingham.ac.uk> Date: Tue, 05 Aug 2014 16:25:35 +0100 From: Masoud Koleini 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-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Subject: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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, I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? Thanks. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 15:44:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 15:44: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 1XEguB-0000Gn-LC; Tue, 05 Aug 2014 15:44:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEgu8-0000Ft-TP for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 15:44:01 +0000 Received: from [85.158.143.35:35214] by server-3.bemta-4.messagelabs.com id 9D/E9-06192-DBBF0E35; Tue, 05 Aug 2014 15:43:57 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1407253436!13624145!1 X-Originating-IP: [74.125.82.51] 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 9567 invoked from network); 5 Aug 2014 15:43:56 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Aug 2014 15:43:56 -0000 Received: by mail-wg0-f51.google.com with SMTP id b13so1229450wgh.22 for ; Tue, 05 Aug 2014 08:43:55 -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=WCN/f163Ecf5cugtEYdbdwhvUBQs7Tww31s6uAclXBg=; b=FFkRAnWlRDCsHA6CoBa3MU4TocTMU1Cp8wqVBYnLHDtK+aCnIMs1uIpPJodQoJYSx4 r6qGX8hxwCYM6idLf1Iz75VmsRbpkEychAETwQ1pkWt41nMp1sSM1RsN/P8x6ii+Cl6r A0KMbjg8iEiDVMtncrU0XMYc+dR5Cjkh21k4fdsDdQmkt183ReuLgVnaJwUQ6oYKfjQX aaKPaNw96tmJkC0bo3co7a1Ld3m+nGhkDLwHdUSvhwaEJiiQz3OWrAfHqQ5vKXPu0/wK PGZ9EWYhXoxvslg5QhDdJPP3MaCdcp+9n3XuCJhLU2HS7fhLDAGZvqZmpmbHiau/q7AP l+Uw== X-Received: by 10.180.94.34 with SMTP id cz2mr41059125wib.74.1407253433799; Tue, 05 Aug 2014 08:43:53 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ch5sm5003172wjb.18.2014.08.05.08.43.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 08:43:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <53E0F76F.4080303@nottingham.ac.uk> Date: Tue, 5 Aug 2014 16:43:48 +0100 Message-Id: <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> References: <53E0F76F.4080303@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? Which error do you have ? Which version of mirage are you running ? > > Thanks. > > > This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 15:44:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 15:44: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 1XEguB-0000Gn-LC; Tue, 05 Aug 2014 15:44:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEgu8-0000Ft-TP for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 15:44:01 +0000 Received: from [85.158.143.35:35214] by server-3.bemta-4.messagelabs.com id 9D/E9-06192-DBBF0E35; Tue, 05 Aug 2014 15:43:57 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1407253436!13624145!1 X-Originating-IP: [74.125.82.51] 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 9567 invoked from network); 5 Aug 2014 15:43:56 -0000 Received: from mail-wg0-f51.google.com (HELO mail-wg0-f51.google.com) (74.125.82.51) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 5 Aug 2014 15:43:56 -0000 Received: by mail-wg0-f51.google.com with SMTP id b13so1229450wgh.22 for ; Tue, 05 Aug 2014 08:43:55 -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=WCN/f163Ecf5cugtEYdbdwhvUBQs7Tww31s6uAclXBg=; b=FFkRAnWlRDCsHA6CoBa3MU4TocTMU1Cp8wqVBYnLHDtK+aCnIMs1uIpPJodQoJYSx4 r6qGX8hxwCYM6idLf1Iz75VmsRbpkEychAETwQ1pkWt41nMp1sSM1RsN/P8x6ii+Cl6r A0KMbjg8iEiDVMtncrU0XMYc+dR5Cjkh21k4fdsDdQmkt183ReuLgVnaJwUQ6oYKfjQX aaKPaNw96tmJkC0bo3co7a1Ld3m+nGhkDLwHdUSvhwaEJiiQz3OWrAfHqQ5vKXPu0/wK PGZ9EWYhXoxvslg5QhDdJPP3MaCdcp+9n3XuCJhLU2HS7fhLDAGZvqZmpmbHiau/q7AP l+Uw== X-Received: by 10.180.94.34 with SMTP id cz2mr41059125wib.74.1407253433799; Tue, 05 Aug 2014 08:43:53 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id ch5sm5003172wjb.18.2014.08.05.08.43.52 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 08:43:53 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <53E0F76F.4080303@nottingham.ac.uk> Date: Tue, 5 Aug 2014 16:43:48 +0100 Message-Id: <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> References: <53E0F76F.4080303@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? Which error do you have ? Which version of mirage are you running ? > > Thanks. > > > This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 15:53:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 15:53: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 1XEh3G-00012D-Q8; Tue, 05 Aug 2014 15:53:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEh3F-00011t-F6 for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 15:53:25 +0000 Received: from [85.158.139.211:20608] by server-11.bemta-5.messagelabs.com id D8/98-31757-4FDF0E35; Tue, 05 Aug 2014 15:53:24 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-11.tower-206.messagelabs.com!1407254004!7891095!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 2347 invoked from network); 5 Aug 2014 15:53:24 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-11.tower-206.messagelabs.com with SMTP; 5 Aug 2014 15:53:24 -0000 Received: (qmail 17269 invoked from network); 5 Aug 2014 15:48:35 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 5 Aug 2014 15:48:35 -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 15655-08 for ; Tue, 5 Aug 2014 16:48:35 +0100 (BST) Received: (qmail 17257 invoked by uid 599); 5 Aug 2014 15:48:35 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 05 Aug 2014 16:48:35 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp4.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XEgyF-00068g-75; Tue, 05 Aug 2014 16:48:15 +0100 Message-ID: <53E0FCBF.4030908@nottingham.ac.uk> Date: Tue, 05 Aug 2014 16:48:15 +0100 From: Masoud Koleini 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: <53E0F76F.4080303@nottingham.ac.uk> <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> In-Reply-To: <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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 Mirage version is 1.2.0 The error is: Mirage Error: Unbound value tap1 Mirage Did you mean tap0? On 05/08/14 16:43, Thomas Gazagnaire wrote: >> I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? > Which error do you have ? Which version of mirage are you running ? > > >> Thanks. >> >> >> 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 -- Masoud Koleini Research Fellow Horizon Digital Economy Research University of Nottingham Innovation Park Nottingham NG7 2TU This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 15:53:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 15:53: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 1XEh3G-00012D-Q8; Tue, 05 Aug 2014 15:53:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEh3F-00011t-F6 for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 15:53:25 +0000 Received: from [85.158.139.211:20608] by server-11.bemta-5.messagelabs.com id D8/98-31757-4FDF0E35; Tue, 05 Aug 2014 15:53:24 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-11.tower-206.messagelabs.com!1407254004!7891095!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 2347 invoked from network); 5 Aug 2014 15:53:24 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-11.tower-206.messagelabs.com with SMTP; 5 Aug 2014 15:53:24 -0000 Received: (qmail 17269 invoked from network); 5 Aug 2014 15:48:35 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 5 Aug 2014 15:48:35 -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 15655-08 for ; Tue, 5 Aug 2014 16:48:35 +0100 (BST) Received: (qmail 17257 invoked by uid 599); 5 Aug 2014 15:48:35 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 05 Aug 2014 16:48:35 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp4.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XEgyF-00068g-75; Tue, 05 Aug 2014 16:48:15 +0100 Message-ID: <53E0FCBF.4030908@nottingham.ac.uk> Date: Tue, 05 Aug 2014 16:48:15 +0100 From: Masoud Koleini 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: <53E0F76F.4080303@nottingham.ac.uk> <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> In-Reply-To: <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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 Mirage version is 1.2.0 The error is: Mirage Error: Unbound value tap1 Mirage Did you mean tap0? On 05/08/14 16:43, Thomas Gazagnaire wrote: >> I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? > Which error do you have ? Which version of mirage are you running ? > > >> Thanks. >> >> >> 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 -- Masoud Koleini Research Fellow Horizon Digital Economy Research University of Nottingham Innovation Park Nottingham NG7 2TU This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 16:49:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 16:49: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 1XEhvs-0003S2-Ch; Tue, 05 Aug 2014 16:49:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEhvr-0003Rx-59 for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:49:51 +0000 Received: from [193.109.254.147:15484] by server-6.bemta-14.messagelabs.com id C1/7F-31278-E2B01E35; Tue, 05 Aug 2014 16:49:50 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1407257389!13915924!1 X-Originating-IP: [209.85.212.169] 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 27519 invoked from network); 5 Aug 2014 16:49:49 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Aug 2014 16:49:49 -0000 Received: by mail-wi0-f169.google.com with SMTP id n3so8218971wiv.0 for ; Tue, 05 Aug 2014 09:49:48 -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=xrN2kMRXOVO4cUFC/iZJ0xTl0inErNGdV3iia4N+tNw=; b=hdGO1zfEIrmlFUNC3F/InjXtS7P0q1IU1Pfvg9SzWRMM85QmAT8gSXgwn8KCHWvqqk J0asW04CDh6YmS3zCuVCBI5y9pdjvxpE1oItqfObOiXucF9ItYLohKKefyT+Zq2y3wby RsUpNi+T1kQ4tGaMgp8vTZPqQIuH5rZh/M0NA7COtftWhvwcLnFlUTanwAdEzp2lgASu 7gp8ks0mGhVGnUVf/C0yEcAh+HzuSzDoUBLdk50v8tUpQ6QODslKRYOrB1pszu+t7Q+g JUX6S9MLSfWDXbT4MMZxo6D4w4/j9MJupyyTtI16K6GzHAwsQpTrofkOQk7JXcbLkKRA 2sTg== X-Received: by 10.194.22.194 with SMTP id g2mr7736546wjf.30.1407257388852; Tue, 05 Aug 2014 09:49:48 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id dc3sm1880385wjc.27.2014.08.05.09.49.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 09:49:47 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <53E0FCBF.4030908@nottingham.ac.uk> Date: Tue, 5 Aug 2014 17:49:46 +0100 Message-Id: <23B9ADDC-83EF-469E-8A01-2F44F05D1812@gazagnaire.org> References: <53E0F76F.4080303@nottingham.ac.uk> <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> <53E0FCBF.4030908@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org What I'm guessing in your cryptic error bug report is that you've simply replaced the variable tap0 by the variable tap1 in the config.ml. However, this file is a normal OCaml program, so it needs to be lexically scoped: tap1 is the name of a variable which needs to be created somewhere. The tap0 variable is defined in https://github.com/mirage/mirage/blob/master/lib/mirage.mli#L209. I think in your case you can use (netfif "tap1") instead of tap0. Best, Thomas On 5 Aug 2014, at 16:48, Masoud Koleini wrote: > Mirage version is 1.2.0 > > The error is: > > Mirage Error: Unbound value tap1 > Mirage Did you mean tap0? > > > On 05/08/14 16:43, Thomas Gazagnaire wrote: >>> I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? >> Which error do you have ? Which version of mirage are you running ? >> >> >>> Thanks. >>> >>> >>> 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 > > -- > Masoud Koleini > Research Fellow > Horizon Digital Economy Research > University of Nottingham Innovation Park > Nottingham > NG7 2TU > > This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. > > > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 16:49:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 16:49: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 1XEhvs-0003S2-Ch; Tue, 05 Aug 2014 16:49:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEhvr-0003Rx-59 for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:49:51 +0000 Received: from [193.109.254.147:15484] by server-6.bemta-14.messagelabs.com id C1/7F-31278-E2B01E35; Tue, 05 Aug 2014 16:49:50 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1407257389!13915924!1 X-Originating-IP: [209.85.212.169] 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 27519 invoked from network); 5 Aug 2014 16:49:49 -0000 Received: from mail-wi0-f169.google.com (HELO mail-wi0-f169.google.com) (209.85.212.169) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 5 Aug 2014 16:49:49 -0000 Received: by mail-wi0-f169.google.com with SMTP id n3so8218971wiv.0 for ; Tue, 05 Aug 2014 09:49:48 -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=xrN2kMRXOVO4cUFC/iZJ0xTl0inErNGdV3iia4N+tNw=; b=hdGO1zfEIrmlFUNC3F/InjXtS7P0q1IU1Pfvg9SzWRMM85QmAT8gSXgwn8KCHWvqqk J0asW04CDh6YmS3zCuVCBI5y9pdjvxpE1oItqfObOiXucF9ItYLohKKefyT+Zq2y3wby RsUpNi+T1kQ4tGaMgp8vTZPqQIuH5rZh/M0NA7COtftWhvwcLnFlUTanwAdEzp2lgASu 7gp8ks0mGhVGnUVf/C0yEcAh+HzuSzDoUBLdk50v8tUpQ6QODslKRYOrB1pszu+t7Q+g JUX6S9MLSfWDXbT4MMZxo6D4w4/j9MJupyyTtI16K6GzHAwsQpTrofkOQk7JXcbLkKRA 2sTg== X-Received: by 10.194.22.194 with SMTP id g2mr7736546wjf.30.1407257388852; Tue, 05 Aug 2014 09:49:48 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id dc3sm1880385wjc.27.2014.08.05.09.49.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 09:49:47 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <53E0FCBF.4030908@nottingham.ac.uk> Date: Tue, 5 Aug 2014 17:49:46 +0100 Message-Id: <23B9ADDC-83EF-469E-8A01-2F44F05D1812@gazagnaire.org> References: <53E0F76F.4080303@nottingham.ac.uk> <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> <53E0FCBF.4030908@nottingham.ac.uk> To: Masoud Koleini X-Mailer: Apple Mail (2.1878.6) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org What I'm guessing in your cryptic error bug report is that you've simply replaced the variable tap0 by the variable tap1 in the config.ml. However, this file is a normal OCaml program, so it needs to be lexically scoped: tap1 is the name of a variable which needs to be created somewhere. The tap0 variable is defined in https://github.com/mirage/mirage/blob/master/lib/mirage.mli#L209. I think in your case you can use (netfif "tap1") instead of tap0. Best, Thomas On 5 Aug 2014, at 16:48, Masoud Koleini wrote: > Mirage version is 1.2.0 > > The error is: > > Mirage Error: Unbound value tap1 > Mirage Did you mean tap0? > > > On 05/08/14 16:43, Thomas Gazagnaire wrote: >>> I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? >> Which error do you have ? Which version of mirage are you running ? >> >> >>> Thanks. >>> >>> >>> 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 > > -- > Masoud Koleini > Research Fellow > Horizon Digital Economy Research > University of Nottingham Innovation Park > Nottingham > NG7 2TU > > This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. > > > > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 16:50:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 16:50: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 1XEhwh-0003TU-Gk; Tue, 05 Aug 2014 16:50:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEhwf-0003TM-Ji for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:50:41 +0000 Received: from [85.158.143.35:61761] by server-2.bemta-4.messagelabs.com id B2/88-04525-06B01E35; Tue, 05 Aug 2014 16:50:40 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1407257439!13642089!1 X-Originating-IP: [217.70.183.195] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjcwLjE4My4xOTUgPT4gMzc4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 848 invoked from network); 5 Aug 2014 16:50:40 -0000 Received: from relay3-d.mail.gandi.net (HELO relay3-d.mail.gandi.net) (217.70.183.195) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Aug 2014 16:50:40 -0000 Received: from mfilter4-d.gandi.net (mfilter4-d.gandi.net [217.70.178.134]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id D5970A80DD for ; Tue, 5 Aug 2014 18:50:39 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter4-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter4-d.gandi.net (mfilter4-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id h7U-ytoJ8Bj6 for ; Tue, 5 Aug 2014 18:50:38 +0200 (CEST) X-Originating-IP: 184.60.30.10 Received: from [192.168.56.14] (h184-60-30-10.mdsnwi.dsl.dynamic.tds.net [184.60.30.10]) (Authenticated sender: guybrush@somerandomidiot.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 17FB3A80B9 for ; Tue, 5 Aug 2014 18:50:37 +0200 (CEST) Message-ID: <53E10B55.7060107@somerandomidiot.com> Date: Tue, 05 Aug 2014 11:50:29 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <53E0F76F.4080303@nottingham.ac.uk> In-Reply-To: <53E0F76F.4080303@nottingham.ac.uk> Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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 Masoud, I had a similar question and ended up with this chunk of config.ml for a Mirage program that needed two network interfaces. Basically, get a different interface by calling `netif` with an integer represented in a string to try for a different interface than the lowest-numbered usable-looking one (tap0 for unix, the vif numbered 0 for xen). I haven't verified that this actually works with Unix, but it does at least configure and build. From a config.ml: let client_netif = (netif "0") (* equivalent to let client_netif = tap0 *) let server_netif = (netif "1") (*netif actually needs an integer, shoved into a string, which maps to a device ID number assigned by Xen, to do anything helpful when xen is the target. Stuff that can't be turned into an int is silently dropped in that case and we just get the first Xen network iface. *) Hope this helps, Mindy On 08/05/2014 10:25 AM, Masoud Koleini wrote: > Hi, > > I am passing tap0 as a parameter from config to the main module in > unikernel.ml. Changing tap0 to tap1 or any other tap device produces > an error in compiling config file. How it is possible to pass tap > devices other than tap0 from config to the main module? > > Thanks. > > > This message and any attachment are intended solely for the addressee > and may contain confidential information. If you have received this > message in error, please send it back to me, and immediately delete > it. Please do not use, copy or disclose the information contained in > this message or in any attachment. Any views or opinions expressed by > the author of this email do not necessarily reflect the views of the > University of Nottingham. > > This message has been checked for viruses but the contents of an > attachment > may still contain software viruses which could damage your computer > system, you are advised to perform your own checks. Email > communications with the University of Nottingham may be monitored as > permitted by UK legislation. > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 16:50:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 16:50: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 1XEhwh-0003TU-Gk; Tue, 05 Aug 2014 16:50:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEhwf-0003TM-Ji for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:50:41 +0000 Received: from [85.158.143.35:61761] by server-2.bemta-4.messagelabs.com id B2/88-04525-06B01E35; Tue, 05 Aug 2014 16:50:40 +0000 X-Env-Sender: mindy@somerandomidiot.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1407257439!13642089!1 X-Originating-IP: [217.70.183.195] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMjE3LjcwLjE4My4xOTUgPT4gMzc4NjI=\n X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 848 invoked from network); 5 Aug 2014 16:50:40 -0000 Received: from relay3-d.mail.gandi.net (HELO relay3-d.mail.gandi.net) (217.70.183.195) by server-7.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Aug 2014 16:50:40 -0000 Received: from mfilter4-d.gandi.net (mfilter4-d.gandi.net [217.70.178.134]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id D5970A80DD for ; Tue, 5 Aug 2014 18:50:39 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter4-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter4-d.gandi.net (mfilter4-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id h7U-ytoJ8Bj6 for ; Tue, 5 Aug 2014 18:50:38 +0200 (CEST) X-Originating-IP: 184.60.30.10 Received: from [192.168.56.14] (h184-60-30-10.mdsnwi.dsl.dynamic.tds.net [184.60.30.10]) (Authenticated sender: guybrush@somerandomidiot.com) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 17FB3A80B9 for ; Tue, 5 Aug 2014 18:50:37 +0200 (CEST) Message-ID: <53E10B55.7060107@somerandomidiot.com> Date: Tue, 05 Aug 2014 11:50:29 -0500 From: Mindy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <53E0F76F.4080303@nottingham.ac.uk> In-Reply-To: <53E0F76F.4080303@nottingham.ac.uk> Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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 Masoud, I had a similar question and ended up with this chunk of config.ml for a Mirage program that needed two network interfaces. Basically, get a different interface by calling `netif` with an integer represented in a string to try for a different interface than the lowest-numbered usable-looking one (tap0 for unix, the vif numbered 0 for xen). I haven't verified that this actually works with Unix, but it does at least configure and build. From a config.ml: let client_netif = (netif "0") (* equivalent to let client_netif = tap0 *) let server_netif = (netif "1") (*netif actually needs an integer, shoved into a string, which maps to a device ID number assigned by Xen, to do anything helpful when xen is the target. Stuff that can't be turned into an int is silently dropped in that case and we just get the first Xen network iface. *) Hope this helps, Mindy On 08/05/2014 10:25 AM, Masoud Koleini wrote: > Hi, > > I am passing tap0 as a parameter from config to the main module in > unikernel.ml. Changing tap0 to tap1 or any other tap device produces > an error in compiling config file. How it is possible to pass tap > devices other than tap0 from config to the main module? > > Thanks. > > > This message and any attachment are intended solely for the addressee > and may contain confidential information. If you have received this > message in error, please send it back to me, and immediately delete > it. Please do not use, copy or disclose the information contained in > this message or in any attachment. Any views or opinions expressed by > the author of this email do not necessarily reflect the views of the > University of Nottingham. > > This message has been checked for viruses but the contents of an > attachment > may still contain software viruses which could damage your computer > system, you are advised to perform your own checks. Email > communications with the University of Nottingham may be monitored as > permitted by UK legislation. > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 16:55:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 16:55:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEi1G-0003Vc-Vl; Tue, 05 Aug 2014 16:55:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEi1E-0003VX-Pd for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:55:25 +0000 Received: from [193.109.254.147:63526] by server-2.bemta-14.messagelabs.com id 51/28-09196-C7C01E35; Tue, 05 Aug 2014 16:55:24 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-5.tower-27.messagelabs.com!1407257723!9271085!1 X-Originating-IP: [93.95.15.169] 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 12596 invoked from network); 5 Aug 2014 16:55:23 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-5.tower-27.messagelabs.com with SMTP; 5 Aug 2014 16:55:23 -0000 Received: (qmail 23787 invoked from network); 5 Aug 2014 16:55:22 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 5 Aug 2014 16:55:22 -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 21261-08 for ; Tue, 5 Aug 2014 17:55:18 +0100 (BST) Received: (qmail 23737 invoked by uid 599); 5 Aug 2014 16:55:18 -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, 05 Aug 2014 17:55:18 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp4.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XEi0n-00089J-4s; Tue, 05 Aug 2014 17:54:57 +0100 Message-ID: <53E10C61.2030809@nottingham.ac.uk> Date: Tue, 05 Aug 2014 17:54:57 +0100 From: Masoud Koleini 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: <53E0F76F.4080303@nottingham.ac.uk> <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> <53E0FCBF.4030908@nottingham.ac.uk> <23B9ADDC-83EF-469E-8A01-2F44F05D1812@gazagnaire.org> In-Reply-To: <23B9ADDC-83EF-469E-8A01-2F44F05D1812@gazagnaire.org> X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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 Thanks Thomas and Mandy, Thomas solution works well. Cheers, Masoud On 05/08/14 17:49, Thomas Gazagnaire wrote: > What I'm guessing in your cryptic error bug report is that you've simply replaced the variable tap0 by the variable tap1 in the config.ml. > > However, this file is a normal OCaml program, so it needs to be lexically scoped: tap1 is the name of a variable which needs to be created somewhere. The tap0 variable is defined in https://github.com/mirage/mirage/blob/master/lib/mirage.mli#L209. I think in your case you can use (netfif "tap1") instead of tap0. > > Best, > Thomas > > > > > On 5 Aug 2014, at 16:48, Masoud Koleini wrote: > >> Mirage version is 1.2.0 >> >> The error is: >> >> Mirage Error: Unbound value tap1 >> Mirage Did you mean tap0? >> >> >> On 05/08/14 16:43, Thomas Gazagnaire wrote: >>>> I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? >>> Which error do you have ? Which version of mirage are you running ? >>> >>> >>>> Thanks. >>>> >>>> >>>> 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 >> -- >> Masoud Koleini >> Research Fellow >> Horizon Digital Economy Research >> University of Nottingham Innovation Park >> Nottingham >> NG7 2TU >> >> 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 From mirageos-devel-bounces@lists.xenproject.org Tue Aug 05 16:55:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 05 Aug 2014 16:55:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEi1G-0003Vc-Vl; Tue, 05 Aug 2014 16:55:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEi1E-0003VX-Pd for mirageos-devel@lists.xenproject.org; Tue, 05 Aug 2014 16:55:25 +0000 Received: from [193.109.254.147:63526] by server-2.bemta-14.messagelabs.com id 51/28-09196-C7C01E35; Tue, 05 Aug 2014 16:55:24 +0000 X-Env-Sender: masoud.koleini@nottingham.ac.uk X-Msg-Ref: server-5.tower-27.messagelabs.com!1407257723!9271085!1 X-Originating-IP: [93.95.15.169] 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 12596 invoked from network); 5 Aug 2014 16:55:23 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-5.tower-27.messagelabs.com with SMTP; 5 Aug 2014 16:55:23 -0000 Received: (qmail 23787 invoked from network); 5 Aug 2014 16:55:22 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 5 Aug 2014 16:55:22 -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 21261-08 for ; Tue, 5 Aug 2014 17:55:18 +0100 (BST) Received: (qmail 23737 invoked by uid 599); 5 Aug 2014 16:55:18 -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, 05 Aug 2014 17:55:18 +0100 Received: from cirrus.cs.nott.ac.uk ([128.243.23.185]) by smtp4.nottingham.ac.uk with esmtp (Exim 4.77) (envelope-from ) id 1XEi0n-00089J-4s; Tue, 05 Aug 2014 17:54:57 +0100 Message-ID: <53E10C61.2030809@nottingham.ac.uk> Date: Tue, 05 Aug 2014 17:54:57 +0100 From: Masoud Koleini 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: <53E0F76F.4080303@nottingham.ac.uk> <16D28E75-8C76-49DA-AB1D-3ADCC7DBAD88@gazagnaire.org> <53E0FCBF.4030908@nottingham.ac.uk> <23B9ADDC-83EF-469E-8A01-2F44F05D1812@gazagnaire.org> In-Reply-To: <23B9ADDC-83EF-469E-8A01-2F44F05D1812@gazagnaire.org> X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Passing tap devices to the main module X-BeenThere: mirageos-devel@lists.xenproject.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 Thanks Thomas and Mandy, Thomas solution works well. Cheers, Masoud On 05/08/14 17:49, Thomas Gazagnaire wrote: > What I'm guessing in your cryptic error bug report is that you've simply replaced the variable tap0 by the variable tap1 in the config.ml. > > However, this file is a normal OCaml program, so it needs to be lexically scoped: tap1 is the name of a variable which needs to be created somewhere. The tap0 variable is defined in https://github.com/mirage/mirage/blob/master/lib/mirage.mli#L209. I think in your case you can use (netfif "tap1") instead of tap0. > > Best, > Thomas > > > > > On 5 Aug 2014, at 16:48, Masoud Koleini wrote: > >> Mirage version is 1.2.0 >> >> The error is: >> >> Mirage Error: Unbound value tap1 >> Mirage Did you mean tap0? >> >> >> On 05/08/14 16:43, Thomas Gazagnaire wrote: >>>> I am passing tap0 as a parameter from config to the main module in unikernel.ml. Changing tap0 to tap1 or any other tap device produces an error in compiling config file. How it is possible to pass tap devices other than tap0 from config to the main module? >>> Which error do you have ? Which version of mirage are you running ? >>> >>> >>>> Thanks. >>>> >>>> >>>> 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 >> -- >> Masoud Koleini >> Research Fellow >> Horizon Digital Economy Research >> University of Nottingham Innovation Park >> Nottingham >> NG7 2TU >> >> 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 From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:03:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:03: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 1XEwBf-00085n-Hz; Wed, 06 Aug 2014 08:03:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwBd-00085f-Ug for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:03:06 +0000 Received: from [193.109.254.147:34645] by server-11.bemta-14.messagelabs.com id 4C/26-14213-931E1E35; Wed, 06 Aug 2014 08:03:05 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-27.messagelabs.com!1407312183!13925369!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25621 invoked from network); 6 Aug 2014 08:03:03 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-3.tower-27.messagelabs.com with SMTP; 6 Aug 2014 08:03:03 -0000 Received: from wwinf1c15 ([10.223.79.59]) by mwinf5d36 with ME id bL331o0071GmtwS03L33UH; Wed, 06 Aug 2014 10:03:03 +0200 X-ME-Helo: wwinf1c15 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 10:03:03 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 10:03:02 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1644832063201200396==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1644832063201200396== Content-Type: multipart/alternative; boundary="----=_Part_3987_932243352.1407312183001" ------=_Part_3987_932243352.1407312183001 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hello, I have this error when i execute : =C2=A0 mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf Parsing config from /etc/xen/xl.conf libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how= =3D(nil) callback=3D(nil) poller=3D0x32578 libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qem= u-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev= =3Dxvda spec.backend=3Dunknown libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev= =3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mode= l pid in /local/domain/9/image/device-model-pid libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mode= l failed for 9 libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, = rc=3D-3 libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress:= poller=3D0x32578, flags=3Dic libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy xc: debug: hypercall buffer: total allocations:26 total releases:26 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 =C2=A0 i have a cubietruck arm and i have installed qemu-system-arm and qemu-syste= m-x86 =C2=A0 ------=_Part_3987_932243352.1407312183001 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

hello,

I have this error when i execute :

=C2=A0

mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
Parsing c= onfig from /etc/xen/xl.conf
libxl: debug: libxl_create.c:1342:do_domai= n_create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x32578=
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefaul= t: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file = or directory
libxl: debug: libxl_device.c:251:libxl__device_disk_set_b= ackend: Disk vdev=3Dxvda spec.backend=3Dunknown
libxl: error: libxl_de= vice.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat:= /dev/vg0/guest-linux-1: No such file or directory
libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
libxl: error: libxl.c:1421:libxl__destroy= _domid: libxl__destroy_device_model failed for 9
libxl: debug: libxl_e= vent.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc=3D-3
libxl: d= ebug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: poller= =3D0x32578, flags=3Dic
libxl: debug: libxl_event.c:1563:libxl__ao__des= troy: ao 0x31f00: destroy
xc: debug: hypercall buffer: total allocatio= ns:26 total releases:26
xc: debug: hypercall buffer: current allocatio= ns:0 maximum allocations:2
xc: debug: hypercall buffer: cache current = size:2
xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2

=C2=A0

i have a cubietruck arm and i have installed qemu-system-arm and qemu-sy= stem-x86

=C2=A0

------=_Part_3987_932243352.1407312183001-- --===============1644832063201200396== 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 --===============1644832063201200396==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:03:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:03: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 1XEwBf-00085n-Hz; Wed, 06 Aug 2014 08:03:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwBd-00085f-Ug for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:03:06 +0000 Received: from [193.109.254.147:34645] by server-11.bemta-14.messagelabs.com id 4C/26-14213-931E1E35; Wed, 06 Aug 2014 08:03:05 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-27.messagelabs.com!1407312183!13925369!1 X-Originating-IP: [80.12.242.123] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_00_10,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25621 invoked from network); 6 Aug 2014 08:03:03 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-3.tower-27.messagelabs.com with SMTP; 6 Aug 2014 08:03:03 -0000 Received: from wwinf1c15 ([10.223.79.59]) by mwinf5d36 with ME id bL331o0071GmtwS03L33UH; Wed, 06 Aug 2014 10:03:03 +0200 X-ME-Helo: wwinf1c15 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 10:03:03 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 10:03:02 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1644832063201200396==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1644832063201200396== Content-Type: multipart/alternative; boundary="----=_Part_3987_932243352.1407312183001" ------=_Part_3987_932243352.1407312183001 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable hello, I have this error when i execute : =C2=A0 mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf Parsing config from /etc/xen/xl.conf libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how= =3D(nil) callback=3D(nil) poller=3D0x32578 libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qem= u-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev= =3Dxvda spec.backend=3Dunknown libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev= =3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mode= l pid in /local/domain/9/image/device-model-pid libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mode= l failed for 9 libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, = rc=3D-3 libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress:= poller=3D0x32578, flags=3Dic libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy xc: debug: hypercall buffer: total allocations:26 total releases:26 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 =C2=A0 i have a cubietruck arm and i have installed qemu-system-arm and qemu-syste= m-x86 =C2=A0 ------=_Part_3987_932243352.1407312183001 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

hello,

I have this error when i execute :

=C2=A0

mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
Parsing c= onfig from /etc/xen/xl.conf
libxl: debug: libxl_create.c:1342:do_domai= n_create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x32578=
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefaul= t: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file = or directory
libxl: debug: libxl_device.c:251:libxl__device_disk_set_b= ackend: Disk vdev=3Dxvda spec.backend=3Dunknown
libxl: error: libxl_de= vice.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat:= /dev/vg0/guest-linux-1: No such file or directory
libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
libxl: error: libxl.c:1421:libxl__destroy= _domid: libxl__destroy_device_model failed for 9
libxl: debug: libxl_e= vent.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc=3D-3
libxl: d= ebug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: poller= =3D0x32578, flags=3Dic
libxl: debug: libxl_event.c:1563:libxl__ao__des= troy: ao 0x31f00: destroy
xc: debug: hypercall buffer: total allocatio= ns:26 total releases:26
xc: debug: hypercall buffer: current allocatio= ns:0 maximum allocations:2
xc: debug: hypercall buffer: cache current = size:2
xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2

=C2=A0

i have a cubietruck arm and i have installed qemu-system-arm and qemu-sy= stem-x86

=C2=A0

------=_Part_3987_932243352.1407312183001-- --===============1644832063201200396== 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 --===============1644832063201200396==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:06:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 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 1XEwEc-000880-Ro; Wed, 06 Aug 2014 08:06:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwEb-00087u-7k for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:06:09 +0000 Received: from [85.158.143.35:17315] by server-3.bemta-4.messagelabs.com id 9B/9D-06192-0F1E1E35; Wed, 06 Aug 2014 08:06:08 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-10.tower-21.messagelabs.com!1407312367!13754280!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=2.1 required=7.0 tests=HOT_NASTY,HTML_10_20, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1166 invoked from network); 6 Aug 2014 08:06:07 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-10.tower-21.messagelabs.com with SMTP; 6 Aug 2014 08:06:07 -0000 Received: from wwinf1c15 ([10.223.79.59]) by mwinf5d17 with ME id bL661o00X1GmtwS03L6621; Wed, 06 Aug 2014 10:06:06 +0200 X-ME-Helo: wwinf1c15 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 10:06:06 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 10:06:06 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> In-Reply-To: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2094475334945041115==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2094475334945041115== Content-Type: multipart/alternative; boundary="----=_Part_4081_1365893923.1407312366807" ------=_Part_4081_1365893923.1407312366807 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable my xl file : # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # Example HVM guest configuration # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # # This is a fairly minimal example of what is required for an # HVM guest. For a more complete guide see xl.cfg(5) # This configures an HVM rather than PV guest builder =3D "hvm" # Guest name name =3D "Xp" # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is sta= rted. #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Enable Microsoft Hyper-V compatibile paravirtualisation / # enlightenment interfaces. Turning this on can improve Windows guest # performance and is therefore recommended #viridian =3D 1 # Initial memory allocation (MB) memory =3D 512 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) #maxmem =3D 512 # Number of VCPUS vcpus =3D 2 # Network devices # A list of 'vifspec' entries as described in # docs/misc/xl-network-configuration.markdown vif =3D [ 'bridge=3Dbr0' ] # Disk Devices # A list of `diskspec' entries as described in # docs/misc/xl-disk-configuration.txt disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] # Guest VGA console configuration, either SDL or VNC sdl =3D 1 #vnc =3D 1 =C2=A0 > Message du 06/08/14 10:03 > De : "Gilles DALMAS"=20 > A : "mirageos-devel@lists.xenproject.org"=20 > Copie =C3=A0 :=20 > Objet : [MirageOS-devel] error when i create hvm guest >=20 > > hello, > I have this error when i execute : > =C2=A0 > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf Parsing config from /etc/xen/xl.conf libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how= =3D(nil) callback=3D(nil) poller=3D0x32578 libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qem= u-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev= =3Dxvda spec.backend=3Dunknown libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev= =3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mode= l pid in /local/domain/9/image/device-model-pid libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mode= l failed for 9 libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, = rc=3D-3 libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress:= poller=3D0x32578, flags=3Dic libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy xc: debug: hypercall buffer: total allocations:26 total releases:26 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > =C2=A0 > i have a cubietruck arm and i have installed qemu-system-arm and qemu-sys= tem-x86 > =C2=A0 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel ------=_Part_4081_1365893923.1407312366807 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

my xl file :
# =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
# Example HVM guest configuration
# =3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#
# This is a fairly minimal= example of what is required for an
# HVM guest. For a more complete g= uide see xl.cfg(5)

# This configures an HVM rather than PV guest=
builder =3D "hvm"

# Guest name
name =3D "Xp"
# 128-bit UUID for the domain as a hexadecimal number.
# Use "uuidg= en" to generate one if required.
# The default behavior is to generate= a new UUID each time the guest is started.
#uuid =3D "XXXXXXXX-XXXX-X= XXX-XXXX-XXXXXXXXXXXX"

# Enable Microsoft Hyper-V compatibile pa= ravirtualisation /
# enlightenment interfaces. Turning this on can imp= rove Windows guest
# performance and is therefore recommended
#vi= ridian =3D 1

# Initial memory allocation (MB)
memory =3D 51= 2

# Maximum memory (MB)
# If this is greater than `memory' = then the slack will start ballooned
# (this assumes guest kernel suppo= rt for ballooning)
#maxmem =3D 512

# Number of VCPUS
v= cpus =3D 2

# Network devices
# A list of 'vifspec' entries = as described in
# docs/misc/xl-network-configuration.markdown
vif= =3D [ 'bridge=3Dbr0' ]

# Disk Devices
# A list of `diskspe= c' entries as described in
# docs/misc/xl-disk-configuration.txt
= disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]

# Guest VGA co= nsole configuration, either SDL or VNC
sdl =3D 1
#vnc =3D 1
=

=C2=A0

> Message du 06/08/14 10:03
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "mirageos-devel@lists.xenprojec= t.org" <mirageos-devel@lists.xenproject.org>
> Copie =C3=A0 :=
> Objet : [MirageOS-devel] error when i create hvm guest
>= ;
>

> hello,

> I have this error when i execute :

> =C2=A0

> mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
Pars= ing config from /etc/xen/xl.conf
libxl: debug: libxl_create.c:1342:do_= domain_create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x= 32578
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setd= efault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such = file or directory
libxl: debug: libxl_device.c:251:libxl__device_disk_= set_backend: Disk vdev=3Dxvda spec.backend=3Dunknown
libxl: error: lib= xl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to = stat: /dev/vg0/guest-linux-1: No such file or directory
libxl: error: = libxl_dm.c:1467:kill_device_model: unable to find device model pid in /loca= l/domain/9/image/device-model-pid
libxl: error: libxl.c:1421:libxl__de= stroy_domid: libxl__destroy_device_model failed for 9
libxl: debug: li= bxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc=3D-3
lib= xl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: po= ller=3D0x32578, flags=3Dic
libxl: debug: libxl_event.c:1563:libxl__ao_= _destroy: ao 0x31f00: destroy
xc: debug: hypercall buffer: total alloc= ations:26 total releases:26
xc: debug: hypercall buffer: current alloc= ations:0 maximum allocations:2
xc: debug: hypercall buffer: cache curr= ent size:2
xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> =C2=A0

> i have a cubietruck arm and i have installed qemu-system-arm and qe= mu-system-x86

> =C2=A0




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

<= /blockquote> ------=_Part_4081_1365893923.1407312366807-- --===============2094475334945041115== 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 --===============2094475334945041115==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:06:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 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 1XEwEc-000880-Ro; Wed, 06 Aug 2014 08:06:10 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwEb-00087u-7k for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:06:09 +0000 Received: from [85.158.143.35:17315] by server-3.bemta-4.messagelabs.com id 9B/9D-06192-0F1E1E35; Wed, 06 Aug 2014 08:06:08 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-10.tower-21.messagelabs.com!1407312367!13754280!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=2.1 required=7.0 tests=HOT_NASTY,HTML_10_20, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1166 invoked from network); 6 Aug 2014 08:06:07 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-10.tower-21.messagelabs.com with SMTP; 6 Aug 2014 08:06:07 -0000 Received: from wwinf1c15 ([10.223.79.59]) by mwinf5d17 with ME id bL661o00X1GmtwS03L6621; Wed, 06 Aug 2014 10:06:06 +0200 X-ME-Helo: wwinf1c15 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 10:06:06 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 10:06:06 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> In-Reply-To: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2094475334945041115==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2094475334945041115== Content-Type: multipart/alternative; boundary="----=_Part_4081_1365893923.1407312366807" ------=_Part_4081_1365893923.1407312366807 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable my xl file : # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # Example HVM guest configuration # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # # This is a fairly minimal example of what is required for an # HVM guest. For a more complete guide see xl.cfg(5) # This configures an HVM rather than PV guest builder =3D "hvm" # Guest name name =3D "Xp" # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is sta= rted. #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Enable Microsoft Hyper-V compatibile paravirtualisation / # enlightenment interfaces. Turning this on can improve Windows guest # performance and is therefore recommended #viridian =3D 1 # Initial memory allocation (MB) memory =3D 512 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) #maxmem =3D 512 # Number of VCPUS vcpus =3D 2 # Network devices # A list of 'vifspec' entries as described in # docs/misc/xl-network-configuration.markdown vif =3D [ 'bridge=3Dbr0' ] # Disk Devices # A list of `diskspec' entries as described in # docs/misc/xl-disk-configuration.txt disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] # Guest VGA console configuration, either SDL or VNC sdl =3D 1 #vnc =3D 1 =C2=A0 > Message du 06/08/14 10:03 > De : "Gilles DALMAS"=20 > A : "mirageos-devel@lists.xenproject.org"=20 > Copie =C3=A0 :=20 > Objet : [MirageOS-devel] error when i create hvm guest >=20 > > hello, > I have this error when i execute : > =C2=A0 > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf Parsing config from /etc/xen/xl.conf libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how= =3D(nil) callback=3D(nil) poller=3D0x32578 libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qem= u-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev= =3Dxvda spec.backend=3Dunknown libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev= =3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mode= l pid in /local/domain/9/image/device-model-pid libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mode= l failed for 9 libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, = rc=3D-3 libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress:= poller=3D0x32578, flags=3Dic libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy xc: debug: hypercall buffer: total allocations:26 total releases:26 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer: cache current size:2 xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > =C2=A0 > i have a cubietruck arm and i have installed qemu-system-arm and qemu-sys= tem-x86 > =C2=A0 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel ------=_Part_4081_1365893923.1407312366807 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

my xl file :
# =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
# Example HVM guest configuration
# =3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#
# This is a fairly minimal= example of what is required for an
# HVM guest. For a more complete g= uide see xl.cfg(5)

# This configures an HVM rather than PV guest=
builder =3D "hvm"

# Guest name
name =3D "Xp"
# 128-bit UUID for the domain as a hexadecimal number.
# Use "uuidg= en" to generate one if required.
# The default behavior is to generate= a new UUID each time the guest is started.
#uuid =3D "XXXXXXXX-XXXX-X= XXX-XXXX-XXXXXXXXXXXX"

# Enable Microsoft Hyper-V compatibile pa= ravirtualisation /
# enlightenment interfaces. Turning this on can imp= rove Windows guest
# performance and is therefore recommended
#vi= ridian =3D 1

# Initial memory allocation (MB)
memory =3D 51= 2

# Maximum memory (MB)
# If this is greater than `memory' = then the slack will start ballooned
# (this assumes guest kernel suppo= rt for ballooning)
#maxmem =3D 512

# Number of VCPUS
v= cpus =3D 2

# Network devices
# A list of 'vifspec' entries = as described in
# docs/misc/xl-network-configuration.markdown
vif= =3D [ 'bridge=3Dbr0' ]

# Disk Devices
# A list of `diskspe= c' entries as described in
# docs/misc/xl-disk-configuration.txt
= disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]

# Guest VGA co= nsole configuration, either SDL or VNC
sdl =3D 1
#vnc =3D 1
=

=C2=A0

> Message du 06/08/14 10:03
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "mirageos-devel@lists.xenprojec= t.org" <mirageos-devel@lists.xenproject.org>
> Copie =C3=A0 :=
> Objet : [MirageOS-devel] error when i create hvm guest
>= ;
>

> hello,

> I have this error when i execute :

> =C2=A0

> mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
Pars= ing config from /etc/xen/xl.conf
libxl: debug: libxl_create.c:1342:do_= domain_create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x= 32578
libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setd= efault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such = file or directory
libxl: debug: libxl_device.c:251:libxl__device_disk_= set_backend: Disk vdev=3Dxvda spec.backend=3Dunknown
libxl: error: lib= xl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to = stat: /dev/vg0/guest-linux-1: No such file or directory
libxl: error: = libxl_dm.c:1467:kill_device_model: unable to find device model pid in /loca= l/domain/9/image/device-model-pid
libxl: error: libxl.c:1421:libxl__de= stroy_domid: libxl__destroy_device_model failed for 9
libxl: debug: li= bxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc=3D-3
lib= xl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: po= ller=3D0x32578, flags=3Dic
libxl: debug: libxl_event.c:1563:libxl__ao_= _destroy: ao 0x31f00: destroy
xc: debug: hypercall buffer: total alloc= ations:26 total releases:26
xc: debug: hypercall buffer: current alloc= ations:0 maximum allocations:2
xc: debug: hypercall buffer: cache curr= ent size:2
xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> =C2=A0

> i have a cubietruck arm and i have installed qemu-system-arm and qe= mu-system-x86

> =C2=A0




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

<= /blockquote> ------=_Part_4081_1365893923.1407312366807-- --===============2094475334945041115== 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 --===============2094475334945041115==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:21:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:21: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 1XEwTW-0008SU-T6; Wed, 06 Aug 2014 08:21:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwTV-0008SF-70 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:21:33 +0000 Received: from [85.158.137.68:41338] by server-14.bemta-3.messagelabs.com id 9F/0F-09441-C85E1E35; Wed, 06 Aug 2014 08:21:32 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-31.messagelabs.com!1407313290!12127940!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=2.3 required=7.0 tests=HOT_NASTY,HTML_20_30, HTML_MESSAGE,MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3675 invoked from network); 6 Aug 2014 08:21:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-31.messagelabs.com with SMTP; 6 Aug 2014 08:21:31 -0000 Received: (qmail 32324 invoked by uid 634); 6 Aug 2014 08:21:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [192.168.99.40]) (212.104.156.18) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 06 Aug 2014 09:21:29 +0100 References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> Mime-Version: 1.0 (1.0) In-Reply-To: <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> Message-Id: <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Wed, 6 Aug 2014 09:21:27 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1085686198163349340==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1085686198163349340== Content-Type: multipart/alternative; boundary=Apple-Mail-B9322BFB-6B38-401F-8416-245E90CAA500 Content-Transfer-Encoding: 7bit --Apple-Mail-B9322BFB-6B38-401F-8416-245E90CAA500 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Why are you trying to create an HVM guest on Xen/ARM? You should just be us= ing the default PV mode on ARM to launch guests. > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: >=20 > my xl file : > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # Example HVM guest configuration > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # > # This is a fairly minimal example of what is required for an > # HVM guest. For a more complete guide see xl.cfg(5) >=20 > # This configures an HVM rather than PV guest > builder =3D "hvm" >=20 > # Guest name > name =3D "Xp" >=20 > # 128-bit UUID for the domain as a hexadecimal number. > # Use "uuidgen" to generate one if required. > # The default behavior is to generate a new UUID each time the guest is st= arted. > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" >=20 > # Enable Microsoft Hyper-V compatibile paravirtualisation / > # enlightenment interfaces. Turning this on can improve Windows guest > # performance and is therefore recommended > #viridian =3D 1 >=20 > # Initial memory allocation (MB) > memory =3D 512 >=20 > # Maximum memory (MB) > # If this is greater than `memory' then the slack will start ballooned > # (this assumes guest kernel support for ballooning) > #maxmem =3D 512 >=20 > # Number of VCPUS > vcpus =3D 2 >=20 > # Network devices > # A list of 'vifspec' entries as described in > # docs/misc/xl-network-configuration.markdown > vif =3D [ 'bridge=3Dbr0' ] >=20 > # Disk Devices > # A list of `diskspec' entries as described in > # docs/misc/xl-disk-configuration.txt > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] >=20 > # Guest VGA console configuration, either SDL or VNC > sdl =3D 1 > #vnc =3D 1 >=20 >=20 > =20 >=20 > > Message du 06/08/14 10:03 > > De : "Gilles DALMAS" > > A : "mirageos-devel@lists.xenproject.org" > > Copie =C3=A0 :=20 > > Objet : [MirageOS-devel] error when i create hvm guest > >=20 > > > > hello, >=20 > > I have this error when i execute : >=20 > > =20 >=20 > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > Parsing config from /etc/xen/xl.conf > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: ho= w=3D(nil) callback=3D(nil) poller=3D0x32578 > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qe= mu-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev= =3Dxvda spec.backend=3Dunknown > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev= =3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mod= el pid in /local/domain/9/image/device-model-pid > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mod= el failed for 9 > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete,= rc=3D-3 > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress= : poller=3D0x32578, flags=3Dic > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy > xc: debug: hypercall buffer: total allocations:26 total releases:26 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > =20 >=20 > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-sy= stem-x86 >=20 > > =20 >=20 >=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-B9322BFB-6B38-401F-8416-245E90CAA500 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Why are you trying to create an HVM gu= est on Xen/ARM?  You should just be using the default PV mode on ARM to= launch guests.

On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

<= /div>

my xl file :
# =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Example HVM guest configuration
# =3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#
# This is a fairly m= inimal example of what is required for an
# HVM guest. For a more complet= e guide see xl.cfg(5)

# This configures an HVM rather than PV guestbuilder =3D "hvm"

# Guest name
name =3D "Xp"

# 128-bit UU= ID for the domain as a hexadecimal number.
# Use "uuidgen" to generate on= e if required.
# The default behavior is to generate a new UUID each time= the guest is started.
#uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
# Enable Microsoft Hyper-V compatibile paravirtualisation /
# enlig= htenment interfaces. Turning this on can improve Windows guest
# performa= nce and is therefore recommended
#viridian =3D 1

# Initial memory a= llocation (MB)
memory =3D 512

# Maximum memory (MB)
# If this i= s greater than `memory' then the slack will start ballooned
# (this assum= es guest kernel support for ballooning)
#maxmem =3D 512

# Number o= f VCPUS
vcpus =3D 2

# Network devices
# A list of 'vifspec' ent= ries as described in
# docs/misc/xl-network-configuration.markdown
vif= =3D [ 'bridge=3Dbr0' ]

# Disk Devices
# A list of `diskspec' entr= ies as described in
# docs/misc/xl-disk-configuration.txt
disk =3D [ '= /dev/vg0/guest-linux-1,raw,xvda,rw' ]

# Guest VGA console configurati= on, either SDL or VNC
sdl =3D 1
#vnc =3D 1

 

> Message du 06/08/14 10:03
> De : "Gilles DALMAS" &= lt;gdalmas@wanadoo.fr>
> A= : "mirageos-devel@li= sts.xenproject.org" <mirageos-devel@lists.xenproject.org>
> Copie =C3=A0 : > Objet : [MirageOS-devel] error when i create hvm guest
>
&g= t;

> hello,

> I have this error when i execute :

>  

> mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
Parsing= config from /etc/xen/xl.conf
libxl: debug: libxl_create.c:1342:do_domain= _create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x32578libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qe= mu-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: D= isk vdev=3Dxvda spec.backend=3Dunknown
libxl: error: libxl_device.c:265:l= ibxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/gue= st-linux-1: No such file or directory
libxl: error: libxl_dm.c:1467:kill_= device_model: unable to find device model pid in /local/domain/9/image/devic= e-model-pid
libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destr= oy_device_model failed for 9
libxl: debug: libxl_event.c:1591:libxl__ao_c= omplete: ao 0x31f00: complete, rc=3D-3
libxl: debug: libxl_create.c:1356:= do_domain_create: ao 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
li= bxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
xc= : debug: hypercall buffer: total allocations:26 total releases:26
xc: deb= ug: hypercall buffer: current allocations:0 maximum allocations:2
xc: deb= ug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: c= ache hits:22 misses:2 toobig:2

>  

> i have a cubietruck arm and i have installed qemu-system-arm and qem= u-system-x86

>  




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

____________________________________= ___________
MirageOS-devel mailing list
MirageOS-devel@lists.xenp= roject.org
http://lists.xenproject.org/cgi-bin/mailm= an/listinfo/mirageos-devel
= --Apple-Mail-B9322BFB-6B38-401F-8416-245E90CAA500-- --===============1085686198163349340== 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 --===============1085686198163349340==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:21:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:21: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 1XEwTW-0008SU-T6; Wed, 06 Aug 2014 08:21:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwTV-0008SF-70 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:21:33 +0000 Received: from [85.158.137.68:41338] by server-14.bemta-3.messagelabs.com id 9F/0F-09441-C85E1E35; Wed, 06 Aug 2014 08:21:32 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-31.messagelabs.com!1407313290!12127940!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=2.3 required=7.0 tests=HOT_NASTY,HTML_20_30, HTML_MESSAGE,MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3675 invoked from network); 6 Aug 2014 08:21:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-31.messagelabs.com with SMTP; 6 Aug 2014 08:21:31 -0000 Received: (qmail 32324 invoked by uid 634); 6 Aug 2014 08:21:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [192.168.99.40]) (212.104.156.18) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 06 Aug 2014 09:21:29 +0100 References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> Mime-Version: 1.0 (1.0) In-Reply-To: <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> Message-Id: <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Wed, 6 Aug 2014 09:21:27 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1085686198163349340==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1085686198163349340== Content-Type: multipart/alternative; boundary=Apple-Mail-B9322BFB-6B38-401F-8416-245E90CAA500 Content-Transfer-Encoding: 7bit --Apple-Mail-B9322BFB-6B38-401F-8416-245E90CAA500 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Why are you trying to create an HVM guest on Xen/ARM? You should just be us= ing the default PV mode on ARM to launch guests. > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: >=20 > my xl file : > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # Example HVM guest configuration > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # > # This is a fairly minimal example of what is required for an > # HVM guest. For a more complete guide see xl.cfg(5) >=20 > # This configures an HVM rather than PV guest > builder =3D "hvm" >=20 > # Guest name > name =3D "Xp" >=20 > # 128-bit UUID for the domain as a hexadecimal number. > # Use "uuidgen" to generate one if required. > # The default behavior is to generate a new UUID each time the guest is st= arted. > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" >=20 > # Enable Microsoft Hyper-V compatibile paravirtualisation / > # enlightenment interfaces. Turning this on can improve Windows guest > # performance and is therefore recommended > #viridian =3D 1 >=20 > # Initial memory allocation (MB) > memory =3D 512 >=20 > # Maximum memory (MB) > # If this is greater than `memory' then the slack will start ballooned > # (this assumes guest kernel support for ballooning) > #maxmem =3D 512 >=20 > # Number of VCPUS > vcpus =3D 2 >=20 > # Network devices > # A list of 'vifspec' entries as described in > # docs/misc/xl-network-configuration.markdown > vif =3D [ 'bridge=3Dbr0' ] >=20 > # Disk Devices > # A list of `diskspec' entries as described in > # docs/misc/xl-disk-configuration.txt > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] >=20 > # Guest VGA console configuration, either SDL or VNC > sdl =3D 1 > #vnc =3D 1 >=20 >=20 > =20 >=20 > > Message du 06/08/14 10:03 > > De : "Gilles DALMAS" > > A : "mirageos-devel@lists.xenproject.org" > > Copie =C3=A0 :=20 > > Objet : [MirageOS-devel] error when i create hvm guest > >=20 > > > > hello, >=20 > > I have this error when i execute : >=20 > > =20 >=20 > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > Parsing config from /etc/xen/xl.conf > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: ho= w=3D(nil) callback=3D(nil) poller=3D0x32578 > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qe= mu-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev= =3Dxvda spec.backend=3Dunknown > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev= =3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mod= el pid in /local/domain/9/image/device-model-pid > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mod= el failed for 9 > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete,= rc=3D-3 > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress= : poller=3D0x32578, flags=3Dic > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy > xc: debug: hypercall buffer: total allocations:26 total releases:26 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > =20 >=20 > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-sy= stem-x86 >=20 > > =20 >=20 >=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-B9322BFB-6B38-401F-8416-245E90CAA500 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Why are you trying to create an HVM gu= est on Xen/ARM?  You should just be using the default PV mode on ARM to= launch guests.

On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

<= /div>

my xl file :
# =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Example HVM guest configuration
# =3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
#
# This is a fairly m= inimal example of what is required for an
# HVM guest. For a more complet= e guide see xl.cfg(5)

# This configures an HVM rather than PV guestbuilder =3D "hvm"

# Guest name
name =3D "Xp"

# 128-bit UU= ID for the domain as a hexadecimal number.
# Use "uuidgen" to generate on= e if required.
# The default behavior is to generate a new UUID each time= the guest is started.
#uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
# Enable Microsoft Hyper-V compatibile paravirtualisation /
# enlig= htenment interfaces. Turning this on can improve Windows guest
# performa= nce and is therefore recommended
#viridian =3D 1

# Initial memory a= llocation (MB)
memory =3D 512

# Maximum memory (MB)
# If this i= s greater than `memory' then the slack will start ballooned
# (this assum= es guest kernel support for ballooning)
#maxmem =3D 512

# Number o= f VCPUS
vcpus =3D 2

# Network devices
# A list of 'vifspec' ent= ries as described in
# docs/misc/xl-network-configuration.markdown
vif= =3D [ 'bridge=3Dbr0' ]

# Disk Devices
# A list of `diskspec' entr= ies as described in
# docs/misc/xl-disk-configuration.txt
disk =3D [ '= /dev/vg0/guest-linux-1,raw,xvda,rw' ]

# Guest VGA console configurati= on, either SDL or VNC
sdl =3D 1
#vnc =3D 1

 

> Message du 06/08/14 10:03
> De : "Gilles DALMAS" &= lt;gdalmas@wanadoo.fr>
> A= : "mirageos-devel@li= sts.xenproject.org" <mirageos-devel@lists.xenproject.org>
> Copie =C3=A0 : > Objet : [MirageOS-devel] error when i create hvm guest
>
&g= t;

> hello,

> I have this error when i execute :

>  

> mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
Parsing= config from /etc/xen/xl.conf
libxl: debug: libxl_create.c:1342:do_domain= _create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x32578libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qe= mu-xen is unavailable, use qemu-xen-traditional instead: No such file or dir= ectory
libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: D= isk vdev=3Dxvda spec.backend=3Dunknown
libxl: error: libxl_device.c:265:l= ibxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/gue= st-linux-1: No such file or directory
libxl: error: libxl_dm.c:1467:kill_= device_model: unable to find device model pid in /local/domain/9/image/devic= e-model-pid
libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destr= oy_device_model failed for 9
libxl: debug: libxl_event.c:1591:libxl__ao_c= omplete: ao 0x31f00: complete, rc=3D-3
libxl: debug: libxl_create.c:1356:= do_domain_create: ao 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
li= bxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
xc= : debug: hypercall buffer: total allocations:26 total releases:26
xc: deb= ug: hypercall buffer: current allocations:0 maximum allocations:2
xc: deb= ug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: c= ache hits:22 misses:2 toobig:2

>  

> i have a cubietruck arm and i have installed qemu-system-arm and qem= u-system-x86

>  




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

____________________________________= ___________
MirageOS-devel mailing list
MirageOS-devel@lists.xenp= roject.org
http://lists.xenproject.org/cgi-bin/mailm= an/listinfo/mirageos-devel
= --Apple-Mail-B9322BFB-6B38-401F-8416-245E90CAA500-- --===============1085686198163349340== 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 --===============1085686198163349340==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:44:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:44: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 1XEwq8-0000as-H2; Wed, 06 Aug 2014 08:44:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwq6-0000ae-Kb for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:44:54 +0000 Received: from [85.158.143.35:27701] by server-3.bemta-4.messagelabs.com id 09/24-06192-50BE1E35; Wed, 06 Aug 2014 08:44:53 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-15.tower-21.messagelabs.com!1407314692!13731016!1 X-Originating-IP: [80.12.242.130] X-SpamReason: No, hits=2.1 required=7.0 tests=HOT_NASTY,HTML_20_30, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22488 invoked from network); 6 Aug 2014 08:44:52 -0000 Received: from smtp08.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.130) by server-15.tower-21.messagelabs.com with SMTP; 6 Aug 2014 08:44:52 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d43 with ME id bLkr1o00W1EBZFu03Lkrdp; Wed, 06 Aug 2014 10:44:51 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 10:44:51 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 10:44:51 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> In-Reply-To: <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1001641867568346210==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1001641867568346210== Content-Type: multipart/alternative; boundary="----=_Part_5934_1821614970.1407314691923" ------=_Part_5934_1821614970.1407314691923 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable the guest system can only be started in this mode. there is a problems with= this mode ? > Message du 06/08/14 10:21 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: >=20 > > my xl file : > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # Example HVM guest configuration > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # > # This is a fairly minimal example of what is required for an > # HVM guest. For a more complete guide see xl.cfg(5) >=20 > # This configures an HVM rather than PV guest > builder =3D "hvm" >=20 > # Guest name > name =3D "Xp" >=20 > # 128-bit UUID for the domain as a hexadecimal number. > # Use "uuidgen" to generate one if required. > # The default behavior is to generate a new UUID each time the guest is s= tarted. > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" >=20 > # Enable Microsoft Hyper-V compatibile paravirtualisation / > # enlightenment interfaces. Turning this on can improve Windows guest > # performance and is therefore recommended > #viridian =3D 1 >=20 > # Initial memory allocation (MB) > memory =3D 512 >=20 > # Maximum memory (MB) > # If this is greater than `memory' then the slack will start ballooned > # (this assumes guest kernel support for ballooning) > #maxmem =3D 512 >=20 > # Number of VCPUS > vcpus =3D 2 >=20 > # Network devices > # A list of 'vifspec' entries as described in > # docs/misc/xl-network-configuration.markdown > vif =3D [ 'bridge=3Dbr0' ] >=20 > # Disk Devices > # A list of `diskspec' entries as described in > # docs/misc/xl-disk-configuration.txt > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] >=20 > # Guest VGA console configuration, either SDL or VNC > sdl =3D 1 > #vnc =3D 1 >=20 > > =C2=A0 > Message du 06/08/14 10:03 > > De : "Gilles DALMAS"=20 > > A : "mirageos-devel@lists.xenproject.org"=20 > > Copie =C3=A0 :=20 > > Objet : [MirageOS-devel] error when i create hvm guest > >=20 > > > > hello, > > I have this error when i execute : > > =C2=A0 > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > Parsing config from /etc/xen/xl.conf > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: h= ow=3D(nil) callback=3D(nil) poller=3D0x32578 > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: q= emu-xen is unavailable, use qemu-xen-traditional instead: No such file or d= irectory > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vde= v=3Dxvda spec.backend=3Dunknown > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vde= v=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mo= del pid in /local/domain/9/image/device-model-pid > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mo= del failed for 9 > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete= , rc=3D-3 > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogres= s: poller=3D0x32578, flags=3Dic > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy > xc: debug: hypercall buffer: total allocations:26 total releases:26 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > =C2=A0 > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-s= ystem-x86 > > =C2=A0 >=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 > ------=_Part_5934_1821614970.1407314691923 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

the guest system can only be started in this mode. there is a problems w= ith this mode ?




> Message du 06/08/14 10:21
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> my xl file :
> # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D
> # Example HVM guest configuration
> # =3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> #
>= ; # This is a fairly minimal example of what is required for an
> #= HVM guest. For a more complete guide see xl.cfg(5)
>
> # = This configures an HVM rather than PV guest
> builder =3D "hvm"
>
> # Guest name
> name =3D "Xp"
>
>= # 128-bit UUID for the domain as a hexadecimal number.
> # Use "uu= idgen" to generate one if required.
> # The default behavior is to = generate a new UUID each time the guest is started.
> #uuid =3D "XX= XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
>
> # Enable Microsoft= Hyper-V compatibile paravirtualisation /
> # enlightenment interfa= ces. Turning this on can improve Windows guest
> # performance and = is therefore recommended
> #viridian =3D 1
>
> # I= nitial memory allocation (MB)
> memory =3D 512
>
>= # Maximum memory (MB)
> # If this is greater than `memory' then th= e slack will start ballooned
> # (this assumes guest kernel support= for ballooning)
> #maxmem =3D 512
>
> # Number of= VCPUS
> vcpus =3D 2
>
> # Network devices
&g= t; # A list of 'vifspec' entries as described in
> # docs/misc/xl-n= etwork-configuration.markdown
> vif =3D [ 'bridge=3Dbr0' ]
>= ;
> # Disk Devices
> # A list of `diskspec' entries as des= cribed in
> # docs/misc/xl-disk-configuration.txt
> disk = =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
>
> # Guest V= GA console configuration, either SDL or VNC
> sdl =3D 1
> #= vnc =3D 1
>
>

> =C2=A0

> Message du 06/08/14 10:03
> > De : "Gilles = DALMAS" <gdalmas@wanadoo.fr>= ;
> > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > Copie =C3=A0 :
> > Objet : [MirageOS-devel] error wh= en i create hvm guest
> >
> >

> > hello,

> > I have this error when i execute :

> > =C2=A0

> > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
> Parsing config from /etc/xen/xl.conf
> libxl: debug: libxl_cr= eate.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil) callback=3D(n= il) poller=3D0x32578
> libxl: verbose: libxl_create.c:134:libxl__do= main_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-tradition= al instead: No such file or directory
> libxl: debug: libxl_device.= c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda spec.backend=3Dunkno= wn
> libxl: error: libxl_device.c:265:libxl__device_disk_set_backen= d: Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or= directory
> libxl: error: libxl_dm.c:1467:kill_device_model: unabl= e to find device model pid in /local/domain/9/image/device-model-pid
&= gt; libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9
> libxl: debug: libxl_event.c:1591:libxl__ao_com= plete: ao 0x31f00: complete, rc=3D-3
> libxl: debug: libxl_create.c= :1356:do_domain_create: ao 0x31f00: inprogress: poller=3D0x32578, flags=3Di= c
> libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00= : destroy
> xc: debug: hypercall buffer: total allocations:26 total= releases:26
> xc: debug: hypercall buffer: current allocations:0 m= aximum allocations:2
> xc: debug: hypercall buffer: cache current s= ize:2
> xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > =C2=A0

> > i have a cubietruck arm and i have installed qemu-system-arm a= nd qemu-system-x86

> > =C2=A0


>
>
> __________________________________________= _____
> 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
>
------=_Part_5934_1821614970.1407314691923-- --===============1001641867568346210== 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 --===============1001641867568346210==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:44:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:44: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 1XEwq8-0000as-H2; Wed, 06 Aug 2014 08:44:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwq6-0000ae-Kb for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:44:54 +0000 Received: from [85.158.143.35:27701] by server-3.bemta-4.messagelabs.com id 09/24-06192-50BE1E35; Wed, 06 Aug 2014 08:44:53 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-15.tower-21.messagelabs.com!1407314692!13731016!1 X-Originating-IP: [80.12.242.130] X-SpamReason: No, hits=2.1 required=7.0 tests=HOT_NASTY,HTML_20_30, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22488 invoked from network); 6 Aug 2014 08:44:52 -0000 Received: from smtp08.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.130) by server-15.tower-21.messagelabs.com with SMTP; 6 Aug 2014 08:44:52 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d43 with ME id bLkr1o00W1EBZFu03Lkrdp; Wed, 06 Aug 2014 10:44:51 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 10:44:51 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 10:44:51 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> In-Reply-To: <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1001641867568346210==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1001641867568346210== Content-Type: multipart/alternative; boundary="----=_Part_5934_1821614970.1407314691923" ------=_Part_5934_1821614970.1407314691923 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable the guest system can only be started in this mode. there is a problems with= this mode ? > Message du 06/08/14 10:21 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: >=20 > > my xl file : > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # Example HVM guest configuration > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > # > # This is a fairly minimal example of what is required for an > # HVM guest. For a more complete guide see xl.cfg(5) >=20 > # This configures an HVM rather than PV guest > builder =3D "hvm" >=20 > # Guest name > name =3D "Xp" >=20 > # 128-bit UUID for the domain as a hexadecimal number. > # Use "uuidgen" to generate one if required. > # The default behavior is to generate a new UUID each time the guest is s= tarted. > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" >=20 > # Enable Microsoft Hyper-V compatibile paravirtualisation / > # enlightenment interfaces. Turning this on can improve Windows guest > # performance and is therefore recommended > #viridian =3D 1 >=20 > # Initial memory allocation (MB) > memory =3D 512 >=20 > # Maximum memory (MB) > # If this is greater than `memory' then the slack will start ballooned > # (this assumes guest kernel support for ballooning) > #maxmem =3D 512 >=20 > # Number of VCPUS > vcpus =3D 2 >=20 > # Network devices > # A list of 'vifspec' entries as described in > # docs/misc/xl-network-configuration.markdown > vif =3D [ 'bridge=3Dbr0' ] >=20 > # Disk Devices > # A list of `diskspec' entries as described in > # docs/misc/xl-disk-configuration.txt > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] >=20 > # Guest VGA console configuration, either SDL or VNC > sdl =3D 1 > #vnc =3D 1 >=20 > > =C2=A0 > Message du 06/08/14 10:03 > > De : "Gilles DALMAS"=20 > > A : "mirageos-devel@lists.xenproject.org"=20 > > Copie =C3=A0 :=20 > > Objet : [MirageOS-devel] error when i create hvm guest > >=20 > > > > hello, > > I have this error when i execute : > > =C2=A0 > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > Parsing config from /etc/xen/xl.conf > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: h= ow=3D(nil) callback=3D(nil) poller=3D0x32578 > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: q= emu-xen is unavailable, use qemu-xen-traditional instead: No such file or d= irectory > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vde= v=3Dxvda spec.backend=3Dunknown > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vde= v=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device mo= del pid in /local/domain/9/image/device-model-pid > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_mo= del failed for 9 > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete= , rc=3D-3 > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogres= s: poller=3D0x32578, flags=3Dic > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy > xc: debug: hypercall buffer: total allocations:26 total releases:26 > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 > xc: debug: hypercall buffer: cache current size:2 > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > =C2=A0 > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-s= ystem-x86 > > =C2=A0 >=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 > ------=_Part_5934_1821614970.1407314691923 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

the guest system can only be started in this mode. there is a problems w= ith this mode ?




> Message du 06/08/14 10:21
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> my xl file :
> # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D
> # Example HVM guest configuration
> # =3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> #
>= ; # This is a fairly minimal example of what is required for an
> #= HVM guest. For a more complete guide see xl.cfg(5)
>
> # = This configures an HVM rather than PV guest
> builder =3D "hvm"
>
> # Guest name
> name =3D "Xp"
>
>= # 128-bit UUID for the domain as a hexadecimal number.
> # Use "uu= idgen" to generate one if required.
> # The default behavior is to = generate a new UUID each time the guest is started.
> #uuid =3D "XX= XXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
>
> # Enable Microsoft= Hyper-V compatibile paravirtualisation /
> # enlightenment interfa= ces. Turning this on can improve Windows guest
> # performance and = is therefore recommended
> #viridian =3D 1
>
> # I= nitial memory allocation (MB)
> memory =3D 512
>
>= # Maximum memory (MB)
> # If this is greater than `memory' then th= e slack will start ballooned
> # (this assumes guest kernel support= for ballooning)
> #maxmem =3D 512
>
> # Number of= VCPUS
> vcpus =3D 2
>
> # Network devices
&g= t; # A list of 'vifspec' entries as described in
> # docs/misc/xl-n= etwork-configuration.markdown
> vif =3D [ 'bridge=3Dbr0' ]
>= ;
> # Disk Devices
> # A list of `diskspec' entries as des= cribed in
> # docs/misc/xl-disk-configuration.txt
> disk = =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
>
> # Guest V= GA console configuration, either SDL or VNC
> sdl =3D 1
> #= vnc =3D 1
>
>

> =C2=A0

> Message du 06/08/14 10:03
> > De : "Gilles = DALMAS" <gdalmas@wanadoo.fr>= ;
> > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > Copie =C3=A0 :
> > Objet : [MirageOS-devel] error wh= en i create hvm guest
> >
> >

> > hello,

> > I have this error when i execute :

> > =C2=A0

> > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
> Parsing config from /etc/xen/xl.conf
> libxl: debug: libxl_cr= eate.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil) callback=3D(n= il) poller=3D0x32578
> libxl: verbose: libxl_create.c:134:libxl__do= main_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-tradition= al instead: No such file or directory
> libxl: debug: libxl_device.= c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda spec.backend=3Dunkno= wn
> libxl: error: libxl_device.c:265:libxl__device_disk_set_backen= d: Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or= directory
> libxl: error: libxl_dm.c:1467:kill_device_model: unabl= e to find device model pid in /local/domain/9/image/device-model-pid
&= gt; libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9
> libxl: debug: libxl_event.c:1591:libxl__ao_com= plete: ao 0x31f00: complete, rc=3D-3
> libxl: debug: libxl_create.c= :1356:do_domain_create: ao 0x31f00: inprogress: poller=3D0x32578, flags=3Di= c
> libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00= : destroy
> xc: debug: hypercall buffer: total allocations:26 total= releases:26
> xc: debug: hypercall buffer: current allocations:0 m= aximum allocations:2
> xc: debug: hypercall buffer: cache current s= ize:2
> xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > =C2=A0

> > i have a cubietruck arm and i have installed qemu-system-arm a= nd qemu-system-x86

> > =C2=A0


>
>
> __________________________________________= _____
> 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
>
------=_Part_5934_1821614970.1407314691923-- --===============1001641867568346210== 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 --===============1001641867568346210==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:53:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:53: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 1XEwy3-0000p6-ID; Wed, 06 Aug 2014 08:53:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwy2-0000ow-IK for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:53:06 +0000 Received: from [193.109.254.147:22296] by server-15.bemta-14.messagelabs.com id 07/12-30948-1FCE1E35; Wed, 06 Aug 2014 08:53:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1407315184!14025488!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.5 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE,MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27519 invoked from network); 6 Aug 2014 08:53:04 -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; 6 Aug 2014 08:53:04 -0000 Received: (qmail 11735 invoked by uid 634); 6 Aug 2014 08:53:03 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [192.168.99.40]) (212.104.156.18) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 06 Aug 2014 09:53:01 +0100 References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> Mime-Version: 1.0 (1.0) In-Reply-To: <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> Message-Id: X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Wed, 6 Aug 2014 09:52:59 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6045588936096399199==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6045588936096399199== Content-Type: multipart/alternative; boundary=Apple-Mail-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC Content-Transfer-Encoding: 7bit --Apple-Mail-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable This mode doesn't exist on ARM: it's an option to run x86 guests in hardware= virtualisation mode. Are you trying to boot an x86 guest on ARM? -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > the guest system can only be started in this mode. there is a problems wit= h this mode ? >=20 >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy" > > A : "Gilles DALMAS" > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > > Why are you trying to create an HVM guest on Xen/ARM? You should just be u= sing the default PV mode on ARM to launch guests. >=20 > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is s= tarted. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > >=20 > > =20 >=20 > > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS" > > > A : "mirageos-devel@lists.xenproject.org" > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, >=20 > > > I have this error when i execute : >=20 > > > =20 >=20 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: h= ow=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: q= emu-xen is unavailable, use qemu-xen-traditional instead: No such file or di= rectory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vd= ev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vd= ev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device m= odel pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_m= odel failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complet= e, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogre= ss: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy= > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2= > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > > =20 >=20 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-= system-x86 >=20 > > > =20 >=20 >=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-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
This mode doesn't exist on ARM: it's a= n option to run x86 guests in hardware virtualisation mode.  Are you tr= ying to boot an x86 guest on ARM?

-anil
<= br>On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

the guest system can only be started in this mode. there is a p= roblems with this mode ?




> Message du 06/08/14 10:21
> De : "Anil Madhavapedd= y" <anil@recoil.org>
> A := "Gilles DALMAS" <gdalmas@wanadoo.f= r>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org= >
> Objet : Re: [MirageOS-devel] error when i create hvm guest
&= gt;
>
Why are you trying to create an HVM guest on Xen/ARM?  You should j= ust be using the default PV mode on ARM to launch guests.

> On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>

> my xl file :
> # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
> # Example HVM guest configuration
> # =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> #
> # This is a fairly minim= al example of what is required for an
> # HVM guest. For a more comple= te guide see xl.cfg(5)
>
> # This configures an HVM rather than= PV guest
> builder =3D "hvm"
>
> # Guest name
> na= me =3D "Xp"
>
> # 128-bit UUID for the domain as a hexadecimal n= umber.
> # Use "uuidgen" to generate one if required.
> # The de= fault behavior is to generate a new UUID each time the guest is started.
= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
>
> # Ena= ble Microsoft Hyper-V compatibile paravirtualisation /
> # enlightenme= nt interfaces. Turning this on can improve Windows guest
> # performan= ce and is therefore recommended
> #viridian =3D 1
>
> # I= nitial memory allocation (MB)
> memory =3D 512
>
> # Maxi= mum memory (MB)
> # If this is greater than `memory' then the slack wi= ll start ballooned
> # (this assumes guest kernel support for ballooni= ng)
> #maxmem =3D 512
>
> # Number of VCPUS
> vcpus= =3D 2
>
> # Network devices
> # A list of 'vifspec' entr= ies as described in
> # docs/misc/xl-network-configuration.markdown> vif =3D [ 'bridge=3Dbr0' ]
>
> # Disk Devices
> # A= list of `diskspec' entries as described in
> # docs/misc/xl-disk-conf= iguration.txt
> disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
&= gt;
> # Guest VGA console configuration, either SDL or VNC
> sd= l =3D 1
> #vnc =3D 1
>
>

>  

> Message du 06/08/14 10:03
> > De : "Gilles DALM= AS" <gdalmas@wanadoo.fr>
= > > A : "mirage= os-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > C= opie =C3=A0 :
> > Objet : [MirageOS-devel] error when i create hvm= guest
> >
> >

> > hello,

> > I have this error when i execute :

> >  

> > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
&g= t; Parsing config from /etc/xen/xl.conf
> libxl: debug: libxl_create.c= :1342:do_domain_create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) pol= ler=3D0x32578
> libxl: verbose: libxl_create.c:134:libxl__domain_build= _info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead:= No such file or directory
> libxl: debug: libxl_device.c:251:libxl__d= evice_disk_set_backend: Disk vdev=3Dxvda spec.backend=3Dunknown
> libx= l: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvd= a failed to stat: /dev/vg0/guest-linux-1: No such file or directory
> l= ibxl: error: libxl_dm.c:1467:kill_device_model: unable to find device model p= id in /local/domain/9/image/device-model-pid
> libxl: error: libxl.c:1= 421:libxl__destroy_domid: libxl__destroy_device_model failed for 9
> l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc= =3D-3
> libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00= : inprogress: poller=3D0x32578, flags=3Dic
> libxl: debug: libxl_event= .c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> xc: debug: hypercall= buffer: total allocations:26 total releases:26
> xc: debug: hypercall= buffer: current allocations:0 maximum allocations:2
> xc: debug: hype= rcall buffer: cache current size:2
> xc: debug: hypercall buffer: cach= e hits:22 misses:2 toobig:2

> >  

> > i have a cubietruck arm and i have installed qemu-system-arm an= d qemu-system-x86

> >  


>
>
> _______________________________________________> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> ht= tp://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/mi= rageos-devel
>
= --Apple-Mail-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC-- --===============6045588936096399199== 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 --===============6045588936096399199==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 08:53:07 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 08:53: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 1XEwy3-0000p6-ID; Wed, 06 Aug 2014 08:53:07 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEwy2-0000ow-IK for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 08:53:06 +0000 Received: from [193.109.254.147:22296] by server-15.bemta-14.messagelabs.com id 07/12-30948-1FCE1E35; Wed, 06 Aug 2014 08:53:05 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-15.tower-27.messagelabs.com!1407315184!14025488!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.5 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE,MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27519 invoked from network); 6 Aug 2014 08:53:04 -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; 6 Aug 2014 08:53:04 -0000 Received: (qmail 11735 invoked by uid 634); 6 Aug 2014 08:53:03 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,MIME_QP_LONG_LINE X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [192.168.99.40]) (212.104.156.18) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 06 Aug 2014 09:53:01 +0100 References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> Mime-Version: 1.0 (1.0) In-Reply-To: <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> Message-Id: X-Mailer: iPhone Mail (11D257) From: Anil Madhavapeddy Date: Wed, 6 Aug 2014 09:52:59 +0100 To: Gilles DALMAS X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6045588936096399199==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6045588936096399199== Content-Type: multipart/alternative; boundary=Apple-Mail-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC Content-Transfer-Encoding: 7bit --Apple-Mail-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable This mode doesn't exist on ARM: it's an option to run x86 guests in hardware= virtualisation mode. Are you trying to boot an x86 guest on ARM? -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > the guest system can only be started in this mode. there is a problems wit= h this mode ? >=20 >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy" > > A : "Gilles DALMAS" > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > > Why are you trying to create an HVM guest on Xen/ARM? You should just be u= sing the default PV mode on ARM to launch guests. >=20 > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is s= tarted. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > >=20 > > =20 >=20 > > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS" > > > A : "mirageos-devel@lists.xenproject.org" > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, >=20 > > > I have this error when i execute : >=20 > > > =20 >=20 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: h= ow=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: q= emu-xen is unavailable, use qemu-xen-traditional instead: No such file or di= rectory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vd= ev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vd= ev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device m= odel pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_m= odel failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complet= e, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogre= ss: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy= > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2= > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > > =20 >=20 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-= system-x86 >=20 > > > =20 >=20 >=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-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
This mode doesn't exist on ARM: it's a= n option to run x86 guests in hardware virtualisation mode.  Are you tr= ying to boot an x86 guest on ARM?

-anil
<= br>On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

the guest system can only be started in this mode. there is a p= roblems with this mode ?




> Message du 06/08/14 10:21
> De : "Anil Madhavapedd= y" <anil@recoil.org>
> A := "Gilles DALMAS" <gdalmas@wanadoo.f= r>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org= >
> Objet : Re: [MirageOS-devel] error when i create hvm guest
&= gt;
>
Why are you trying to create an HVM guest on Xen/ARM?  You should j= ust be using the default PV mode on ARM to launch guests.

> On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>

> my xl file :
> # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
> # Example HVM guest configuration
> # =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> #
> # This is a fairly minim= al example of what is required for an
> # HVM guest. For a more comple= te guide see xl.cfg(5)
>
> # This configures an HVM rather than= PV guest
> builder =3D "hvm"
>
> # Guest name
> na= me =3D "Xp"
>
> # 128-bit UUID for the domain as a hexadecimal n= umber.
> # Use "uuidgen" to generate one if required.
> # The de= fault behavior is to generate a new UUID each time the guest is started.
= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
>
> # Ena= ble Microsoft Hyper-V compatibile paravirtualisation /
> # enlightenme= nt interfaces. Turning this on can improve Windows guest
> # performan= ce and is therefore recommended
> #viridian =3D 1
>
> # I= nitial memory allocation (MB)
> memory =3D 512
>
> # Maxi= mum memory (MB)
> # If this is greater than `memory' then the slack wi= ll start ballooned
> # (this assumes guest kernel support for ballooni= ng)
> #maxmem =3D 512
>
> # Number of VCPUS
> vcpus= =3D 2
>
> # Network devices
> # A list of 'vifspec' entr= ies as described in
> # docs/misc/xl-network-configuration.markdown> vif =3D [ 'bridge=3Dbr0' ]
>
> # Disk Devices
> # A= list of `diskspec' entries as described in
> # docs/misc/xl-disk-conf= iguration.txt
> disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
&= gt;
> # Guest VGA console configuration, either SDL or VNC
> sd= l =3D 1
> #vnc =3D 1
>
>

>  

> Message du 06/08/14 10:03
> > De : "Gilles DALM= AS" <gdalmas@wanadoo.fr>
= > > A : "mirage= os-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > C= opie =C3=A0 :
> > Objet : [MirageOS-devel] error when i create hvm= guest
> >
> >

> > hello,

> > I have this error when i execute :

> >  

> > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
&g= t; Parsing config from /etc/xen/xl.conf
> libxl: debug: libxl_create.c= :1342:do_domain_create: ao 0x31f00: create: how=3D(nil) callback=3D(nil) pol= ler=3D0x32578
> libxl: verbose: libxl_create.c:134:libxl__domain_build= _info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead:= No such file or directory
> libxl: debug: libxl_device.c:251:libxl__d= evice_disk_set_backend: Disk vdev=3Dxvda spec.backend=3Dunknown
> libx= l: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvd= a failed to stat: /dev/vg0/guest-linux-1: No such file or directory
> l= ibxl: error: libxl_dm.c:1467:kill_device_model: unable to find device model p= id in /local/domain/9/image/device-model-pid
> libxl: error: libxl.c:1= 421:libxl__destroy_domid: libxl__destroy_device_model failed for 9
> l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc= =3D-3
> libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00= : inprogress: poller=3D0x32578, flags=3Dic
> libxl: debug: libxl_event= .c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> xc: debug: hypercall= buffer: total allocations:26 total releases:26
> xc: debug: hypercall= buffer: current allocations:0 maximum allocations:2
> xc: debug: hype= rcall buffer: cache current size:2
> xc: debug: hypercall buffer: cach= e hits:22 misses:2 toobig:2

> >  

> > i have a cubietruck arm and i have installed qemu-system-arm an= d qemu-system-x86

> >  


>
>
> _______________________________________________> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> ht= tp://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/mi= rageos-devel
>
= --Apple-Mail-7C3E97DF-F3CA-4464-98E9-5DB399A7B6AC-- --===============6045588936096399199== 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 --===============6045588936096399199==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 09:58:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 09:58: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 1XExzh-0003KM-En; Wed, 06 Aug 2014 09:58:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XExzf-0003JJ-Tk for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 09:58:52 +0000 Received: from [85.158.137.68:54322] by server-10.bemta-3.messagelabs.com id 2A/C1-28313-B5CF1E35; Wed, 06 Aug 2014 09:58:51 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-9.tower-31.messagelabs.com!1407319129!8426213!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25669 invoked from network); 6 Aug 2014 09:58:49 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-9.tower-31.messagelabs.com with SMTP; 6 Aug 2014 09:58:49 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d57 with ME id bMyp1o0051EBZFu03Mypt8; Wed, 06 Aug 2014 11:58:49 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 11:58:49 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 11:58:49 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1526918094.7865.1407319129060.JavaMail.www@wwinf1c13> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6991441886765989272==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6991441886765989272== Content-Type: multipart/alternative; boundary="----=_Part_7864_845054815.1407319129052" ------=_Part_7864_845054815.1407319129052 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am this guide: http://www.abobier.be/2014/03/18/installer-xpenology-dsm5-= avec-gnoboot-0-10-3-sur-xenserver-6-2/ I do not know if it works the other way, I'll test. > Message du 06/08/14 10:53 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > > the guest system can only be started in this mode. there is a problems wi= th this mode ? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is= started. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > > > =C2=A0 > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS"=20 > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, > > > I have this error when i execute : > > > =C2=A0 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create:= how=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:= qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or= directory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk v= dev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk v= dev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or director= y > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device = model pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comple= te, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogr= ess: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destro= y > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2 > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > =C2=A0 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu= -system-x86 > > > =C2=A0 > >=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 > > ------=_Part_7864_845054815.1407319129052 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I am this guide: http://www.abobier.be/2014/03/18/installer-xpenology-ds= m5-avec-gnoboot-0-10-3-sur-xenserver-6-2/
I do not know if it works th= e other way, I'll test.




> Message du 06/08/14 10:53
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> the guest system can only be started in this mode. there is a probl= ems with this mode ?
>
>
>
>
><= /p>

> Message du 06/08/14 10:21
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > my xl file :
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # Example HVM guest configuratio= n
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> > #
> > # This is a fairly minimal example of w= hat is required for an
> > # HVM guest. For a more complete guid= e see xl.cfg(5)
> >
> > # This configures an HVM rat= her than PV guest
> > builder =3D "hvm"
> >
>= ; > # Guest name
> > name =3D "Xp"
> >
> = > # 128-bit UUID for the domain as a hexadecimal number.
> > = # Use "uuidgen" to generate one if required.
> > # The default b= ehavior is to generate a new UUID each time the guest is started.
>= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> &= gt; #viridian =3D 1
> >
> > # Initial memory allocat= ion (MB)
> > memory =3D 512
> >
> > # Max= imum memory (MB)
> > # If this is greater than `memory' then the= slack will start ballooned
> > # (this assumes guest kernel sup= port for ballooning)
> > #maxmem =3D 512
> >
&g= t; > # Number of VCPUS
> > vcpus =3D 2
> >
&= gt; > # Network devices
> > # A list of 'vifspec' entries as = described in
> > # docs/misc/xl-network-configuration.markdown> > vif =3D [ 'bridge=3Dbr0' ]
> >
> > # D= isk Devices
> > # A list of `diskspec' entries as described in> > # docs/misc/xl-disk-configuration.txt
> > disk =3D= [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D 1=
> > #vnc =3D 1
> >
> >

> > =C2=A0

> Message du 06/08/14 10:03
> > > De : "Gi= lles DALMAS" <gdalmas@wanadoo.fr>
> > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Copie =C3=A0 :
> > > Objet : [Mira= geOS-devel] error when i create hvm guest
> > >
> &g= t; >

> > > hello,

> > > I have this error when i execute :

> > > =C2=A0

> > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf=
> > Parsing config from /etc/xen/xl.conf
> > libxl: = debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil= ) callback=3D(nil) poller=3D0x32578
> > libxl: verbose: libxl_cr= eate.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, us= e qemu-xen-traditional instead: No such file or directory
> > li= bxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3D= xvda spec.backend=3Dunknown
> > libxl: error: libxl_device.c:265= :libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/= guest-linux-1: No such file or directory
> > libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
> > libxl: error: libxl.c:1421:libx= l__destroy_domid: libxl__destroy_device_model failed for 9
> > l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, r= c=3D-3
> > libxl: debug: libxl_create.c:1356:do_domain_create: a= o 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
> > libxl: d= ebug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> = > xc: debug: hypercall buffer: total allocations:26 total releases:26> > xc: debug: hypercall buffer: current allocations:0 maximum all= ocations:2
> > xc: debug: hypercall buffer: cache current size:2=
> > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > =C2=A0

> > > i have a cubietruck arm and i have installed qemu-system-= arm and qemu-system-x86

> > > =C2=A0


> >
> >
> > ___________________________= ____________________
> > MirageOS-devel mailing list
> &= gt; MirageOS-devel@l= ists.xenproject.org
> > http://lists.xenproject.org/cgi= -bin/mailman/listinfo/mirageos-devel
> >
> >
_______________________________________________
>= > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenpro= ject.org
> > http://lists.xenproject.org/c= gi-bin/mailman/listinfo/mirageos-devel
> >
------=_Part_7864_845054815.1407319129052-- --===============6991441886765989272== 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 --===============6991441886765989272==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 09:58:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 09:58: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 1XExzh-0003KM-En; Wed, 06 Aug 2014 09:58:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XExzf-0003JJ-Tk for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 09:58:52 +0000 Received: from [85.158.137.68:54322] by server-10.bemta-3.messagelabs.com id 2A/C1-28313-B5CF1E35; Wed, 06 Aug 2014 09:58:51 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-9.tower-31.messagelabs.com!1407319129!8426213!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25669 invoked from network); 6 Aug 2014 09:58:49 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-9.tower-31.messagelabs.com with SMTP; 6 Aug 2014 09:58:49 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d57 with ME id bMyp1o0051EBZFu03Mypt8; Wed, 06 Aug 2014 11:58:49 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 11:58:49 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 11:58:49 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1526918094.7865.1407319129060.JavaMail.www@wwinf1c13> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6991441886765989272==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6991441886765989272== Content-Type: multipart/alternative; boundary="----=_Part_7864_845054815.1407319129052" ------=_Part_7864_845054815.1407319129052 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am this guide: http://www.abobier.be/2014/03/18/installer-xpenology-dsm5-= avec-gnoboot-0-10-3-sur-xenserver-6-2/ I do not know if it works the other way, I'll test. > Message du 06/08/14 10:53 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > > the guest system can only be started in this mode. there is a problems wi= th this mode ? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is= started. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > > > =C2=A0 > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS"=20 > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, > > > I have this error when i execute : > > > =C2=A0 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create:= how=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:= qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or= directory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk v= dev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk v= dev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or director= y > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device = model pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comple= te, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogr= ess: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destro= y > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2 > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > =C2=A0 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu= -system-x86 > > > =C2=A0 > >=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 > > ------=_Part_7864_845054815.1407319129052 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I am this guide: http://www.abobier.be/2014/03/18/installer-xpenology-ds= m5-avec-gnoboot-0-10-3-sur-xenserver-6-2/
I do not know if it works th= e other way, I'll test.




> Message du 06/08/14 10:53
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> the guest system can only be started in this mode. there is a probl= ems with this mode ?
>
>
>
>
><= /p>

> Message du 06/08/14 10:21
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > my xl file :
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # Example HVM guest configuratio= n
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> > #
> > # This is a fairly minimal example of w= hat is required for an
> > # HVM guest. For a more complete guid= e see xl.cfg(5)
> >
> > # This configures an HVM rat= her than PV guest
> > builder =3D "hvm"
> >
>= ; > # Guest name
> > name =3D "Xp"
> >
> = > # 128-bit UUID for the domain as a hexadecimal number.
> > = # Use "uuidgen" to generate one if required.
> > # The default b= ehavior is to generate a new UUID each time the guest is started.
>= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> &= gt; #viridian =3D 1
> >
> > # Initial memory allocat= ion (MB)
> > memory =3D 512
> >
> > # Max= imum memory (MB)
> > # If this is greater than `memory' then the= slack will start ballooned
> > # (this assumes guest kernel sup= port for ballooning)
> > #maxmem =3D 512
> >
&g= t; > # Number of VCPUS
> > vcpus =3D 2
> >
&= gt; > # Network devices
> > # A list of 'vifspec' entries as = described in
> > # docs/misc/xl-network-configuration.markdown> > vif =3D [ 'bridge=3Dbr0' ]
> >
> > # D= isk Devices
> > # A list of `diskspec' entries as described in> > # docs/misc/xl-disk-configuration.txt
> > disk =3D= [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D 1=
> > #vnc =3D 1
> >
> >

> > =C2=A0

> Message du 06/08/14 10:03
> > > De : "Gi= lles DALMAS" <gdalmas@wanadoo.fr>
> > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Copie =C3=A0 :
> > > Objet : [Mira= geOS-devel] error when i create hvm guest
> > >
> &g= t; >

> > > hello,

> > > I have this error when i execute :

> > > =C2=A0

> > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf=
> > Parsing config from /etc/xen/xl.conf
> > libxl: = debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil= ) callback=3D(nil) poller=3D0x32578
> > libxl: verbose: libxl_cr= eate.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, us= e qemu-xen-traditional instead: No such file or directory
> > li= bxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3D= xvda spec.backend=3Dunknown
> > libxl: error: libxl_device.c:265= :libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/= guest-linux-1: No such file or directory
> > libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
> > libxl: error: libxl.c:1421:libx= l__destroy_domid: libxl__destroy_device_model failed for 9
> > l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, r= c=3D-3
> > libxl: debug: libxl_create.c:1356:do_domain_create: a= o 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
> > libxl: d= ebug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> = > xc: debug: hypercall buffer: total allocations:26 total releases:26> > xc: debug: hypercall buffer: current allocations:0 maximum all= ocations:2
> > xc: debug: hypercall buffer: cache current size:2=
> > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > =C2=A0

> > > i have a cubietruck arm and i have installed qemu-system-= arm and qemu-system-x86

> > > =C2=A0


> >
> >
> > ___________________________= ____________________
> > MirageOS-devel mailing list
> &= gt; MirageOS-devel@l= ists.xenproject.org
> > http://lists.xenproject.org/cgi= -bin/mailman/listinfo/mirageos-devel
> >
> >
_______________________________________________
>= > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenpro= ject.org
> > http://lists.xenproject.org/c= gi-bin/mailman/listinfo/mirageos-devel
> >
------=_Part_7864_845054815.1407319129052-- --===============6991441886765989272== 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 --===============6991441886765989272==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 11:07:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 11:07: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 1XEz3W-0005DE-Pt; Wed, 06 Aug 2014 11:06:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEz3U-0005D3-Hl for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 11:06:52 +0000 Received: from [85.158.139.211:34769] by server-15.bemta-5.messagelabs.com id 34/15-12002-B4C02E35; Wed, 06 Aug 2014 11:06:51 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-7.tower-206.messagelabs.com!1407323210!12227166!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30044 invoked from network); 6 Aug 2014 11:06:50 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-7.tower-206.messagelabs.com with SMTP; 6 Aug 2014 11:06:50 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d57 with ME id bP6p1o0081EBZFu03P6p7v; Wed, 06 Aug 2014 13:06:49 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 13:06:49 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 13:06:49 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <743760884.9077.1407323209423.JavaMail.www@wwinf1c13> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2306264045619511285==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2306264045619511285== Content-Type: multipart/alternative; boundary="----=_Part_9076_798882104.1407323209422" ------=_Part_9076_798882104.1407323209422 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i have same error with thisconf file : # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # Example PV Linux guest configuration # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # # This is a fairly minimal example of what is required for a # Paravirtualised Linux guest. For a more complete guide see xl.cfg(5) # Guest name name =3D "Xp" # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is sta= rted. #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Kernel image to boot kernel =3D "/zImage" # Ramdisk (optional) #ramdisk =3D "/boot/initrd.gz" # Kernel command line options extra =3D "root=3D/dev/vg0/linux-guest-1p2" # Initial memory allocation (MB) memory =3D 512 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) #maxmem =3D 512 # Number of VCPUS vcpus =3D 2 # Network devices # A list of 'vifspec' entries as described in # docs/misc/xl-network-configuration.markdown vif =3D [ 'bridge=3Dbr0' ] # Disk Devices # A list of `diskspec' entries as described in # docs/misc/xl-disk-configuration.txt disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > Message du 06/08/14 10:53 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > > the guest system can only be started in this mode. there is a problems wi= th this mode ? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is= started. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > > > =C2=A0 > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS"=20 > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, > > > I have this error when i execute : > > > =C2=A0 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create:= how=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:= qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or= directory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk v= dev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk v= dev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or director= y > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device = model pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comple= te, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogr= ess: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destro= y > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2 > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > =C2=A0 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu= -system-x86 > > > =C2=A0 > >=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 > > ------=_Part_9076_798882104.1407323209422 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

i have same error with thisconf file :


# =3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Example PV Linux gu= est configuration
# =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D
#
# This is a fairly minimal example of what is require= d for a
# Paravirtualised Linux guest. For a more complete guide see x= l.cfg(5)

# Guest name
name =3D "Xp"

# 128-bit UU= ID for the domain as a hexadecimal number.
# Use "uuidgen" to generate= one if required.
# The default behavior is to generate a new UUID eac= h time the guest is started.
#uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXX= XXXXXX"

# Kernel image to boot
kernel =3D "/zImage"
# Ramdisk (optional)
#ramdisk =3D "/boot/initrd.gz"

# K= ernel command line options
extra =3D "root=3D/dev/vg0/linux-guest-1p2"=

# Initial memory allocation (MB)
memory =3D 512

# Maximum memory (MB)
# If this is greater than `memory' then the sla= ck will start ballooned
# (this assumes guest kernel support for ballo= oning)
#maxmem =3D 512

# Number of VCPUS
vcpus =3D 2
# Network devices
# A list of 'vifspec' entries as described= in
# docs/misc/xl-network-configuration.markdown
vif =3D [ 'brid= ge=3Dbr0' ]

# Disk Devices
# A list of `diskspec' entries a= s described in
# docs/misc/xl-disk-configuration.txt
disk =3D [ '= /dev/vg0/guest-linux-1,raw,xvda,rw' ]

> Message du 06/08/14 10:53
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> the guest system can only be started in this mode. there is a probl= ems with this mode ?
>
>
>
>
><= /p>

> Message du 06/08/14 10:21
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > my xl file :
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # Example HVM guest configuratio= n
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> > #
> > # This is a fairly minimal example of w= hat is required for an
> > # HVM guest. For a more complete guid= e see xl.cfg(5)
> >
> > # This configures an HVM rat= her than PV guest
> > builder =3D "hvm"
> >
>= ; > # Guest name
> > name =3D "Xp"
> >
> = > # 128-bit UUID for the domain as a hexadecimal number.
> > = # Use "uuidgen" to generate one if required.
> > # The default b= ehavior is to generate a new UUID each time the guest is started.
>= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> &= gt; #viridian =3D 1
> >
> > # Initial memory allocat= ion (MB)
> > memory =3D 512
> >
> > # Max= imum memory (MB)
> > # If this is greater than `memory' then the= slack will start ballooned
> > # (this assumes guest kernel sup= port for ballooning)
> > #maxmem =3D 512
> >
&g= t; > # Number of VCPUS
> > vcpus =3D 2
> >
&= gt; > # Network devices
> > # A list of 'vifspec' entries as = described in
> > # docs/misc/xl-network-configuration.markdown> > vif =3D [ 'bridge=3Dbr0' ]
> >
> > # D= isk Devices
> > # A list of `diskspec' entries as described in> > # docs/misc/xl-disk-configuration.txt
> > disk =3D= [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D 1=
> > #vnc =3D 1
> >
> >

> > =C2=A0

> Message du 06/08/14 10:03
> > > De : "Gi= lles DALMAS" <gdalmas@wanadoo.fr>
> > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Copie =C3=A0 :
> > > Objet : [Mira= geOS-devel] error when i create hvm guest
> > >
> &g= t; >

> > > hello,

> > > I have this error when i execute :

> > > =C2=A0

> > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf=
> > Parsing config from /etc/xen/xl.conf
> > libxl: = debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil= ) callback=3D(nil) poller=3D0x32578
> > libxl: verbose: libxl_cr= eate.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, us= e qemu-xen-traditional instead: No such file or directory
> > li= bxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3D= xvda spec.backend=3Dunknown
> > libxl: error: libxl_device.c:265= :libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/= guest-linux-1: No such file or directory
> > libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
> > libxl: error: libxl.c:1421:libx= l__destroy_domid: libxl__destroy_device_model failed for 9
> > l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, r= c=3D-3
> > libxl: debug: libxl_create.c:1356:do_domain_create: a= o 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
> > libxl: d= ebug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> = > xc: debug: hypercall buffer: total allocations:26 total releases:26> > xc: debug: hypercall buffer: current allocations:0 maximum all= ocations:2
> > xc: debug: hypercall buffer: cache current size:2=
> > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > =C2=A0

> > > i have a cubietruck arm and i have installed qemu-system-= arm and qemu-system-x86

> > > =C2=A0


> >
> >
> > ___________________________= ____________________
> > MirageOS-devel mailing list
> &= gt; MirageOS-devel@l= ists.xenproject.org
> > http://lists.xenproject.org/cgi= -bin/mailman/listinfo/mirageos-devel
> >
> >
_______________________________________________
>= > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenpro= ject.org
> > http://lists.xenproject.org/c= gi-bin/mailman/listinfo/mirageos-devel
> >
------=_Part_9076_798882104.1407323209422-- --===============2306264045619511285== 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 --===============2306264045619511285==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 11:07:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 11:07: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 1XEz3W-0005DE-Pt; Wed, 06 Aug 2014 11:06:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XEz3U-0005D3-Hl for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 11:06:52 +0000 Received: from [85.158.139.211:34769] by server-15.bemta-5.messagelabs.com id 34/15-12002-B4C02E35; Wed, 06 Aug 2014 11:06:51 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-7.tower-206.messagelabs.com!1407323210!12227166!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30044 invoked from network); 6 Aug 2014 11:06:50 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-7.tower-206.messagelabs.com with SMTP; 6 Aug 2014 11:06:50 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d57 with ME id bP6p1o0081EBZFu03P6p7v; Wed, 06 Aug 2014 13:06:49 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 13:06:49 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 13:06:49 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <743760884.9077.1407323209423.JavaMail.www@wwinf1c13> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2306264045619511285==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2306264045619511285== Content-Type: multipart/alternative; boundary="----=_Part_9076_798882104.1407323209422" ------=_Part_9076_798882104.1407323209422 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i have same error with thisconf file : # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # Example PV Linux guest configuration # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D # # This is a fairly minimal example of what is required for a # Paravirtualised Linux guest. For a more complete guide see xl.cfg(5) # Guest name name =3D "Xp" # 128-bit UUID for the domain as a hexadecimal number. # Use "uuidgen" to generate one if required. # The default behavior is to generate a new UUID each time the guest is sta= rted. #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" # Kernel image to boot kernel =3D "/zImage" # Ramdisk (optional) #ramdisk =3D "/boot/initrd.gz" # Kernel command line options extra =3D "root=3D/dev/vg0/linux-guest-1p2" # Initial memory allocation (MB) memory =3D 512 # Maximum memory (MB) # If this is greater than `memory' then the slack will start ballooned # (this assumes guest kernel support for ballooning) #maxmem =3D 512 # Number of VCPUS vcpus =3D 2 # Network devices # A list of 'vifspec' entries as described in # docs/misc/xl-network-configuration.markdown vif =3D [ 'bridge=3Dbr0' ] # Disk Devices # A list of `diskspec' entries as described in # docs/misc/xl-disk-configuration.txt disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > Message du 06/08/14 10:53 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > > the guest system can only be started in this mode. there is a problems wi= th this mode ? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is= started. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > > > =C2=A0 > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS"=20 > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, > > > I have this error when i execute : > > > =C2=A0 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create:= how=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:= qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or= directory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk v= dev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk v= dev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or director= y > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device = model pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comple= te, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogr= ess: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destro= y > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2 > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > =C2=A0 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu= -system-x86 > > > =C2=A0 > >=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 > > ------=_Part_9076_798882104.1407323209422 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

i have same error with thisconf file :


# =3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
# Example PV Linux gu= est configuration
# =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D
#
# This is a fairly minimal example of what is require= d for a
# Paravirtualised Linux guest. For a more complete guide see x= l.cfg(5)

# Guest name
name =3D "Xp"

# 128-bit UU= ID for the domain as a hexadecimal number.
# Use "uuidgen" to generate= one if required.
# The default behavior is to generate a new UUID eac= h time the guest is started.
#uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXX= XXXXXX"

# Kernel image to boot
kernel =3D "/zImage"
# Ramdisk (optional)
#ramdisk =3D "/boot/initrd.gz"

# K= ernel command line options
extra =3D "root=3D/dev/vg0/linux-guest-1p2"=

# Initial memory allocation (MB)
memory =3D 512

# Maximum memory (MB)
# If this is greater than `memory' then the sla= ck will start ballooned
# (this assumes guest kernel support for ballo= oning)
#maxmem =3D 512

# Number of VCPUS
vcpus =3D 2
# Network devices
# A list of 'vifspec' entries as described= in
# docs/misc/xl-network-configuration.markdown
vif =3D [ 'brid= ge=3Dbr0' ]

# Disk Devices
# A list of `diskspec' entries a= s described in
# docs/misc/xl-disk-configuration.txt
disk =3D [ '= /dev/vg0/guest-linux-1,raw,xvda,rw' ]

> Message du 06/08/14 10:53
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> the guest system can only be started in this mode. there is a probl= ems with this mode ?
>
>
>
>
><= /p>

> Message du 06/08/14 10:21
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > my xl file :
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # Example HVM guest configuratio= n
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> > #
> > # This is a fairly minimal example of w= hat is required for an
> > # HVM guest. For a more complete guid= e see xl.cfg(5)
> >
> > # This configures an HVM rat= her than PV guest
> > builder =3D "hvm"
> >
>= ; > # Guest name
> > name =3D "Xp"
> >
> = > # 128-bit UUID for the domain as a hexadecimal number.
> > = # Use "uuidgen" to generate one if required.
> > # The default b= ehavior is to generate a new UUID each time the guest is started.
>= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> &= gt; #viridian =3D 1
> >
> > # Initial memory allocat= ion (MB)
> > memory =3D 512
> >
> > # Max= imum memory (MB)
> > # If this is greater than `memory' then the= slack will start ballooned
> > # (this assumes guest kernel sup= port for ballooning)
> > #maxmem =3D 512
> >
&g= t; > # Number of VCPUS
> > vcpus =3D 2
> >
&= gt; > # Network devices
> > # A list of 'vifspec' entries as = described in
> > # docs/misc/xl-network-configuration.markdown> > vif =3D [ 'bridge=3Dbr0' ]
> >
> > # D= isk Devices
> > # A list of `diskspec' entries as described in> > # docs/misc/xl-disk-configuration.txt
> > disk =3D= [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D 1=
> > #vnc =3D 1
> >
> >

> > =C2=A0

> Message du 06/08/14 10:03
> > > De : "Gi= lles DALMAS" <gdalmas@wanadoo.fr>
> > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Copie =C3=A0 :
> > > Objet : [Mira= geOS-devel] error when i create hvm guest
> > >
> &g= t; >

> > > hello,

> > > I have this error when i execute :

> > > =C2=A0

> > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf=
> > Parsing config from /etc/xen/xl.conf
> > libxl: = debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil= ) callback=3D(nil) poller=3D0x32578
> > libxl: verbose: libxl_cr= eate.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, us= e qemu-xen-traditional instead: No such file or directory
> > li= bxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3D= xvda spec.backend=3Dunknown
> > libxl: error: libxl_device.c:265= :libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/= guest-linux-1: No such file or directory
> > libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
> > libxl: error: libxl.c:1421:libx= l__destroy_domid: libxl__destroy_device_model failed for 9
> > l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, r= c=3D-3
> > libxl: debug: libxl_create.c:1356:do_domain_create: a= o 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
> > libxl: d= ebug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> = > xc: debug: hypercall buffer: total allocations:26 total releases:26> > xc: debug: hypercall buffer: current allocations:0 maximum all= ocations:2
> > xc: debug: hypercall buffer: cache current size:2=
> > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > =C2=A0

> > > i have a cubietruck arm and i have installed qemu-system-= arm and qemu-system-x86

> > > =C2=A0


> >
> >
> > ___________________________= ____________________
> > MirageOS-devel mailing list
> &= gt; MirageOS-devel@l= ists.xenproject.org
> > http://lists.xenproject.org/cgi= -bin/mailman/listinfo/mirageos-devel
> >
> >
_______________________________________________
>= > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenpro= ject.org
> > http://lists.xenproject.org/c= gi-bin/mailman/listinfo/mirageos-devel
> >
------=_Part_9076_798882104.1407323209422-- --===============2306264045619511285== 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 --===============2306264045619511285==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 14:45:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 14: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 1XF2Sh-0003W6-8q; Wed, 06 Aug 2014 14:45:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF2Se-0003W1-29 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 14:45:06 +0000 Received: from [85.158.139.211:19685] by server-12.bemta-5.messagelabs.com id FC/D0-22251-F6F32E35; Wed, 06 Aug 2014 14:45:03 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-206.messagelabs.com!1407336302!4654589!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18966 invoked from network); 6 Aug 2014 14:45:03 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-3.tower-206.messagelabs.com with SMTP; 6 Aug 2014 14:45:03 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d38 with ME id bSl21o00K1EBZFu03Sl2cv; Wed, 06 Aug 2014 16:45:02 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 16:45:02 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 16:45:02 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2858330432928781761==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2858330432928781761== Content-Type: multipart/alternative; boundary="----=_Part_13885_829782865.1407336302472" ------=_Part_13885_829782865.1407336302472 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit hello, normally, with the cubie.img file of xen-arm-builder, is it possible to have an graphical interface ? lxde or other ? ------=_Part_13885_829782865.1407336302472 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

hello,

normally, with the cubie.img file of xen-arm-builder, is it possible to have an graphical interface ? lxde or other ?

------=_Part_13885_829782865.1407336302472-- --===============2858330432928781761== 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 --===============2858330432928781761==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 14:45:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 14: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 1XF2Sh-0003W6-8q; Wed, 06 Aug 2014 14:45:07 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF2Se-0003W1-29 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 14:45:06 +0000 Received: from [85.158.139.211:19685] by server-12.bemta-5.messagelabs.com id FC/D0-22251-F6F32E35; Wed, 06 Aug 2014 14:45:03 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-206.messagelabs.com!1407336302!4654589!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_00_10,HTML_MESSAGE, HTML_SHORT_LENGTH X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18966 invoked from network); 6 Aug 2014 14:45:03 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-3.tower-206.messagelabs.com with SMTP; 6 Aug 2014 14:45:03 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d38 with ME id bSl21o00K1EBZFu03Sl2cv; Wed, 06 Aug 2014 16:45:02 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 16:45:02 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 16:45:02 +0200 (CEST) From: Gilles DALMAS To: "mirageos-devel@lists.xenproject.org" Message-ID: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-REPLYTO: |~| Subject: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2858330432928781761==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2858330432928781761== Content-Type: multipart/alternative; boundary="----=_Part_13885_829782865.1407336302472" ------=_Part_13885_829782865.1407336302472 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit hello, normally, with the cubie.img file of xen-arm-builder, is it possible to have an graphical interface ? lxde or other ? ------=_Part_13885_829782865.1407336302472 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

hello,

normally, with the cubie.img file of xen-arm-builder, is it possible to have an graphical interface ? lxde or other ?

------=_Part_13885_829782865.1407336302472-- --===============2858330432928781761== 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 --===============2858330432928781761==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 15:05:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 15:05: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 1XF2mC-0005ru-8e; Wed, 06 Aug 2014 15:05:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF2mA-0005rd-I3 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 15:05:14 +0000 Received: from [193.109.254.147:10481] by server-6.bemta-14.messagelabs.com id 12/6C-31278-92442E35; Wed, 06 Aug 2014 15:05:13 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1407337512!14154066!1 X-Originating-IP: [209.85.214.175] 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 29228 invoked from network); 6 Aug 2014 15:05:13 -0000 Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Aug 2014 15:05:13 -0000 Received: by mail-ob0-f175.google.com with SMTP id wp18so1897869obc.34 for ; Wed, 06 Aug 2014 08:05:11 -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=+uVjReDlhDlJyWTtvpFtDubDQXssqPEUI+oXraoyZlA=; b=x2nWHXtWOMK00h7/u27OJHUQrq3YI4/Spkic+EwzkCgMwRGZUCCADO/FeuV/sdkMwJ IxA+euiKJMmqGSbVRk3LqkCRHzklwf1J8s9+Pm0TKzn8jeRh1jSYCyArSiZjsvcDVYN2 W21nnufO9Ks5JiteqbXPMWVHUR+gMLd1PLFVvwNMfXzs34nCmhYLkEYbibQa7YkqYnf2 u3Xlv34s7l/L3sQt45HNWWba0MYXVluyUFbYpF+V8zjyTcvybKhidmWoiodUYIugtbTw 46RE1x5dzkrPeV1zLISW8kPalaQfnK561b+O5xhz+NquHUDu86j7BCnnKtZTQnHzThLx 7SMA== MIME-Version: 1.0 X-Received: by 10.182.205.231 with SMTP id lj7mr15603362obc.37.1407337511912; Wed, 06 Aug 2014 08:05:11 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Wed, 6 Aug 2014 08:05:11 -0700 (PDT) In-Reply-To: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> Date: Wed, 6 Aug 2014 16:05:11 +0100 Message-ID: From: Thomas Leonard To: Gilles DALMAS Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 6 August 2014 15:45, Gilles DALMAS wrote: > hello, > > normally, with the cubie.img file of xen-arm-builder, is it possible to have > an graphical interface ? lxde or other ? Did you try it? Did you get an error? -- 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 Aug 06 15:05:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 15:05: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 1XF2mC-0005ru-8e; Wed, 06 Aug 2014 15:05:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF2mA-0005rd-I3 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 15:05:14 +0000 Received: from [193.109.254.147:10481] by server-6.bemta-14.messagelabs.com id 12/6C-31278-92442E35; Wed, 06 Aug 2014 15:05:13 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1407337512!14154066!1 X-Originating-IP: [209.85.214.175] 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 29228 invoked from network); 6 Aug 2014 15:05:13 -0000 Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 6 Aug 2014 15:05:13 -0000 Received: by mail-ob0-f175.google.com with SMTP id wp18so1897869obc.34 for ; Wed, 06 Aug 2014 08:05:11 -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=+uVjReDlhDlJyWTtvpFtDubDQXssqPEUI+oXraoyZlA=; b=x2nWHXtWOMK00h7/u27OJHUQrq3YI4/Spkic+EwzkCgMwRGZUCCADO/FeuV/sdkMwJ IxA+euiKJMmqGSbVRk3LqkCRHzklwf1J8s9+Pm0TKzn8jeRh1jSYCyArSiZjsvcDVYN2 W21nnufO9Ks5JiteqbXPMWVHUR+gMLd1PLFVvwNMfXzs34nCmhYLkEYbibQa7YkqYnf2 u3Xlv34s7l/L3sQt45HNWWba0MYXVluyUFbYpF+V8zjyTcvybKhidmWoiodUYIugtbTw 46RE1x5dzkrPeV1zLISW8kPalaQfnK561b+O5xhz+NquHUDu86j7BCnnKtZTQnHzThLx 7SMA== MIME-Version: 1.0 X-Received: by 10.182.205.231 with SMTP id lj7mr15603362obc.37.1407337511912; Wed, 06 Aug 2014 08:05:11 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Wed, 6 Aug 2014 08:05:11 -0700 (PDT) In-Reply-To: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> Date: Wed, 6 Aug 2014 16:05:11 +0100 Message-ID: From: Thomas Leonard To: Gilles DALMAS Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 6 August 2014 15:45, Gilles DALMAS wrote: > hello, > > normally, with the cubie.img file of xen-arm-builder, is it possible to have > an graphical interface ? lxde or other ? Did you try it? Did you get an error? -- 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 Aug 06 18:11:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 18:11: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 1XF5g4-0006MP-Ci; Wed, 06 Aug 2014 18:11:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF5g3-0006MD-R2 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 18:11:07 +0000 Received: from [85.158.143.35:9185] by server-2.bemta-4.messagelabs.com id FD/51-04525-BBF62E35; Wed, 06 Aug 2014 18:11:07 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-14.tower-21.messagelabs.com!1407348665!13915639!1 X-Originating-IP: [80.12.242.128] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31687 invoked from network); 6 Aug 2014 18:11:05 -0000 Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by server-14.tower-21.messagelabs.com with SMTP; 6 Aug 2014 18:11:05 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d64 with ME id bWB41o00M1EBZFu03WB45h; Wed, 06 Aug 2014 20:11:04 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 20:11:04 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 20:11:04 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <1566309735.18869.1407348664783.JavaMail.www@wwinf1c13> In-Reply-To: References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6108767133464660307==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6108767133464660307== Content-Type: multipart/alternative; boundary="----=_Part_18868_1783700679.1407348664767" ------=_Part_18868_1783700679.1407348664767 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nothing, just nothing. Black screen. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 > ------=_Part_18868_1783700679.1407348664767 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Nothing, just nothing. Black screen.



> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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
> ------=_Part_18868_1783700679.1407348664767-- --===============6108767133464660307== 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 --===============6108767133464660307==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 18:11:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 18:11: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 1XF5g4-0006MP-Ci; Wed, 06 Aug 2014 18:11:08 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF5g3-0006MD-R2 for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 18:11:07 +0000 Received: from [85.158.143.35:9185] by server-2.bemta-4.messagelabs.com id FD/51-04525-BBF62E35; Wed, 06 Aug 2014 18:11:07 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-14.tower-21.messagelabs.com!1407348665!13915639!1 X-Originating-IP: [80.12.242.128] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31687 invoked from network); 6 Aug 2014 18:11:05 -0000 Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by server-14.tower-21.messagelabs.com with SMTP; 6 Aug 2014 18:11:05 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d64 with ME id bWB41o00M1EBZFu03WB45h; Wed, 06 Aug 2014 20:11:04 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 20:11:04 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 20:11:04 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <1566309735.18869.1407348664783.JavaMail.www@wwinf1c13> In-Reply-To: References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6108767133464660307==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6108767133464660307== Content-Type: multipart/alternative; boundary="----=_Part_18868_1783700679.1407348664767" ------=_Part_18868_1783700679.1407348664767 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nothing, just nothing. Black screen. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 > ------=_Part_18868_1783700679.1407348664767 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Nothing, just nothing. Black screen.



> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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
> ------=_Part_18868_1783700679.1407348664767-- --===============6108767133464660307== 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 --===============6108767133464660307==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 18:14:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 18:14:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF5iv-0006Ra-Oj; Wed, 06 Aug 2014 18:14:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF5iu-0006RU-KS for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 18:14:04 +0000 Received: from [85.158.139.211:48954] by server-15.bemta-5.messagelabs.com id 36/F4-12002-B6072E35; Wed, 06 Aug 2014 18:14:03 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-6.tower-206.messagelabs.com!1407348843!12269794!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27162 invoked from network); 6 Aug 2014 18:14:03 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-6.tower-206.messagelabs.com with SMTP; 6 Aug 2014 18:14:03 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d69 with ME id bWE21o00F1EBZFu03WE2on; Wed, 06 Aug 2014 20:14:02 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 20:14:02 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 20:14:02 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> In-Reply-To: References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2520530643720666147==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2520530643720666147== Content-Type: multipart/alternative; boundary="----=_Part_19007_1293093372.1407348842500" ------=_Part_19007_1293093372.1407348842500 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i have installed lxde because i don't know if there was a graphic environme= nt. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 > ------=_Part_19007_1293093372.1407348842500 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

i have installed lxde because i don't know if there was a graphic enviro= nment.




> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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
> ------=_Part_19007_1293093372.1407348842500-- --===============2520530643720666147== 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 --===============2520530643720666147==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 18:14:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 18:14:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF5iv-0006Ra-Oj; Wed, 06 Aug 2014 18:14:05 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF5iu-0006RU-KS for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 18:14:04 +0000 Received: from [85.158.139.211:48954] by server-15.bemta-5.messagelabs.com id 36/F4-12002-B6072E35; Wed, 06 Aug 2014 18:14:03 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-6.tower-206.messagelabs.com!1407348843!12269794!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27162 invoked from network); 6 Aug 2014 18:14:03 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-6.tower-206.messagelabs.com with SMTP; 6 Aug 2014 18:14:03 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d69 with ME id bWE21o00F1EBZFu03WE2on; Wed, 06 Aug 2014 20:14:02 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 20:14:02 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 20:14:02 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> In-Reply-To: References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2520530643720666147==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2520530643720666147== Content-Type: multipart/alternative; boundary="----=_Part_19007_1293093372.1407348842500" ------=_Part_19007_1293093372.1407348842500 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i have installed lxde because i don't know if there was a graphic environme= nt. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 > ------=_Part_19007_1293093372.1407348842500 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

i have installed lxde because i don't know if there was a graphic enviro= nment.




> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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
> ------=_Part_19007_1293093372.1407348842500-- --===============2520530643720666147== 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 --===============2520530643720666147==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 19:17:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 19:17: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 1XF6if-0000lg-7i; Wed, 06 Aug 2014 19:17:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF6id-0000lb-Qd for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 19:17:52 +0000 Received: from [85.158.143.35:25059] by server-1.bemta-4.messagelabs.com id 38/79-05872-F5F72E35; Wed, 06 Aug 2014 19:17:51 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-5.tower-21.messagelabs.com!1407352669!13862504!1 X-Originating-IP: [80.12.242.128] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3215 invoked from network); 6 Aug 2014 19:17:50 -0000 Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by server-5.tower-21.messagelabs.com with SMTP; 6 Aug 2014 19:17:50 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d12 with ME id bXHp1o00B1EBZFu03XHpXG; Wed, 06 Aug 2014 21:17:49 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 21:17:49 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 21:17:49 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <244724588.20228.1407352669454.JavaMail.www@wwinf1c13> In-Reply-To: <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_20226_971071809.1407352669442" X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org ------=_Part_20226_971071809.1407352669442 Content-Type: multipart/alternative; boundary="----=_Part_20227_2075660310.1407352669443" ------=_Part_20227_2075660310.1407352669443 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable but on cubietruck image for ubuntu, debian and co, they use a uEnv.txt and = script.bin file=C2=A0 > Message du 06/08/14 20:14 > De : "Gilles DALMAS"=20 > A : "Thomas Leonard"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > > i have installed lxde because i don't know if there was a graphic environ= ment. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 ------=_Part_20227_2075660310.1407352669443 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

but on cubietruck image for ubuntu, debian and co, they use a uEnv.txt a= nd script.bin file=C2=A0




> Message du 06/08/14 20:14
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "Thomas Leonard" <talex5@gma= il.com>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
>

> i have installed lxde because i don't know if there was a graphic e= nvironment.




> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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.xe= nproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mira= geos-devel

------=_Part_20227_2075660310.1407352669443-- ------=_Part_20226_971071809.1407352669442 Content-Type: application/octet-stream; name=script.fex content-transfer-encoding: base64 Content-Disposition: attachment; size=33184; filename=script.fex W3Byb2R1Y3RdCnZlcnNpb24gPSAiMTAwIgptYWNoaW5lID0gImN1YmlldHJ1Y2siCgpbcGxhdGZv cm1dCmVyYXNlZmxhZyA9IDAKClt0YXJnZXRdCmJvb3RfY2xvY2sgPSA5MTIKZGNkYzJfdm9sID0g MTQ1MApkY2RjM192b2wgPSAxMzAwCmxkbzJfdm9sID0gMzAwMApsZG8zX3ZvbCA9IDI4MDAKbGRv NF92b2wgPSAyODAwCnN0b3JhZ2VfdHlwZSA9IDAKCltjbG9ja10KcGxsMyA9IDI5NwpwbGw0ID0g MzAwCnBsbDYgPSA2MDAKcGxsNyA9IDI5NwpwbGw4ID0gMzM2CgpbY2FyZF9ib290XQpsb2dpY2Fs X3N0YXJ0ID0gNDA5NjAKc3ByaXRlX2dwaW8wID0KCltjYXJkMF9ib290X3BhcmFdCmNhcmRfY3Ry bCA9IDAKY2FyZF9oaWdoX3NwZWVkID0gMQpjYXJkX2xpbmUgPSA0CnNkY19kMSA9IHBvcnQ6UEYw MDwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgpzZGNfZDAgPSBwb3J0OlBGMDE8Mj48MT48ZGVmYXVs dD48ZGVmYXVsdD4Kc2RjX2NsayA9IHBvcnQ6UEYwMjwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgpz ZGNfY21kID0gcG9ydDpQRjAzPDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnNkY19kMyA9IHBvcnQ6 UEYwNDwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgpzZGNfZDIgPSBwb3J0OlBGMDU8Mj48MT48ZGVm YXVsdD48ZGVmYXVsdD4KCltjYXJkMl9ib290X3BhcmFdCmNhcmRfY3RybCA9IDIKY2FyZF9oaWdo X3NwZWVkID0gMQpjYXJkX2xpbmUgPSA0CnNkY19jbWQgPSBwb3J0OlBDMDY8Mz48MT48ZGVmYXVs dD48ZGVmYXVsdD4Kc2RjX2NsayA9IHBvcnQ6UEMwNzwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgpz ZGNfZDAgPSBwb3J0OlBDMDg8Mz48MT48ZGVmYXVsdD48ZGVmYXVsdD4Kc2RjX2QxID0gcG9ydDpQ QzA5PDM+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnNkY19kMiA9IHBvcnQ6UEMxMDwzPjwxPjxkZWZh dWx0PjxkZWZhdWx0PgpzZGNfZDMgPSBwb3J0OlBDMTE8Mz48MT48ZGVmYXVsdD48ZGVmYXVsdD4K Clt0d2lfcGFyYV0KdHdpX3BvcnQgPSAwCnR3aV9zY2wgPSBwb3J0OlBCMDA8Mj48ZGVmYXVsdD48 ZGVmYXVsdD48ZGVmYXVsdD4KdHdpX3NkYSA9IHBvcnQ6UEIwMTwyPjxkZWZhdWx0PjxkZWZhdWx0 PjxkZWZhdWx0PgoKW3VhcnRfcGFyYV0KdWFydF9kZWJ1Z19wb3J0ID0gMAp1YXJ0X2RlYnVnX3R4 ID0gcG9ydDpQQjIyPDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfZGVidWdfcnggPSBwb3J0 OlBCMjM8Mj48MT48ZGVmYXVsdD48ZGVmYXVsdD4KClt1YXJ0X2ZvcmNlX2RlYnVnXQp1YXJ0X2Rl YnVnX3BvcnQgPSAwCnVhcnRfZGVidWdfdHggPSBwb3J0OlBGMDI8ND48MT48ZGVmYXVsdD48ZGVm YXVsdD4KdWFydF9kZWJ1Z19yeCA9IHBvcnQ6UEYwNDw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoK W2p0YWdfcGFyYV0KanRhZ19lbmFibGUgPSAwCmp0YWdfbXMgPSBwb3J0OlBCMTQ8Mz48ZGVmYXVs dD48ZGVmYXVsdD48ZGVmYXVsdD4KanRhZ19jayA9IHBvcnQ6UEIxNTwzPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0PgpqdGFnX2RvID0gcG9ydDpQQjE2PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRl ZmF1bHQ+Cmp0YWdfZGkgPSBwb3J0OlBCMTc8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4K CltwbV9wYXJhXQpzdGFuZGJ5X21vZGUgPSAwCgpbZHJhbV9wYXJhXQpkcmFtX2Jhc2VhZGRyID0g MHg0MDAwMDAwMApkcmFtX2NsayA9IDQzMgpkcmFtX3R5cGUgPSAzCmRyYW1fcmFua19udW0gPSAt MQpkcmFtX2NoaXBfZGVuc2l0eSA9IC0xCmRyYW1faW9fd2lkdGggPSAtMQpkcmFtX2J1c193aWR0 aCA9IC0xCmRyYW1fY2FzID0gOQpkcmFtX3pxID0gMHg3ZgpkcmFtX29kdF9lbiA9IDAKZHJhbV9z aXplID0gLTEKZHJhbV90cHIwID0gMHg0MmQ4OTliNwpkcmFtX3RwcjEgPSAweGEwOTAKZHJhbV90 cHIyID0gMHgyMmEwMApkcmFtX3RwcjMgPSAweDAKZHJhbV90cHI0ID0gMHgxCmRyYW1fdHByNSA9 IDB4MApkcmFtX2VtcjEgPSAweDQKZHJhbV9lbXIyID0gMHgxMApkcmFtX2VtcjMgPSAweDAKCltt YWxpX3BhcmFdCm1hbGlfdXNlZCA9IDEKbWFsaV9jbGtkaXYgPSAxCgpbZ21hY19wYXJhXQpnbWFj X3VzZWQgPSAxCmdtYWNfcnhkMyA9IHBvcnQ6UEEwMDw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0Pgpn bWFjX3J4ZDIgPSBwb3J0OlBBMDE8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY19yeGQxID0g cG9ydDpQQTAyPDU+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+CmdtYWNfcnhkMCA9IHBvcnQ6UEEwMzw1 PjxkZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3R4ZDMgPSBwb3J0OlBBMDQ8NT48ZGVmYXVsdD48 Mz48ZGVmYXVsdD4KZ21hY190eGQyID0gcG9ydDpQQTA1PDU+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+ CmdtYWNfdHhkMSA9IHBvcnQ6UEEwNjw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3R4ZDAg PSBwb3J0OlBBMDc8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY19yeGNsayA9IHBvcnQ6UEEw ODw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3J4ZXJyID0gcG9ydDpQQTA5PDA+PGRlZmF1 bHQ+PDM+PGRlZmF1bHQ+CmdtYWNfcnhjdGwgPSBwb3J0OlBBMTA8NT48ZGVmYXVsdD48Mz48ZGVm YXVsdD4KZ21hY19tZGMgPSBwb3J0OlBBMTE8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY19t ZGlvID0gcG9ydDpQQTEyPDU+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+CmdtYWNfdHhjdGwgPSBwb3J0 OlBBMTM8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY190eGNsayA9IHBvcnQ6UEExNDwwPjxk ZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3R4Y2sgPSBwb3J0OlBBMTU8NT48ZGVmYXVsdD48Mz48 ZGVmYXVsdD4KZ21hY19jbGtpbiA9IHBvcnQ6UEExNjw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0Pgpn bWFjX3R4ZXJyID0gcG9ydDpQQTE3PDA+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+CgpbdHdpMF9wYXJh XQp0d2kwX3VzZWQgPSAxCnR3aTBfc2NsID0gcG9ydDpQQjAwPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+CnR3aTBfc2RhID0gcG9ydDpQQjAxPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1 bHQ+CgpbdHdpMV9wYXJhXQp0d2kxX3VzZWQgPSAwCnR3aTFfc2NsID0gcG9ydDpQQjE4PDI+PGRl ZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CnR3aTFfc2RhID0gcG9ydDpQQjE5PDI+PGRlZmF1bHQ+ PGRlZmF1bHQ+PGRlZmF1bHQ+CgpbdHdpMl9wYXJhXQp0d2kyX3VzZWQgPSAwCnR3aTJfc2NsID0g cG9ydDpQQjIwPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CnR3aTJfc2RhID0gcG9ydDpQ QjIxPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CgpbdWFydF9wYXJhMF0KdWFydF91c2Vk ID0gMQp1YXJ0X3BvcnQgPSAwCnVhcnRfdHlwZSA9IDIKdWFydF90eCA9IHBvcnQ6UEIyMjwyPjwx PjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X3J4ID0gcG9ydDpQQjIzPDI+PDE+PGRlZmF1bHQ+PGRl ZmF1bHQ+CgpbdWFydF9wYXJhMV0KdWFydF91c2VkID0gMAp1YXJ0X3BvcnQgPSAxCnVhcnRfdHlw ZSA9IDgKdWFydF90eCA9IHBvcnQ6UEExMDw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X3J4 ID0gcG9ydDpQQTExPDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfcnRzID0gcG9ydDpQQTEy PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfY3RzID0gcG9ydDpQQTEzPDQ+PDE+PGRlZmF1 bHQ+PGRlZmF1bHQ+CnVhcnRfZHRyID0gcG9ydDpQQTE0PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+ CnVhcnRfZHNyID0gcG9ydDpQQTE1PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfZGNkID0g cG9ydDpQQTE2PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfcmluZyA9IHBvcnQ6UEExNzw0 PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTJdCnVhcnRfdXNlZCA9IDEKdWFydF9w b3J0ID0gMgp1YXJ0X3R5cGUgPSA0CnVhcnRfdHggPSBwb3J0OlBJMTg8Mz48MT48ZGVmYXVsdD48 ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEkxOTwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0 X3J0cyA9IHBvcnQ6UEkxNjwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X2N0cyA9IHBvcnQ6 UEkxNzwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTNdCnVhcnRfdXNlZCA9IDAK dWFydF9wb3J0ID0gMwp1YXJ0X3R5cGUgPSA0CnVhcnRfdHggPSBwb3J0OlBIMDA8ND48MT48ZGVm YXVsdD48ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEgwMTw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0 Pgp1YXJ0X3J0cyA9IHBvcnQ6UEgwMjw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X2N0cyA9 IHBvcnQ6UEgwMzw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTRdCnVhcnRfdXNl ZCA9IDAKdWFydF9wb3J0ID0gNAp1YXJ0X3R5cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBIMDQ8ND48 MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEgwNTw0PjwxPjxkZWZhdWx0Pjxk ZWZhdWx0PgoKW3VhcnRfcGFyYTVdCnVhcnRfdXNlZCA9IDAKdWFydF9wb3J0ID0gNQp1YXJ0X3R5 cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBIMDY8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFydF9y eCA9IHBvcnQ6UEgwNzw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTZdCnVhcnRf dXNlZCA9IDAKdWFydF9wb3J0ID0gNgp1YXJ0X3R5cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBBMTI8 ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEExMzw0PjwxPjxkZWZhdWx0 PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTddCnVhcnRfdXNlZCA9IDAKdWFydF9wb3J0ID0gNwp1YXJ0 X3R5cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBBMTQ8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFy dF9yeCA9IHBvcnQ6UEExNTw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3NwaTBfcGFyYV0Kc3Bp X3VzZWQgPSAwCnNwaV9jc19iaXRtYXAgPSAxCnNwaV9jczAgPSBwb3J0OlBJMTA8Mj48ZGVmYXVs dD48ZGVmYXVsdD48ZGVmYXVsdD4Kc3BpX2NzMSA9IHBvcnQ6UEkxNDwyPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0PgpzcGlfc2NsayA9IHBvcnQ6UEkxMTwyPjxkZWZhdWx0PjxkZWZhdWx0Pjxk ZWZhdWx0PgpzcGlfbW9zaSA9IHBvcnQ6UEkxMjwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0 PgpzcGlfbWlzbyA9IHBvcnQ6UEkxMzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgoKW3Nw aTFfcGFyYV0Kc3BpX3VzZWQgPSAwCnNwaV9jc19iaXRtYXAgPSAxCnNwaV9jczAgPSBwb3J0OlBB MDA8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc3BpX2NzMSA9IHBvcnQ6UEEwNDwzPjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfc2NsayA9IHBvcnQ6UEEwMTwzPjxkZWZhdWx0 PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbW9zaSA9IHBvcnQ6UEEwMjwzPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0PgpzcGlfbWlzbyA9IHBvcnQ6UEEwMzwzPjxkZWZhdWx0PjxkZWZhdWx0Pjxk ZWZhdWx0PgoKW3NwaTJfcGFyYV0Kc3BpX3VzZWQgPSAwCnNwaV9jc19iaXRtYXAgPSAxCnNwaV9j czAgPSBwb3J0OlBDMTk8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc3BpX2NzMSA9IHBv cnQ6UEIxMzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfc2NsayA9IHBvcnQ6UEMy MDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbW9zaSA9IHBvcnQ6UEMyMTwzPjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbWlzbyA9IHBvcnQ6UEMyMjwzPjxkZWZhdWx0 PjxkZWZhdWx0PjxkZWZhdWx0PgoKW3NwaTNfcGFyYV0Kc3BpX3VzZWQgPSAwCnNwaV9jc19iaXRt YXAgPSAxCnNwaV9jczAgPSBwb3J0OlBBMDU8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4K c3BpX2NzMSA9IHBvcnQ6UEEwOTwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfc2Ns ayA9IHBvcnQ6UEEwNjwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbW9zaSA9IHBv cnQ6UEEwNzwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbWlzbyA9IHBvcnQ6UEEw ODwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgoKW2N0cF9wYXJhXQpjdHBfdXNlZCA9IDAK Y3RwX25hbWUgPSAiZ3Q4MTEiCmN0cF90d2lfaWQgPSAyCmN0cF90d2lfYWRkciA9IDB4NDAKY3Rw X3NjcmVlbl9tYXhfeCA9IDEwMjQKY3RwX3NjcmVlbl9tYXhfeSA9IDYwMApjdHBfcmV2ZXJ0X3hf ZmxhZyA9IDAKY3RwX3JldmVydF95X2ZsYWcgPSAwCmN0cF9leGNoYW5nZV94X3lfZmxhZyA9IDEK Y3RwX2Zpcm0gPSAxCmN0cF9pbnRfcG9ydCA9IHBvcnQ6UEgyMTw2PjxkZWZhdWx0PjxkZWZhdWx0 PjxkZWZhdWx0PgpjdHBfd2FrZXVwID0gcG9ydDpQQjEzPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDE+ CgpbY3RwX2xpc3RfcGFyYV0KY3RwX2RldF91c2VkID0gMApmdDV4X3RzID0gMApndDgyeCA9IDAK Z3NsWDY4MCA9IDAKZ3Q5eHhfdHMgPSAwCmd0ODExID0gMAoKW3RrZXlfcGFyYV0KdGtleV91c2Vk ID0gMAp0a2V5X3R3aV9pZCA9IDIKdGtleV90d2lfYWRkciA9IDB4NjIKdGtleV9pbnQgPSBwb3J0 OlBJMTM8Nj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KClttb3Rvcl9wYXJhXQptb3Rvcl91 c2VkID0gMAptb3Rvcl9zaGFrZSA9IHBvcnQ6UEIwMzwxPjxkZWZhdWx0PjxkZWZhdWx0PjwxPgoK W2dwaW9fcGFyYV0KZ3Bpb191c2VkID0gMQpncGlvX251bSA9IDIKZ3Bpb19waW5fMSA9IHBvcnQ6 UEgyMDwxPjxkZWZhdWx0PjxkZWZhdWx0PjwxPgpncGlvX3Bpbl8yID0gcG9ydDpQSDEwPDA+PGRl ZmF1bHQ+PGRlZmF1bHQ+PDA+CgpbbGVkc19wYXJhXQpsZWRzX3VzZWQgPSAxCmxlZHNfbnVtID0g NApsZWRzX3Bpbl8xID0gcG9ydDpQSDIxPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDA+CmxlZHNfbmFt ZV8xID0gImJsdWU6cGgyMTpsZWQxIgpsZWRzX2RlZmF1bHRfMSA9IDAKbGVkc190cmlnZ2VyXzEg PSAiaGVhcnRiZWF0IgpsZWRzX3Bpbl8yID0gcG9ydDpQSDIwPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+ PDA+CmxlZHNfbmFtZV8yID0gIm9yYW5nZTpwaDIwOmxlZDIiCmxlZHNfZGVmYXVsdF8yID0gMAps ZWRzX3RyaWdnZXJfMiA9ICJjcHUwIgpsZWRzX3Bpbl8zID0gcG9ydDpQSDExPDE+PGRlZmF1bHQ+ PGRlZmF1bHQ+PDA+CmxlZHNfbmFtZV8zID0gIndoaXRlOnBoMTE6bGVkMyIKbGVkc19kZWZhdWx0 XzMgPSAwCmxlZHNfdHJpZ2dlcl8zID0gImNwdTEiCmxlZHNfcGluXzQgPSBwb3J0OlBIMDc8MT48 ZGVmYXVsdD48ZGVmYXVsdD48MD4KbGVkc19uYW1lXzQgPSAiZ3JlZW46cGgwNzpsZWQ0IgpsZWRz X2RlZmF1bHRfNCA9IDEKbGVkc190cmlnZ2VyXzQgPSAibW1jMCIKCltuYW5kX3BhcmFdCm5hbmRf dXNlZCA9IDEKbmFuZF93ZSA9IHBvcnQ6UEMwMDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0 PgpuYW5kX2FsZSA9IHBvcnQ6UEMwMTwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5k X2NsZSA9IHBvcnQ6UEMwMjwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2NlMSA9 IHBvcnQ6UEMwMzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2NlMCA9IHBvcnQ6 UEMwNDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX25yZSA9IHBvcnQ6UEMwNTwy PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX3JiMCA9IHBvcnQ6UEMwNjwyPjxkZWZh dWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX3JiMSA9IHBvcnQ6UEMwNzwyPjxkZWZhdWx0Pjxk ZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2QwID0gcG9ydDpQQzA4PDI+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+Cm5hbmRfZDEgPSBwb3J0OlBDMDk8Mj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVs dD4KbmFuZF9kMiA9IHBvcnQ6UEMxMDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5k X2QzID0gcG9ydDpQQzExPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+Cm5hbmRfZDQgPSBw b3J0OlBDMTI8Mj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KbmFuZF9kNSA9IHBvcnQ6UEMx MzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2Q2ID0gcG9ydDpQQzE0PDI+PGRl ZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+Cm5hbmRfZDcgPSBwb3J0OlBDMTU8Mj48ZGVmYXVsdD48 ZGVmYXVsdD48ZGVmYXVsdD4KbmFuZF93cCA9IHBvcnQ6UEMxNjwyPjxkZWZhdWx0PjxkZWZhdWx0 PjxkZWZhdWx0PgpuYW5kX2NlMiA9IHBvcnQ6UEMxNzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0PgpuYW5kX2NlMyA9IHBvcnQ6UEMxODwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpu YW5kX2NlNCA9Cm5hbmRfY2U1ID0KbmFuZF9jZTYgPQpuYW5kX2NlNyA9Cm5hbmRfc3BpID0gcG9y dDpQQzIzPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+Cm5hbmRfbmRxcyA9IHBvcnQ6UEMy NDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpnb29kX2Jsb2NrX3JhdGlvID0gMAoKW2Rp c3BfaW5pdF0KZGlzcF9pbml0X2VuYWJsZSA9IDEKZGlzcF9tb2RlID0gMApzY3JlZW4wX291dHB1 dF90eXBlID0gMwpzY3JlZW4wX291dHB1dF9tb2RlID0gNApzY3JlZW4xX291dHB1dF90eXBlID0g MApzY3JlZW4xX291dHB1dF9tb2RlID0gNApmYjBfd2lkdGggPSAxMDI0CmZiMF9oZWlnaHQgPSA3 NjgKZmIwX2ZyYW1lYnVmZmVyX251bSA9IDIKZmIwX2Zvcm1hdCA9IDEwCmZiMF9waXhlbF9zZXF1 ZW5jZSA9IDAKZmIwX3NjYWxlcl9tb2RlX2VuYWJsZSA9IDEKZmIxX3dpZHRoID0gMTAyNApmYjFf aGVpZ2h0ID0gNzY4CmZiMV9mcmFtZWJ1ZmZlcl9udW0gPSAyCmZiMV9mb3JtYXQgPSAxMApmYjFf cGl4ZWxfc2VxdWVuY2UgPSAwCmZiMV9zY2FsZXJfbW9kZV9lbmFibGUgPSAwCmxjZDBfYmFja2xp Z2h0ID0gMTk3CmxjZDFfYmFja2xpZ2h0ID0gMTk3CmxjZDBfYnJpZ2h0ID0gNTAKbGNkMF9jb250 cmFzdCA9IDUwCmxjZDBfc2F0dXJhdGlvbiA9IDU3CmxjZDBfaHVlID0gNTAKbGNkMV9icmlnaHQg PSA1MApsY2QxX2NvbnRyYXN0ID0gNTAKbGNkMV9zYXR1cmF0aW9uID0gNTcKbGNkMV9odWUgPSA1 MAoKW2xjZDBfcGFyYV0KbGNkX3VzZWQgPSAxCmxjZF94ID0gMTAyNApsY2RfeSA9IDYwMApsY2Rf ZGNsa19mcmVxID0gNTEKbGNkX3B3bV9ub3RfdXNlZCA9IDAKbGNkX3B3bV9jaCA9IDAKbGNkX3B3 bV9mcmVxID0gMTAwMDAKbGNkX3B3bV9wb2wgPSAxCmxjZF9tYXhfYnJpZ2h0ID0gMjQwCmxjZF9t aW5fYnJpZ2h0ID0gNjQKbGNkX2lmID0gMApsY2RfaGJwID0gMTU4CmxjZF9odCA9IDEzNDQKbGNk X3ZicCA9IDI1CmxjZF92dCA9IDEyNzAKbGNkX3ZzcHcgPSAzCmxjZF9oc3B3ID0gMjAKbGNkX2h2 X2lmID0gMApsY2RfaHZfc21vZGUgPSAwCmxjZF9odl9zODg4X2lmID0gMApsY2RfaHZfc3l1dl9p ZiA9IDAKbGNkX2x2ZHNfY2ggPSAwCmxjZF9sdmRzX21vZGUgPSAwCmxjZF9sdmRzX2JpdHdpZHRo ID0gMApsY2RfbHZkc19pb19jcm9zcyA9IDAKbGNkX2NwdV9pZiA9IDAKbGNkX2ZybSA9IDEKbGNk X2lvX2NmZzAgPSAwCmxjZF9nYW1tYV9jb3JyZWN0aW9uX2VuID0gMApsY2RfZ2FtbWFfdGJsXzAg PSAweDAKbGNkX2dhbW1hX3RibF8xID0gMHgxMDEwMQpsY2RfZ2FtbWFfdGJsXzI1NSA9IDB4ZmZm ZmZmCmxjZF9ibF9lbl91c2VkID0gMApsY2RfYmxfZW4gPSBwb3J0OlBIMDc8MT48MD48ZGVmYXVs dD48MT4KbGNkX3Bvd2VyX3VzZWQgPSAwCmxjZF9wb3dlciA9IHBvcnQ6UEgwODwxPjwwPjxkZWZh dWx0PjwxPgpsY2RfcHdtX3VzZWQgPSAwCmxjZF9wd20gPSBwb3J0OlBCMDI8Mj48MD48ZGVmYXVs dD48ZGVmYXVsdD4KbGNkZDAgPSBwb3J0OlBEMDA8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNk ZDEgPSBwb3J0OlBEMDE8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDIgPSBwb3J0OlBEMDI8 Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDMgPSBwb3J0OlBEMDM8Mj48MD48ZGVmYXVsdD48 ZGVmYXVsdD4KbGNkZDQgPSBwb3J0OlBEMDQ8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDUg PSBwb3J0OlBEMDU8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDYgPSBwb3J0OlBEMDY8Mj48 MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDcgPSBwb3J0OlBEMDc8Mj48MD48ZGVmYXVsdD48ZGVm YXVsdD4KbGNkZDggPSBwb3J0OlBEMDg8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDkgPSBw b3J0OlBEMDk8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDEwID0gcG9ydDpQRDEwPDI+PDA+ PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxMSA9IHBvcnQ6UEQxMTwyPjwwPjxkZWZhdWx0PjxkZWZh dWx0PgpsY2RkMTIgPSBwb3J0OlBEMTI8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDEzID0g cG9ydDpQRDEzPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxNCA9IHBvcnQ6UEQxNDwyPjww PjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTUgPSBwb3J0OlBEMTU8Mj48MD48ZGVmYXVsdD48ZGVm YXVsdD4KbGNkZDE2ID0gcG9ydDpQRDE2PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxNyA9 IHBvcnQ6UEQxNzwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTggPSBwb3J0OlBEMTg8Mj48 MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDE5ID0gcG9ydDpQRDE5PDI+PDA+PGRlZmF1bHQ+PGRl ZmF1bHQ+CmxjZGQyMCA9IHBvcnQ6UEQyMDwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMjEg PSBwb3J0OlBEMjE8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDIyID0gcG9ydDpQRDIyPDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQyMyA9IHBvcnQ6UEQyMzwyPjwwPjxkZWZhdWx0Pjxk ZWZhdWx0PgpsY2RjbGsgPSBwb3J0OlBEMjQ8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZGUg PSBwb3J0OlBEMjU8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkaHN5bmMgPSBwb3J0OlBEMjY8 Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkdnN5bmMgPSBwb3J0OlBEMjc8Mj48MD48ZGVmYXVs dD48ZGVmYXVsdD4KCltsY2QxX3BhcmFdCmxjZF91c2VkID0gMApsY2RfeCA9IDAKbGNkX3kgPSAw CmxjZF9kY2xrX2ZyZXEgPSAwCmxjZF9wd21fbm90X3VzZWQgPSAwCmxjZF9wd21fY2ggPSAxCmxj ZF9wd21fZnJlcSA9IDAKbGNkX3B3bV9wb2wgPSAwCmxjZF9tYXhfYnJpZ2h0ID0gMjQwCmxjZF9t aW5fYnJpZ2h0ID0gNjQKbGNkX2lmID0gMApsY2RfaGJwID0gMApsY2RfaHQgPSAwCmxjZF92YnAg PSAwCmxjZF92dCA9IDAKbGNkX3ZzcHcgPSAwCmxjZF9oc3B3ID0gMApsY2RfaHZfaWYgPSAwCmxj ZF9odl9zbW9kZSA9IDAKbGNkX2h2X3M4ODhfaWYgPSAwCmxjZF9odl9zeXV2X2lmID0gMApsY2Rf bHZkc19jaCA9IDAKbGNkX2x2ZHNfbW9kZSA9IDAKbGNkX2x2ZHNfYml0d2lkdGggPSAwCmxjZF9s dmRzX2lvX2Nyb3NzID0gMApsY2RfY3B1X2lmID0gMApsY2RfZnJtID0gMApsY2RfaW9fY2ZnMCA9 IDAKbGNkX2dhbW1hX2NvcnJlY3Rpb25fZW4gPSAwCmxjZF9nYW1tYV90YmxfMCA9IDB4MApsY2Rf Z2FtbWFfdGJsXzEgPSAweDEwMTAxCmxjZF9nYW1tYV90YmxfMjU1ID0gMHhmZmZmZmYKbGNkX2Js X2VuX3VzZWQgPSAwCmxjZF9ibF9lbiA9CmxjZF9wb3dlcl91c2VkID0gMApsY2RfcG93ZXIgPQps Y2RfcHdtX3VzZWQgPSAxCmxjZF9wd20gPSBwb3J0OlBJMDM8Mj48MD48ZGVmYXVsdD48ZGVmYXVs dD4KbGNkX2dwaW9fMCA9CmxjZF9ncGlvXzEgPQpsY2RfZ3Bpb18yID0KbGNkX2dwaW9fMyA9Cmxj ZGQwID0gcG9ydDpQSDAwPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxID0gcG9ydDpQSDAx PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQyID0gcG9ydDpQSDAyPDI+PDA+PGRlZmF1bHQ+ PGRlZmF1bHQ+CmxjZGQzID0gcG9ydDpQSDAzPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ0 ID0gcG9ydDpQSDA0PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ1ID0gcG9ydDpQSDA1PDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ2ID0gcG9ydDpQSDA2PDI+PDA+PGRlZmF1bHQ+PGRl ZmF1bHQ+CmxjZGQ3ID0gcG9ydDpQSDA3PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ4ID0g cG9ydDpQSDA4PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ5ID0gcG9ydDpQSDA5PDI+PDA+ PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxMCA9IHBvcnQ6UEgxMDwyPjwwPjxkZWZhdWx0PjxkZWZh dWx0PgpsY2RkMTEgPSBwb3J0OlBIMTE8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDEyID0g cG9ydDpQSDEyPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxMyA9IHBvcnQ6UEgxMzwyPjww PjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTQgPSBwb3J0OlBIMTQ8Mj48MD48ZGVmYXVsdD48ZGVm YXVsdD4KbGNkZDE1ID0gcG9ydDpQSDE1PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxNiA9 IHBvcnQ6UEgxNjwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTcgPSBwb3J0OlBIMTc8Mj48 MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDE4ID0gcG9ydDpQSDE4PDI+PDA+PGRlZmF1bHQ+PGRl ZmF1bHQ+CmxjZGQxOSA9IHBvcnQ6UEgxOTwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMjAg PSBwb3J0OlBIMjA8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDIxID0gcG9ydDpQSDIxPDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQyMiA9IHBvcnQ6UEgyMjwyPjwwPjxkZWZhdWx0Pjxk ZWZhdWx0PgpsY2RkMjMgPSBwb3J0OlBIMjM8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkY2xr ID0gcG9ydDpQSDI0PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGRlID0gcG9ydDpQSDI1PDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGhzeW5jID0gcG9ydDpQSDI2PDI+PDA+PGRlZmF1bHQ+ PGRlZmF1bHQ+CmxjZHZzeW5jID0gcG9ydDpQSDI3PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+Cgpb dHZfb3V0X2RhY19wYXJhXQpkYWNfdXNlZCA9IDEKZGFjMF9zcmMgPSA0CmRhYzFfc3JjID0gNQpk YWMyX3NyYyA9IDYKZGFjM19zcmMgPSAwCgpbaGRtaV9wYXJhXQpoZG1pX3VzZWQgPSAxCgpbY2Ft ZXJhX2xpc3RfcGFyYV0KY2FtZXJhX2xpc3RfcGFyYV91c2VkID0gMQpvdjc2NzAgPSAwCmdjMDMw OCA9IDEKZ3QyMDA1ID0gMQpoaTcwNCA9IDAKc3AwODM4ID0gMAptdDltMTEyID0gMAptdDltMTEz ID0gMApvdjI2NTUgPSAwCmhpMjUzID0gMApnYzAzMDcgPSAwCm10OWQxMTIgPSAwCm92NTY0MCA9 IDAKZ2MyMDE1ID0gMApvdjI2NDMgPSAwCmdjMDMyOSA9IDAKZ2MwMzA5ID0gMAp0dnA1MTUwID0g MApzNWs0ZWMgPSAwCm92NTY1MF9tdjkzMzUgPSAwCnNpdjEyMWQgPSAwCmdjMjAzNSA9IDAKCltj c2kwX3BhcmFdCmNzaV91c2VkID0gMApjc2lfZGV2X3F0eSA9IDIKY3NpX3N0YnlfbW9kZSA9IDAK Y3NpX21uYW1lID0gImdjMDMwOCIKY3NpX3R3aV9pZCA9IDEKY3NpX3R3aV9hZGRyID0gMHg0Mgpj c2lfaWYgPSAwCmNzaV92ZmxpcCA9IDAKY3NpX2hmbGlwID0gMApjc2lfaW92ZGQgPSAiYXhwMjBf cGxsIgpjc2lfYXZkZCA9ICIiCmNzaV9kdmRkID0gIiIKY3NpX3ZvbF9pb3ZkZCA9IDI4MDAKY3Np X3ZvbF9kdmRkID0KY3NpX3ZvbF9hdmRkID0KY3NpX2ZsYXNoX3BvbCA9IDAKY3NpX21uYW1lX2Ig PSAiZ3QyMDA1Igpjc2lfdHdpX2lkX2IgPSAxCmNzaV90d2lfYWRkcl9iID0gMHg3OApjc2lfaWZf YiA9IDAKY3NpX3ZmbGlwX2IgPSAwCmNzaV9oZmxpcF9iID0gMApjc2lfaW92ZGRfYiA9ICJheHAy MF9wbGwiCmNzaV9hdmRkX2IgPSAiIgpjc2lfZHZkZF9iID0gIiIKY3NpX3ZvbF9pb3ZkZF9iID0g MjgwMApjc2lfdm9sX2F2ZGRfYiA9CmNzaV92b2xfZHZkZF9iID0KY3NpX2ZsYXNoX3BvbF9iID0g MApjc2lfcGNrID0gcG9ydDpQRTAwPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9j ayA9IHBvcnQ6UEUwMTwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfaHN5bmMgPSBw b3J0OlBFMDI8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX3ZzeW5jID0gcG9ydDpQ RTAzPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9kMCA9IHBvcnQ6UEUwNDwzPjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfZDEgPSBwb3J0OlBFMDU8Mz48ZGVmYXVsdD48 ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2QyID0gcG9ydDpQRTA2PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+CmNzaV9kMyA9IHBvcnQ6UEUwNzwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0 Pgpjc2lfZDQgPSBwb3J0OlBFMDg8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2Q1 ID0gcG9ydDpQRTA5PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9kNiA9IHBvcnQ6 UEUxMDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfZDcgPSBwb3J0OlBFMTE8Mz48 ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX3Jlc2V0ID0gcG9ydDpQSDE0PDE+PGRlZmF1 bHQ+PGRlZmF1bHQ+PDA+CmNzaV9wb3dlcl9lbiA9IHBvcnQ6UEgxNzwxPjxkZWZhdWx0PjxkZWZh dWx0PjwwPgpjc2lfc3RieSA9IHBvcnQ6UEgxOTwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgpjc2lf Zmxhc2ggPQpjc2lfYWZfZW4gPQpjc2lfcmVzZXRfYiA9IHBvcnQ6UEgxNDwxPjxkZWZhdWx0Pjxk ZWZhdWx0PjwwPgpjc2lfcG93ZXJfZW5fYiA9IHBvcnQ6UEgxNzwxPjxkZWZhdWx0PjxkZWZhdWx0 PjwwPgpjc2lfc3RieV9iID0gcG9ydDpQSDE4PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDA+CmNzaV9m bGFzaF9iID0KY3NpX2FmX2VuX2IgPQoKW2NzaTFfcGFyYV0KY3NpX3VzZWQgPSAwCmNzaV9kZXZf cXR5ID0gMQpjc2lfc3RieV9tb2RlID0gMApjc2lfbW5hbWUgPSAiZ2MwMzA4Igpjc2lfaWYgPSAw CmNzaV9pb3ZkZCA9ICJheHAyMF9wbGwiCmNzaV9hdmRkID0gIiIKY3NpX2R2ZGQgPSAiIgpjc2lf dm9sX2lvdmRkID0gMjgwMApjc2lfdm9sX2R2ZGQgPQpjc2lfdm9sX2F2ZGQgPQpjc2lfdmZsaXAg PSAwCmNzaV9oZmxpcCA9IDAKY3NpX2ZsYXNoX3BvbCA9IDAKY3NpX2ZhY2luZyA9IDEKY3NpX3R3 aV9pZCA9IDEKY3NpX3R3aV9hZGRyID0gMHg0Mgpjc2lfcGNrID0gcG9ydDpQRzAwPDM+PGRlZmF1 bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9jayA9IHBvcnQ6UEcwMTwzPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0Pgpjc2lfaHN5bmMgPSBwb3J0OlBHMDI8Mz48ZGVmYXVsdD48ZGVmYXVsdD48 ZGVmYXVsdD4KY3NpX3ZzeW5jID0gcG9ydDpQRzAzPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1 bHQ+CmNzaV9kMCA9IHBvcnQ6UEcwNDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lf ZDEgPSBwb3J0OlBHMDU8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2QyID0gcG9y dDpQRzA2PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9kMyA9IHBvcnQ6UEcwNzwz PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfZDQgPSBwb3J0OlBHMDg8Mz48ZGVmYXVs dD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2Q1ID0gcG9ydDpQRzA5PDM+PGRlZmF1bHQ+PGRlZmF1 bHQ+PGRlZmF1bHQ+CmNzaV9kNiA9IHBvcnQ6UEcxMDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0Pgpjc2lfZDcgPSBwb3J0OlBHMTE8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3Np X3Jlc2V0ID0gcG9ydDpQSDEzPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDA+CmNzaV9wb3dlcl9lbiA9 IHBvcnQ6UEgxNjwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgpjc2lfc3RieSA9IHBvcnQ6UEgxOTwx PjxkZWZhdWx0PjxkZWZhdWx0PjwwPgoKW3R2b3V0X3BhcmFdCnR2b3V0X3VzZWQgPSAxCnR2b3V0 X2NoYW5uZWxfbnVtID0gMQoKW3R2aW5fcGFyYV0KdHZpbl91c2VkID0gMAp0dmluX2NoYW5uZWxf bnVtID0gNAoKW3B3bTBfcGFyYV0KcHdtX3VzZWQgPSAxCnB3bV9wZXJpb2QgPSAyMApwd21fZHV0 eV9wZXJjZW50ID0gNTAKCltzYXRhX3BhcmFdCnNhdGFfdXNlZCA9IDEKc2F0YV9wb3dlcl9lbiA9 IHBvcnQ6UEgxMjwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgoKW21tYzBfcGFyYV0Kc2RjX3VzZWQg PSAxCnNkY19kZXRtb2RlID0gMQpzZGNfYnVzd2lkdGggPSA0CnNkY19jbGsgPSBwb3J0OlBGMDI8 Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2NtZCA9IHBvcnQ6UEYwMzwyPjwxPjwyPjxkZWZhdWx0Pgpz ZGNfZDAgPSBwb3J0OlBGMDE8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2QxID0gcG9ydDpQRjAwPDI+ PDE+PDI+PGRlZmF1bHQ+CnNkY19kMiA9IHBvcnQ6UEYwNTwyPjwxPjwyPjxkZWZhdWx0PgpzZGNf ZDMgPSBwb3J0OlBGMDQ8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2RldCA9IHBvcnQ6UEgwMTwwPjwx PjxkZWZhdWx0PjxkZWZhdWx0PgpzZGNfdXNlX3dwID0gMApzZGNfd3AgPQpzZGNfaXNpbyA9IDAK c2RjX3JlZ3VsYXRvciA9ICJub25lIgoKW21tYzFfcGFyYV0Kc2RjX3VzZWQgPSAwCnNkY19kZXRt b2RlID0gNApzZGNfYnVzd2lkdGggPSA0CnNkY19jbGsgPSBwb3J0OlBHMDA8Mj48MT48Mj48ZGVm YXVsdD4Kc2RjX2NtZCA9IHBvcnQ6UEcwMTwyPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDAgPSBwb3J0 OlBHMDI8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2QxID0gcG9ydDpQRzAzPDI+PDE+PDI+PGRlZmF1 bHQ+CnNkY19kMiA9IHBvcnQ6UEcwNDwyPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDMgPSBwb3J0OlBH MDU8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2RldCA9CnNkY191c2Vfd3AgPSAwCnNkY193cCA9CnNk Y19pc2lvID0gMApzZGNfcmVndWxhdG9yID0gIm5vbmUiCgpbbW1jMl9wYXJhXQpzZGNfdXNlZCA9 IDAKc2RjX2RldG1vZGUgPSAzCnNkY19idXN3aWR0aCA9IDQKc2RjX2NtZCA9IHBvcnQ6UEMwNjwz PjwxPjwyPjxkZWZhdWx0PgpzZGNfY2xrID0gcG9ydDpQQzA3PDM+PDE+PDI+PGRlZmF1bHQ+CnNk Y19kMCA9IHBvcnQ6UEMwODwzPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDEgPSBwb3J0OlBDMDk8Mz48 MT48Mj48ZGVmYXVsdD4Kc2RjX2QyID0gcG9ydDpQQzEwPDM+PDE+PDI+PGRlZmF1bHQ+CnNkY19k MyA9IHBvcnQ6UEMxMTwzPjwxPjwyPjxkZWZhdWx0PgpzZGNfZGV0ID0Kc2RjX3VzZV93cCA9IDAK c2RjX3dwID0Kc2RjX2lzaW8gPSAwCnNkY19yZWd1bGF0b3IgPSAibm9uZSIKClttbWMzX3BhcmFd CnNkY191c2VkID0gMQpzZGNfZGV0bW9kZSA9IDQKc2RjX2J1c3dpZHRoID0gNApzZGNfY21kID0g cG9ydDpQSTA0PDI+PDE+PDI+PGRlZmF1bHQ+CnNkY19jbGsgPSBwb3J0OlBJMDU8Mj48MT48Mj48 ZGVmYXVsdD4Kc2RjX2QwID0gcG9ydDpQSTA2PDI+PDE+PDI+PGRlZmF1bHQ+CnNkY19kMSA9IHBv cnQ6UEkwNzwyPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDIgPSBwb3J0OlBJMDg8Mj48MT48Mj48ZGVm YXVsdD4Kc2RjX2QzID0gcG9ydDpQSTA5PDI+PDE+PDI+PGRlZmF1bHQ+CnNkY19kZXQgPQpzZGNf dXNlX3dwID0gMApzZGNfd3AgPQpzZGNfaXNpbyA9IDEKc2RjX3JlZ3VsYXRvciA9ICJub25lIgoK W21zX3BhcmFdCm1zX3VzZWQgPSAwCm1zX2JzID0gcG9ydDpQSDA2PDU+PGRlZmF1bHQ+PGRlZmF1 bHQ+PGRlZmF1bHQ+Cm1zX2NsayA9IHBvcnQ6UEgwNzw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0Pgptc19kMCA9IHBvcnQ6UEgwODw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19k MSA9IHBvcnQ6UEgwOTw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19kMiA9IHBvcnQ6 UEgxMDw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19kMyA9IHBvcnQ6UEgxMTw1Pjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19kZXQgPQoKW3NtY19wYXJhXQpzbWNfdXNlZCA9 IDAKc21jX3JzdCA9IHBvcnQ6UEgxMzw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzbWNf dnBwZW4gPSBwb3J0OlBIMTQ8NT48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc21jX3ZwcHAg PSBwb3J0OlBIMTU8NT48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc21jX2RldCA9IHBvcnQ6 UEgxNjw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzbWNfdmNjZW4gPSBwb3J0OlBIMTc8 NT48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc21jX3NjayA9IHBvcnQ6UEgxODw1PjxkZWZh dWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzbWNfc2RhID0gcG9ydDpQSDE5PDU+PGRlZmF1bHQ+PGRl ZmF1bHQ+PGRlZmF1bHQ+CgpbcHMyXzBfcGFyYV0KcHMyX3VzZWQgPSAwCnBzMl9zY2wgPSBwb3J0 OlBJMjA8Mj48MT48ZGVmYXVsdD48ZGVmYXVsdD4KcHMyX3NkYSA9IHBvcnQ6UEkyMTwyPjwxPjxk ZWZhdWx0PjxkZWZhdWx0PgoKW3BzMl8xX3BhcmFdCnBzMl91c2VkID0gMApwczJfc2NsID0gcG9y dDpQSTE0PDM+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnBzMl9zZGEgPSBwb3J0OlBJMTU8Mz48MT48 ZGVmYXVsdD48ZGVmYXVsdD4KCltjYW5fcGFyYV0KY2FuX3VzZWQgPSAwCmNhbl90eCA9IHBvcnQ6 UEExNjwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpjYW5fcnggPSBwb3J0OlBBMTc8Mz48 ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KCltrZXlwYWRfcGFyYV0Ka3BfdXNlZCA9IDAKa3Bf aW5fc2l6ZSA9IDgKa3Bfb3V0X3NpemUgPSA4CmtwX2luMCA9IHBvcnQ6UEgwODw0PjwxPjxkZWZh dWx0PjxkZWZhdWx0PgprcF9pbjEgPSBwb3J0OlBIMDk8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4K a3BfaW4yID0gcG9ydDpQSDEwPDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CmtwX2luMyA9IHBvcnQ6 UEgxMTw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9pbjQgPSBwb3J0OlBIMTQ8ND48MT48ZGVm YXVsdD48ZGVmYXVsdD4Ka3BfaW41ID0gcG9ydDpQSDE1PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+ CmtwX2luNiA9IHBvcnQ6UEgxNjw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9pbjcgPSBwb3J0 OlBIMTc8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4Ka3Bfb3V0MCA9IHBvcnQ6UEgxODw0PjwxPjxk ZWZhdWx0PjxkZWZhdWx0PgprcF9vdXQxID0gcG9ydDpQSDE5PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1 bHQ+CmtwX291dDIgPSBwb3J0OlBIMjI8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4Ka3Bfb3V0MyA9 IHBvcnQ6UEgyMzw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9vdXQ0ID0gcG9ydDpQSDI0PDQ+ PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CmtwX291dDUgPSBwb3J0OlBIMjU8ND48MT48ZGVmYXVsdD48 ZGVmYXVsdD4Ka3Bfb3V0NiA9IHBvcnQ6UEgyNjw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9v dXQ3ID0gcG9ydDpQSDI3PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CgpbdXNiYzBdCnVzYl91c2Vk ID0gMQp1c2JfcG9ydF90eXBlID0gMgp1c2JfZGV0ZWN0X3R5cGUgPSAxCnVzYl9pZF9ncGlvID0g cG9ydDpQSDE5PDA+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVzYl9kZXRfdmJ1c19ncGlvID0gcG9y dDpQSDIyPDE+PDA+PGRlZmF1bHQ+PDA+CnVzYl9kcnZfdmJ1c19ncGlvID0gcG9ydDpQSDE3PDE+ PDA+PGRlZmF1bHQ+PDA+CnVzYl9yZXN0cmljdF9ncGlvID0gcG9ydDpQSDAwPDE+PDA+PGRlZmF1 bHQ+PDA+CnVzYl9ob3N0X2luaXRfc3RhdGUgPSAxCnVzYl9yZXN0cmljX2ZsYWcgPSAwCnVzYl9y ZXN0cmljX3ZvbHRhZ2UgPSAzNTUwMDAwCnVzYl9yZXN0cmljX2NhcGFjaXR5ID0gNQoKW3VzYmMx XQp1c2JfdXNlZCA9IDEKdXNiX3BvcnRfdHlwZSA9IDEKdXNiX2RldGVjdF90eXBlID0gMAp1c2Jf ZHJ2X3ZidXNfZ3BpbyA9IHBvcnQ6UEgwNjwxPjwwPjxkZWZhdWx0PjwwPgp1c2JfcmVzdHJpY3Rf Z3BpbyA9CnVzYl9ob3N0X2luaXRfc3RhdGUgPSAxCnVzYl9yZXN0cmljX2ZsYWcgPSAwCgpbdXNi YzJdCnVzYl91c2VkID0gMQp1c2JfcG9ydF90eXBlID0gMQp1c2JfZGV0ZWN0X3R5cGUgPSAwCnVz Yl9kcnZfdmJ1c19ncGlvID0gcG9ydDpQSDAzPDE+PDA+PGRlZmF1bHQ+PDA+CnVzYl9yZXN0cmlj dF9ncGlvID0KdXNiX2hvc3RfaW5pdF9zdGF0ZSA9IDEKdXNiX3Jlc3RyaWNfZmxhZyA9IDAKClt1 c2JfZmVhdHVyZV0KdmVuZG9yX2lkID0gNjM1MwptYXNzX3N0b3JhZ2VfaWQgPSAxCmFkYl9pZCA9 IDIKbWFudWZhY3R1cmVyX25hbWUgPSAiVVNCIERldmVsb3BlciIKcHJvZHVjdF9uYW1lID0gIkFu ZHJvaWQiCnNlcmlhbF9udW1iZXIgPSAiMjAwODA0MTEiCgpbbXNjX2ZlYXR1cmVdCnZlbmRvcl9u YW1lID0gIlVTQiAyLjAiCnByb2R1Y3RfbmFtZSA9ICJVU0IgRmxhc2ggRHJpdmVyIgpyZWxlYXNl ID0gMTAwCmx1bnMgPSAzCgpbZ3NlbnNvcl9wYXJhXQpnc2Vuc29yX3VzZWQgPSAwCmdzZW5zb3Jf dHdpX2lkID0gMQpnc2Vuc29yX2ludDEgPQpnc2Vuc29yX2ludDIgPQoKW2dzZW5zb3JfbGlzdF9w YXJhXQpnc2Vuc29yX2RldF91c2VkID0gMQpibWEyNTAgPSAxCm1tYTg0NTIgPSAxCm1tYTc2NjAg PSAxCm1tYTg2NXggPSAxCmFmYTc1MCA9IDEKbGlzM2RlX2FjYyA9IDEKbGlzM2RoX2FjYyA9IDEK a3h0aWsgPSAxCmRtYXJkMTAgPSAwCmRtYXJkMDYgPSAxCm14YzYyMnggPSAxCmZ4b3M4NzAwID0g MQpsc20zMDNkID0gMQoKW2dwc19wYXJhXQpncHNfdXNlZCA9IDAKZ3BzX3NwaV9pZCA9IDIKZ3Bz X3NwaV9jc19udW0gPSAwCmdwc19scmFkYyA9IDEKZ3BzX2NsayA9IHBvcnQ6UEkwMDwyPjxkZWZh dWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpncHNfc2lnbiA9IHBvcnQ6UEkwMTwyPjxkZWZhdWx0Pjxk ZWZhdWx0PjxkZWZhdWx0PgpncHNfbWFnID0gcG9ydDpQSTAyPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+Cmdwc192Y2NfZW4gPSBwb3J0OlBDMjI8MT48ZGVmYXVsdD48ZGVmYXVsdD48MD4K Z3BzX29zY19lbiA9IHBvcnQ6UEkxNDwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgpncHNfcnhfZW4g PSBwb3J0OlBJMTU8MT48ZGVmYXVsdD48ZGVmYXVsdD48MD4KClt3aWZpX3BhcmFdCndpZmlfdXNl ZCA9IDEKd2lmaV9zZGNfaWQgPSAzCndpZmlfdXNiY19pZCA9IDIKd2lmaV91c2JjX3R5cGUgPSAx CndpZmlfbW9kX3NlbCA9IDcKd2lmaV9wb3dlciA9ICIiCmFwNnh4eF93bF9yZWdvbiA9IHBvcnQ6 UEgwOTwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgphcDZ4eHhfYnRfcmVnb24gPSBwb3J0OlBIMTg8 MT48ZGVmYXVsdD48ZGVmYXVsdD48MD4KYXA2eHh4X2J0X3dha2UgPSBwb3J0OlBIMjQ8MT48ZGVm YXVsdD48ZGVmYXVsdD48MD4KYXA2eHh4X2J0X2hvc3Rfd2FrZSA9IHBvcnQ6UEgyNTwwPjxkZWZh dWx0PjxkZWZhdWx0PjwwPgphcDZ4eHhfbHBvID0gcG9ydDpQSTEyPDQ+PDE+PGRlZmF1bHQ+PDE+ CgpbdXNiX3dpZmlfcGFyYV0KdXNiX3dpZmlfdXNlZCA9IDAKdXNiX3dpZmlfdXNiY19udW0gPSAy CgpbM2dfcGFyYV0KM2dfdXNlZCA9IDAKM2dfdXNiY19udW0gPSAyCjNnX3VhcnRfbnVtID0gMAoz Z19wd3IgPQozZ193YWtldXAgPQozZ19pbnQgPQoKW2d5X3BhcmFdCmd5X3VzZWQgPSAwCmd5X3R3 aV9pZCA9IDEKZ3lfdHdpX2FkZHIgPSAwCmd5X2ludDEgPSBwb3J0OlBIMTg8Nj48MT48ZGVmYXVs dD48ZGVmYXVsdD4KZ3lfaW50MiA9IHBvcnQ6UEgxOTw2PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoK W2xzX3BhcmFdCmxzX3VzZWQgPSAwCmxzX3R3aV9pZCA9IDEKbHNfdHdpX2FkZHIgPSAwCmxzX2lu dCA9IHBvcnQ6UEgyMDw2PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW2NvbXBhc3NfcGFyYV0KY29t cGFzc191c2VkID0gMApjb21wYXNzX3R3aV9pZCA9IDEKY29tcGFzc190d2lfYWRkciA9IDAKY29t cGFzc19pbnQgPSBwb3J0OlBJMTM8Nj48MT48ZGVmYXVsdD48ZGVmYXVsdD4KCltidF9wYXJhXQpi dF91c2VkID0gMQpidF91YXJ0X2lkID0gMgoKW2kyc19wYXJhXQppMnNfdXNlZCA9IDEKaTJzX2No YW5uZWwgPSAyCmkyc19tY2xrID0gcG9ydDpQQjA1PDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+Cmky c19iY2xrID0gcG9ydDpQQjA2PDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+Cmkyc19scmNsayA9IHBv cnQ6UEIwNzwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgppMnNfZG91dDAgPSBwb3J0OlBCMDg8Mj48 MT48ZGVmYXVsdD48ZGVmYXVsdD4KaTJzX2RvdXQxID0KaTJzX2RvdXQyID0KaTJzX2RvdXQzID0K aTJzX2RpbiA9IHBvcnQ6UEIxMjwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3NwZGlmX3BhcmFd CnNwZGlmX3VzZWQgPSAxCnNwZGlmX21jbGsgPQpzcGRpZl9kb3V0ID0gcG9ydDpQQjEzPDQ+PDE+ PGRlZmF1bHQ+PGRlZmF1bHQ+CnNwZGlmX2RpbiA9CgpbYXVkaW9fcGFyYV0KYXVkaW9fdXNlZCA9 IDEKYXVkaW9fcGFfY3RybCA9IHBvcnQ6UEgxNTwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgoKW3N3 aXRjaF9wYXJhXQpzd2l0Y2hfdXNlZCA9IDEKCltpcl9wYXJhXQppcl91c2VkID0gMQppcjBfcngg PSBwb3J0OlBCMDQ8Mj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KCltwbXVfcGFyYV0KcG11 X3VzZWQgPSAxCnBtdV90d2lfYWRkciA9IDUyCnBtdV90d2lfaWQgPSAwCnBtdV9pcnFfaWQgPSAz MgpwbXVfYmF0dGVyeV9yZGMgPSAxMjAKcG11X2JhdHRlcnlfY2FwID0gMjEwMApwbXVfaW5pdF9j aGdjdXIgPSAzMDAKcG11X2Vhcmx5c3VzcGVuZF9jaGdjdXIgPSA2MDAKcG11X3N1c3BlbmRfY2hn Y3VyID0gMTAwMApwbXVfcmVzdW1lX2NoZ2N1ciA9IDMwMApwbXVfc2h1dGRvd25fY2hnY3VyID0g MTAwMApwbXVfaW5pdF9jaGd2b2wgPSA0MjAwCnBtdV9pbml0X2NoZ2VuZF9yYXRlID0gMTUKcG11 X2luaXRfY2hnX2VuYWJsZWQgPSAxCnBtdV9pbml0X2FkY19mcmVxID0gMTAwCnBtdV9pbml0X2Fk Y19mcmVxYyA9IDEwMApwbXVfaW5pdF9jaGdfcHJldGltZSA9IDUwCnBtdV9pbml0X2NoZ19jc3R0 aW1lID0gNzIwCnBtdV9iYXRfcGFyYTEgPSAwCnBtdV9iYXRfcGFyYTIgPSAwCnBtdV9iYXRfcGFy YTMgPSAwCnBtdV9iYXRfcGFyYTQgPSAwCnBtdV9iYXRfcGFyYTUgPSA1CnBtdV9iYXRfcGFyYTYg PSAxMQpwbXVfYmF0X3BhcmE3ID0gMTMKcG11X2JhdF9wYXJhOCA9IDE1CnBtdV9iYXRfcGFyYTkg PSAxOQpwbXVfYmF0X3BhcmExMCA9IDMyCnBtdV9iYXRfcGFyYTExID0gNTAKcG11X2JhdF9wYXJh MTIgPSA1OApwbXVfYmF0X3BhcmExMyA9IDcxCnBtdV9iYXRfcGFyYTE0ID0gODEKcG11X2JhdF9w YXJhMTUgPSA4OQpwbXVfYmF0X3BhcmExNiA9IDEwMApwbXVfdXNidm9sX2xpbWl0ID0gMQpwbXVf dXNiY3VyX2xpbWl0ID0gMApwbXVfdXNidm9sID0gNDAwMApwbXVfdXNiY3VyID0gMApwbXVfdXNi dm9sX3BjID0gNDIwMApwbXVfdXNiY3VyX3BjID0gMApwbXVfcHdyb2ZmX3ZvbCA9IDMzMDAKcG11 X3B3cm9uX3ZvbCA9IDI5MDAKcG11X3Bla29mZl90aW1lID0gNjAwMApwbXVfcGVrb2ZmX2VuID0g MQpwbXVfcGVrbG9uZ190aW1lID0gMTUwMApwbXVfcGVrb25fdGltZSA9IDEwMDAKcG11X3B3cm9r X3RpbWUgPSA2NApwbXVfcHdybm9lX3RpbWUgPSAyMDAwCnBtdV9pbnRvdHBfZW4gPSAxCnBtdV91 c2VkMiA9IDAKcG11X2FkcGRldCA9IHBvcnQ6UEgwMjwwPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0PgpwbXVfaW5pdF9jaGdjdXIyID0gNDAwCnBtdV9lYXJseXN1c3BlbmRfY2hnY3VyMiA9IDYw MApwbXVfc3VzcGVuZF9jaGdjdXIyID0gMTIwMApwbXVfcmVzdW1lX2NoZ2N1cjIgPSA0MDAKcG11 X3NodXRkb3duX2NoZ2N1cjIgPSAxMjAwCnBtdV9zdXNwZW5kcHdyb2ZmX3ZvbCA9IDM1MDAKcG11 X2JhdGRldGVuID0gMQpwbXVfYmFja3VwZW4gPSAxCgpbcmVjb3Zlcnlfa2V5XQprZXlfbWluID0g NAprZXlfbWF4ID0gNDAKCltkdmZzX3RhYmxlXQptYXhfZnJlcSA9IDkxMjAwMDAwMAptaW5fZnJl cSA9IDcyMDAwMDAwMApub3JtYWxfZnJlcSA9IDcyMDAwMDAwMApMVl9jb3VudCA9IDcKTFYxX2Zy ZXEgPSAxMDA4MDAwMDAwCkxWMV92b2x0ID0gMTQ1MApMVjJfZnJlcSA9IDkxMjAwMDAwMApMVjJf dm9sdCA9IDE0MjUKTFYzX2ZyZXEgPSA4NjQwMDAwMDAKTFYzX3ZvbHQgPSAxMzUwCkxWNF9mcmVx ID0gNzIwMDAwMDAwCkxWNF92b2x0ID0gMTI1MApMVjVfZnJlcSA9IDUyODAwMDAwMApMVjVfdm9s dCA9IDExNTAKTFY2X2ZyZXEgPSAzMTIwMDAwMDAKTFY2X3ZvbHQgPSAxMTAwCkxWN19mcmVxID0g MTQ0MDAwMDAwCkxWN192b2x0ID0gMTA1MAoKW2Jvb3RfZGlzcF0Kb3V0cHV0X3R5cGUgPSAzCm91 dHB1dF9tb2RlID0gNAphdXRvX2hwZCA9IDEKCg== ------=_Part_20226_971071809.1407352669442 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 ------=_Part_20226_971071809.1407352669442-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 19:17:56 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 19:17: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 1XF6if-0000lg-7i; Wed, 06 Aug 2014 19:17:53 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF6id-0000lb-Qd for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 19:17:52 +0000 Received: from [85.158.143.35:25059] by server-1.bemta-4.messagelabs.com id 38/79-05872-F5F72E35; Wed, 06 Aug 2014 19:17:51 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-5.tower-21.messagelabs.com!1407352669!13862504!1 X-Originating-IP: [80.12.242.128] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3215 invoked from network); 6 Aug 2014 19:17:50 -0000 Received: from smtp06.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.128) by server-5.tower-21.messagelabs.com with SMTP; 6 Aug 2014 19:17:50 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d12 with ME id bXHp1o00B1EBZFu03XHpXG; Wed, 06 Aug 2014 21:17:49 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 21:17:49 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 21:17:49 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <244724588.20228.1407352669454.JavaMail.www@wwinf1c13> In-Reply-To: <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_20226_971071809.1407352669442" X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org ------=_Part_20226_971071809.1407352669442 Content-Type: multipart/alternative; boundary="----=_Part_20227_2075660310.1407352669443" ------=_Part_20227_2075660310.1407352669443 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable but on cubietruck image for ubuntu, debian and co, they use a uEnv.txt and = script.bin file=C2=A0 > Message du 06/08/14 20:14 > De : "Gilles DALMAS"=20 > A : "Thomas Leonard"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > > i have installed lxde because i don't know if there was a graphic environ= ment. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 ------=_Part_20227_2075660310.1407352669443 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

but on cubietruck image for ubuntu, debian and co, they use a uEnv.txt a= nd script.bin file=C2=A0




> Message du 06/08/14 20:14
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "Thomas Leonard" <talex5@gma= il.com>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
>

> i have installed lxde because i don't know if there was a graphic e= nvironment.




> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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.xe= nproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mira= geos-devel

------=_Part_20227_2075660310.1407352669443-- ------=_Part_20226_971071809.1407352669442 Content-Type: application/octet-stream; name=script.fex content-transfer-encoding: base64 Content-Disposition: attachment; size=33184; filename=script.fex W3Byb2R1Y3RdCnZlcnNpb24gPSAiMTAwIgptYWNoaW5lID0gImN1YmlldHJ1Y2siCgpbcGxhdGZv cm1dCmVyYXNlZmxhZyA9IDAKClt0YXJnZXRdCmJvb3RfY2xvY2sgPSA5MTIKZGNkYzJfdm9sID0g MTQ1MApkY2RjM192b2wgPSAxMzAwCmxkbzJfdm9sID0gMzAwMApsZG8zX3ZvbCA9IDI4MDAKbGRv NF92b2wgPSAyODAwCnN0b3JhZ2VfdHlwZSA9IDAKCltjbG9ja10KcGxsMyA9IDI5NwpwbGw0ID0g MzAwCnBsbDYgPSA2MDAKcGxsNyA9IDI5NwpwbGw4ID0gMzM2CgpbY2FyZF9ib290XQpsb2dpY2Fs X3N0YXJ0ID0gNDA5NjAKc3ByaXRlX2dwaW8wID0KCltjYXJkMF9ib290X3BhcmFdCmNhcmRfY3Ry bCA9IDAKY2FyZF9oaWdoX3NwZWVkID0gMQpjYXJkX2xpbmUgPSA0CnNkY19kMSA9IHBvcnQ6UEYw MDwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgpzZGNfZDAgPSBwb3J0OlBGMDE8Mj48MT48ZGVmYXVs dD48ZGVmYXVsdD4Kc2RjX2NsayA9IHBvcnQ6UEYwMjwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgpz ZGNfY21kID0gcG9ydDpQRjAzPDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnNkY19kMyA9IHBvcnQ6 UEYwNDwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgpzZGNfZDIgPSBwb3J0OlBGMDU8Mj48MT48ZGVm YXVsdD48ZGVmYXVsdD4KCltjYXJkMl9ib290X3BhcmFdCmNhcmRfY3RybCA9IDIKY2FyZF9oaWdo X3NwZWVkID0gMQpjYXJkX2xpbmUgPSA0CnNkY19jbWQgPSBwb3J0OlBDMDY8Mz48MT48ZGVmYXVs dD48ZGVmYXVsdD4Kc2RjX2NsayA9IHBvcnQ6UEMwNzwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgpz ZGNfZDAgPSBwb3J0OlBDMDg8Mz48MT48ZGVmYXVsdD48ZGVmYXVsdD4Kc2RjX2QxID0gcG9ydDpQ QzA5PDM+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnNkY19kMiA9IHBvcnQ6UEMxMDwzPjwxPjxkZWZh dWx0PjxkZWZhdWx0PgpzZGNfZDMgPSBwb3J0OlBDMTE8Mz48MT48ZGVmYXVsdD48ZGVmYXVsdD4K Clt0d2lfcGFyYV0KdHdpX3BvcnQgPSAwCnR3aV9zY2wgPSBwb3J0OlBCMDA8Mj48ZGVmYXVsdD48 ZGVmYXVsdD48ZGVmYXVsdD4KdHdpX3NkYSA9IHBvcnQ6UEIwMTwyPjxkZWZhdWx0PjxkZWZhdWx0 PjxkZWZhdWx0PgoKW3VhcnRfcGFyYV0KdWFydF9kZWJ1Z19wb3J0ID0gMAp1YXJ0X2RlYnVnX3R4 ID0gcG9ydDpQQjIyPDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfZGVidWdfcnggPSBwb3J0 OlBCMjM8Mj48MT48ZGVmYXVsdD48ZGVmYXVsdD4KClt1YXJ0X2ZvcmNlX2RlYnVnXQp1YXJ0X2Rl YnVnX3BvcnQgPSAwCnVhcnRfZGVidWdfdHggPSBwb3J0OlBGMDI8ND48MT48ZGVmYXVsdD48ZGVm YXVsdD4KdWFydF9kZWJ1Z19yeCA9IHBvcnQ6UEYwNDw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoK W2p0YWdfcGFyYV0KanRhZ19lbmFibGUgPSAwCmp0YWdfbXMgPSBwb3J0OlBCMTQ8Mz48ZGVmYXVs dD48ZGVmYXVsdD48ZGVmYXVsdD4KanRhZ19jayA9IHBvcnQ6UEIxNTwzPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0PgpqdGFnX2RvID0gcG9ydDpQQjE2PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRl ZmF1bHQ+Cmp0YWdfZGkgPSBwb3J0OlBCMTc8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4K CltwbV9wYXJhXQpzdGFuZGJ5X21vZGUgPSAwCgpbZHJhbV9wYXJhXQpkcmFtX2Jhc2VhZGRyID0g MHg0MDAwMDAwMApkcmFtX2NsayA9IDQzMgpkcmFtX3R5cGUgPSAzCmRyYW1fcmFua19udW0gPSAt MQpkcmFtX2NoaXBfZGVuc2l0eSA9IC0xCmRyYW1faW9fd2lkdGggPSAtMQpkcmFtX2J1c193aWR0 aCA9IC0xCmRyYW1fY2FzID0gOQpkcmFtX3pxID0gMHg3ZgpkcmFtX29kdF9lbiA9IDAKZHJhbV9z aXplID0gLTEKZHJhbV90cHIwID0gMHg0MmQ4OTliNwpkcmFtX3RwcjEgPSAweGEwOTAKZHJhbV90 cHIyID0gMHgyMmEwMApkcmFtX3RwcjMgPSAweDAKZHJhbV90cHI0ID0gMHgxCmRyYW1fdHByNSA9 IDB4MApkcmFtX2VtcjEgPSAweDQKZHJhbV9lbXIyID0gMHgxMApkcmFtX2VtcjMgPSAweDAKCltt YWxpX3BhcmFdCm1hbGlfdXNlZCA9IDEKbWFsaV9jbGtkaXYgPSAxCgpbZ21hY19wYXJhXQpnbWFj X3VzZWQgPSAxCmdtYWNfcnhkMyA9IHBvcnQ6UEEwMDw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0Pgpn bWFjX3J4ZDIgPSBwb3J0OlBBMDE8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY19yeGQxID0g cG9ydDpQQTAyPDU+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+CmdtYWNfcnhkMCA9IHBvcnQ6UEEwMzw1 PjxkZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3R4ZDMgPSBwb3J0OlBBMDQ8NT48ZGVmYXVsdD48 Mz48ZGVmYXVsdD4KZ21hY190eGQyID0gcG9ydDpQQTA1PDU+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+ CmdtYWNfdHhkMSA9IHBvcnQ6UEEwNjw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3R4ZDAg PSBwb3J0OlBBMDc8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY19yeGNsayA9IHBvcnQ6UEEw ODw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3J4ZXJyID0gcG9ydDpQQTA5PDA+PGRlZmF1 bHQ+PDM+PGRlZmF1bHQ+CmdtYWNfcnhjdGwgPSBwb3J0OlBBMTA8NT48ZGVmYXVsdD48Mz48ZGVm YXVsdD4KZ21hY19tZGMgPSBwb3J0OlBBMTE8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY19t ZGlvID0gcG9ydDpQQTEyPDU+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+CmdtYWNfdHhjdGwgPSBwb3J0 OlBBMTM8NT48ZGVmYXVsdD48Mz48ZGVmYXVsdD4KZ21hY190eGNsayA9IHBvcnQ6UEExNDwwPjxk ZWZhdWx0PjwzPjxkZWZhdWx0PgpnbWFjX3R4Y2sgPSBwb3J0OlBBMTU8NT48ZGVmYXVsdD48Mz48 ZGVmYXVsdD4KZ21hY19jbGtpbiA9IHBvcnQ6UEExNjw1PjxkZWZhdWx0PjwzPjxkZWZhdWx0Pgpn bWFjX3R4ZXJyID0gcG9ydDpQQTE3PDA+PGRlZmF1bHQ+PDM+PGRlZmF1bHQ+CgpbdHdpMF9wYXJh XQp0d2kwX3VzZWQgPSAxCnR3aTBfc2NsID0gcG9ydDpQQjAwPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+CnR3aTBfc2RhID0gcG9ydDpQQjAxPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1 bHQ+CgpbdHdpMV9wYXJhXQp0d2kxX3VzZWQgPSAwCnR3aTFfc2NsID0gcG9ydDpQQjE4PDI+PGRl ZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CnR3aTFfc2RhID0gcG9ydDpQQjE5PDI+PGRlZmF1bHQ+ PGRlZmF1bHQ+PGRlZmF1bHQ+CgpbdHdpMl9wYXJhXQp0d2kyX3VzZWQgPSAwCnR3aTJfc2NsID0g cG9ydDpQQjIwPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CnR3aTJfc2RhID0gcG9ydDpQ QjIxPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CgpbdWFydF9wYXJhMF0KdWFydF91c2Vk ID0gMQp1YXJ0X3BvcnQgPSAwCnVhcnRfdHlwZSA9IDIKdWFydF90eCA9IHBvcnQ6UEIyMjwyPjwx PjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X3J4ID0gcG9ydDpQQjIzPDI+PDE+PGRlZmF1bHQ+PGRl ZmF1bHQ+CgpbdWFydF9wYXJhMV0KdWFydF91c2VkID0gMAp1YXJ0X3BvcnQgPSAxCnVhcnRfdHlw ZSA9IDgKdWFydF90eCA9IHBvcnQ6UEExMDw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X3J4 ID0gcG9ydDpQQTExPDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfcnRzID0gcG9ydDpQQTEy PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfY3RzID0gcG9ydDpQQTEzPDQ+PDE+PGRlZmF1 bHQ+PGRlZmF1bHQ+CnVhcnRfZHRyID0gcG9ydDpQQTE0PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+ CnVhcnRfZHNyID0gcG9ydDpQQTE1PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfZGNkID0g cG9ydDpQQTE2PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVhcnRfcmluZyA9IHBvcnQ6UEExNzw0 PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTJdCnVhcnRfdXNlZCA9IDEKdWFydF9w b3J0ID0gMgp1YXJ0X3R5cGUgPSA0CnVhcnRfdHggPSBwb3J0OlBJMTg8Mz48MT48ZGVmYXVsdD48 ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEkxOTwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0 X3J0cyA9IHBvcnQ6UEkxNjwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X2N0cyA9IHBvcnQ6 UEkxNzwzPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTNdCnVhcnRfdXNlZCA9IDAK dWFydF9wb3J0ID0gMwp1YXJ0X3R5cGUgPSA0CnVhcnRfdHggPSBwb3J0OlBIMDA8ND48MT48ZGVm YXVsdD48ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEgwMTw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0 Pgp1YXJ0X3J0cyA9IHBvcnQ6UEgwMjw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0Pgp1YXJ0X2N0cyA9 IHBvcnQ6UEgwMzw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTRdCnVhcnRfdXNl ZCA9IDAKdWFydF9wb3J0ID0gNAp1YXJ0X3R5cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBIMDQ8ND48 MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEgwNTw0PjwxPjxkZWZhdWx0Pjxk ZWZhdWx0PgoKW3VhcnRfcGFyYTVdCnVhcnRfdXNlZCA9IDAKdWFydF9wb3J0ID0gNQp1YXJ0X3R5 cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBIMDY8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFydF9y eCA9IHBvcnQ6UEgwNzw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTZdCnVhcnRf dXNlZCA9IDAKdWFydF9wb3J0ID0gNgp1YXJ0X3R5cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBBMTI8 ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFydF9yeCA9IHBvcnQ6UEExMzw0PjwxPjxkZWZhdWx0 PjxkZWZhdWx0PgoKW3VhcnRfcGFyYTddCnVhcnRfdXNlZCA9IDAKdWFydF9wb3J0ID0gNwp1YXJ0 X3R5cGUgPSAyCnVhcnRfdHggPSBwb3J0OlBBMTQ8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4KdWFy dF9yeCA9IHBvcnQ6UEExNTw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3NwaTBfcGFyYV0Kc3Bp X3VzZWQgPSAwCnNwaV9jc19iaXRtYXAgPSAxCnNwaV9jczAgPSBwb3J0OlBJMTA8Mj48ZGVmYXVs dD48ZGVmYXVsdD48ZGVmYXVsdD4Kc3BpX2NzMSA9IHBvcnQ6UEkxNDwyPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0PgpzcGlfc2NsayA9IHBvcnQ6UEkxMTwyPjxkZWZhdWx0PjxkZWZhdWx0Pjxk ZWZhdWx0PgpzcGlfbW9zaSA9IHBvcnQ6UEkxMjwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0 PgpzcGlfbWlzbyA9IHBvcnQ6UEkxMzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgoKW3Nw aTFfcGFyYV0Kc3BpX3VzZWQgPSAwCnNwaV9jc19iaXRtYXAgPSAxCnNwaV9jczAgPSBwb3J0OlBB MDA8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc3BpX2NzMSA9IHBvcnQ6UEEwNDwzPjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfc2NsayA9IHBvcnQ6UEEwMTwzPjxkZWZhdWx0 PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbW9zaSA9IHBvcnQ6UEEwMjwzPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0PgpzcGlfbWlzbyA9IHBvcnQ6UEEwMzwzPjxkZWZhdWx0PjxkZWZhdWx0Pjxk ZWZhdWx0PgoKW3NwaTJfcGFyYV0Kc3BpX3VzZWQgPSAwCnNwaV9jc19iaXRtYXAgPSAxCnNwaV9j czAgPSBwb3J0OlBDMTk8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc3BpX2NzMSA9IHBv cnQ6UEIxMzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfc2NsayA9IHBvcnQ6UEMy MDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbW9zaSA9IHBvcnQ6UEMyMTwzPjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbWlzbyA9IHBvcnQ6UEMyMjwzPjxkZWZhdWx0 PjxkZWZhdWx0PjxkZWZhdWx0PgoKW3NwaTNfcGFyYV0Kc3BpX3VzZWQgPSAwCnNwaV9jc19iaXRt YXAgPSAxCnNwaV9jczAgPSBwb3J0OlBBMDU8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4K c3BpX2NzMSA9IHBvcnQ6UEEwOTwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfc2Ns ayA9IHBvcnQ6UEEwNjwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbW9zaSA9IHBv cnQ6UEEwNzwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzcGlfbWlzbyA9IHBvcnQ6UEEw ODwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgoKW2N0cF9wYXJhXQpjdHBfdXNlZCA9IDAK Y3RwX25hbWUgPSAiZ3Q4MTEiCmN0cF90d2lfaWQgPSAyCmN0cF90d2lfYWRkciA9IDB4NDAKY3Rw X3NjcmVlbl9tYXhfeCA9IDEwMjQKY3RwX3NjcmVlbl9tYXhfeSA9IDYwMApjdHBfcmV2ZXJ0X3hf ZmxhZyA9IDAKY3RwX3JldmVydF95X2ZsYWcgPSAwCmN0cF9leGNoYW5nZV94X3lfZmxhZyA9IDEK Y3RwX2Zpcm0gPSAxCmN0cF9pbnRfcG9ydCA9IHBvcnQ6UEgyMTw2PjxkZWZhdWx0PjxkZWZhdWx0 PjxkZWZhdWx0PgpjdHBfd2FrZXVwID0gcG9ydDpQQjEzPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDE+ CgpbY3RwX2xpc3RfcGFyYV0KY3RwX2RldF91c2VkID0gMApmdDV4X3RzID0gMApndDgyeCA9IDAK Z3NsWDY4MCA9IDAKZ3Q5eHhfdHMgPSAwCmd0ODExID0gMAoKW3RrZXlfcGFyYV0KdGtleV91c2Vk ID0gMAp0a2V5X3R3aV9pZCA9IDIKdGtleV90d2lfYWRkciA9IDB4NjIKdGtleV9pbnQgPSBwb3J0 OlBJMTM8Nj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KClttb3Rvcl9wYXJhXQptb3Rvcl91 c2VkID0gMAptb3Rvcl9zaGFrZSA9IHBvcnQ6UEIwMzwxPjxkZWZhdWx0PjxkZWZhdWx0PjwxPgoK W2dwaW9fcGFyYV0KZ3Bpb191c2VkID0gMQpncGlvX251bSA9IDIKZ3Bpb19waW5fMSA9IHBvcnQ6 UEgyMDwxPjxkZWZhdWx0PjxkZWZhdWx0PjwxPgpncGlvX3Bpbl8yID0gcG9ydDpQSDEwPDA+PGRl ZmF1bHQ+PGRlZmF1bHQ+PDA+CgpbbGVkc19wYXJhXQpsZWRzX3VzZWQgPSAxCmxlZHNfbnVtID0g NApsZWRzX3Bpbl8xID0gcG9ydDpQSDIxPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDA+CmxlZHNfbmFt ZV8xID0gImJsdWU6cGgyMTpsZWQxIgpsZWRzX2RlZmF1bHRfMSA9IDAKbGVkc190cmlnZ2VyXzEg PSAiaGVhcnRiZWF0IgpsZWRzX3Bpbl8yID0gcG9ydDpQSDIwPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+ PDA+CmxlZHNfbmFtZV8yID0gIm9yYW5nZTpwaDIwOmxlZDIiCmxlZHNfZGVmYXVsdF8yID0gMAps ZWRzX3RyaWdnZXJfMiA9ICJjcHUwIgpsZWRzX3Bpbl8zID0gcG9ydDpQSDExPDE+PGRlZmF1bHQ+ PGRlZmF1bHQ+PDA+CmxlZHNfbmFtZV8zID0gIndoaXRlOnBoMTE6bGVkMyIKbGVkc19kZWZhdWx0 XzMgPSAwCmxlZHNfdHJpZ2dlcl8zID0gImNwdTEiCmxlZHNfcGluXzQgPSBwb3J0OlBIMDc8MT48 ZGVmYXVsdD48ZGVmYXVsdD48MD4KbGVkc19uYW1lXzQgPSAiZ3JlZW46cGgwNzpsZWQ0IgpsZWRz X2RlZmF1bHRfNCA9IDEKbGVkc190cmlnZ2VyXzQgPSAibW1jMCIKCltuYW5kX3BhcmFdCm5hbmRf dXNlZCA9IDEKbmFuZF93ZSA9IHBvcnQ6UEMwMDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0 PgpuYW5kX2FsZSA9IHBvcnQ6UEMwMTwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5k X2NsZSA9IHBvcnQ6UEMwMjwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2NlMSA9 IHBvcnQ6UEMwMzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2NlMCA9IHBvcnQ6 UEMwNDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX25yZSA9IHBvcnQ6UEMwNTwy PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX3JiMCA9IHBvcnQ6UEMwNjwyPjxkZWZh dWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX3JiMSA9IHBvcnQ6UEMwNzwyPjxkZWZhdWx0Pjxk ZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2QwID0gcG9ydDpQQzA4PDI+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+Cm5hbmRfZDEgPSBwb3J0OlBDMDk8Mj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVs dD4KbmFuZF9kMiA9IHBvcnQ6UEMxMDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5k X2QzID0gcG9ydDpQQzExPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+Cm5hbmRfZDQgPSBw b3J0OlBDMTI8Mj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KbmFuZF9kNSA9IHBvcnQ6UEMx MzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpuYW5kX2Q2ID0gcG9ydDpQQzE0PDI+PGRl ZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+Cm5hbmRfZDcgPSBwb3J0OlBDMTU8Mj48ZGVmYXVsdD48 ZGVmYXVsdD48ZGVmYXVsdD4KbmFuZF93cCA9IHBvcnQ6UEMxNjwyPjxkZWZhdWx0PjxkZWZhdWx0 PjxkZWZhdWx0PgpuYW5kX2NlMiA9IHBvcnQ6UEMxNzwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0PgpuYW5kX2NlMyA9IHBvcnQ6UEMxODwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpu YW5kX2NlNCA9Cm5hbmRfY2U1ID0KbmFuZF9jZTYgPQpuYW5kX2NlNyA9Cm5hbmRfc3BpID0gcG9y dDpQQzIzPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+Cm5hbmRfbmRxcyA9IHBvcnQ6UEMy NDwyPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpnb29kX2Jsb2NrX3JhdGlvID0gMAoKW2Rp c3BfaW5pdF0KZGlzcF9pbml0X2VuYWJsZSA9IDEKZGlzcF9tb2RlID0gMApzY3JlZW4wX291dHB1 dF90eXBlID0gMwpzY3JlZW4wX291dHB1dF9tb2RlID0gNApzY3JlZW4xX291dHB1dF90eXBlID0g MApzY3JlZW4xX291dHB1dF9tb2RlID0gNApmYjBfd2lkdGggPSAxMDI0CmZiMF9oZWlnaHQgPSA3 NjgKZmIwX2ZyYW1lYnVmZmVyX251bSA9IDIKZmIwX2Zvcm1hdCA9IDEwCmZiMF9waXhlbF9zZXF1 ZW5jZSA9IDAKZmIwX3NjYWxlcl9tb2RlX2VuYWJsZSA9IDEKZmIxX3dpZHRoID0gMTAyNApmYjFf aGVpZ2h0ID0gNzY4CmZiMV9mcmFtZWJ1ZmZlcl9udW0gPSAyCmZiMV9mb3JtYXQgPSAxMApmYjFf cGl4ZWxfc2VxdWVuY2UgPSAwCmZiMV9zY2FsZXJfbW9kZV9lbmFibGUgPSAwCmxjZDBfYmFja2xp Z2h0ID0gMTk3CmxjZDFfYmFja2xpZ2h0ID0gMTk3CmxjZDBfYnJpZ2h0ID0gNTAKbGNkMF9jb250 cmFzdCA9IDUwCmxjZDBfc2F0dXJhdGlvbiA9IDU3CmxjZDBfaHVlID0gNTAKbGNkMV9icmlnaHQg PSA1MApsY2QxX2NvbnRyYXN0ID0gNTAKbGNkMV9zYXR1cmF0aW9uID0gNTcKbGNkMV9odWUgPSA1 MAoKW2xjZDBfcGFyYV0KbGNkX3VzZWQgPSAxCmxjZF94ID0gMTAyNApsY2RfeSA9IDYwMApsY2Rf ZGNsa19mcmVxID0gNTEKbGNkX3B3bV9ub3RfdXNlZCA9IDAKbGNkX3B3bV9jaCA9IDAKbGNkX3B3 bV9mcmVxID0gMTAwMDAKbGNkX3B3bV9wb2wgPSAxCmxjZF9tYXhfYnJpZ2h0ID0gMjQwCmxjZF9t aW5fYnJpZ2h0ID0gNjQKbGNkX2lmID0gMApsY2RfaGJwID0gMTU4CmxjZF9odCA9IDEzNDQKbGNk X3ZicCA9IDI1CmxjZF92dCA9IDEyNzAKbGNkX3ZzcHcgPSAzCmxjZF9oc3B3ID0gMjAKbGNkX2h2 X2lmID0gMApsY2RfaHZfc21vZGUgPSAwCmxjZF9odl9zODg4X2lmID0gMApsY2RfaHZfc3l1dl9p ZiA9IDAKbGNkX2x2ZHNfY2ggPSAwCmxjZF9sdmRzX21vZGUgPSAwCmxjZF9sdmRzX2JpdHdpZHRo ID0gMApsY2RfbHZkc19pb19jcm9zcyA9IDAKbGNkX2NwdV9pZiA9IDAKbGNkX2ZybSA9IDEKbGNk X2lvX2NmZzAgPSAwCmxjZF9nYW1tYV9jb3JyZWN0aW9uX2VuID0gMApsY2RfZ2FtbWFfdGJsXzAg PSAweDAKbGNkX2dhbW1hX3RibF8xID0gMHgxMDEwMQpsY2RfZ2FtbWFfdGJsXzI1NSA9IDB4ZmZm ZmZmCmxjZF9ibF9lbl91c2VkID0gMApsY2RfYmxfZW4gPSBwb3J0OlBIMDc8MT48MD48ZGVmYXVs dD48MT4KbGNkX3Bvd2VyX3VzZWQgPSAwCmxjZF9wb3dlciA9IHBvcnQ6UEgwODwxPjwwPjxkZWZh dWx0PjwxPgpsY2RfcHdtX3VzZWQgPSAwCmxjZF9wd20gPSBwb3J0OlBCMDI8Mj48MD48ZGVmYXVs dD48ZGVmYXVsdD4KbGNkZDAgPSBwb3J0OlBEMDA8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNk ZDEgPSBwb3J0OlBEMDE8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDIgPSBwb3J0OlBEMDI8 Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDMgPSBwb3J0OlBEMDM8Mj48MD48ZGVmYXVsdD48 ZGVmYXVsdD4KbGNkZDQgPSBwb3J0OlBEMDQ8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDUg PSBwb3J0OlBEMDU8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDYgPSBwb3J0OlBEMDY8Mj48 MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDcgPSBwb3J0OlBEMDc8Mj48MD48ZGVmYXVsdD48ZGVm YXVsdD4KbGNkZDggPSBwb3J0OlBEMDg8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDkgPSBw b3J0OlBEMDk8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDEwID0gcG9ydDpQRDEwPDI+PDA+ PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxMSA9IHBvcnQ6UEQxMTwyPjwwPjxkZWZhdWx0PjxkZWZh dWx0PgpsY2RkMTIgPSBwb3J0OlBEMTI8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDEzID0g cG9ydDpQRDEzPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxNCA9IHBvcnQ6UEQxNDwyPjww PjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTUgPSBwb3J0OlBEMTU8Mj48MD48ZGVmYXVsdD48ZGVm YXVsdD4KbGNkZDE2ID0gcG9ydDpQRDE2PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxNyA9 IHBvcnQ6UEQxNzwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTggPSBwb3J0OlBEMTg8Mj48 MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDE5ID0gcG9ydDpQRDE5PDI+PDA+PGRlZmF1bHQ+PGRl ZmF1bHQ+CmxjZGQyMCA9IHBvcnQ6UEQyMDwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMjEg PSBwb3J0OlBEMjE8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDIyID0gcG9ydDpQRDIyPDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQyMyA9IHBvcnQ6UEQyMzwyPjwwPjxkZWZhdWx0Pjxk ZWZhdWx0PgpsY2RjbGsgPSBwb3J0OlBEMjQ8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZGUg PSBwb3J0OlBEMjU8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkaHN5bmMgPSBwb3J0OlBEMjY8 Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkdnN5bmMgPSBwb3J0OlBEMjc8Mj48MD48ZGVmYXVs dD48ZGVmYXVsdD4KCltsY2QxX3BhcmFdCmxjZF91c2VkID0gMApsY2RfeCA9IDAKbGNkX3kgPSAw CmxjZF9kY2xrX2ZyZXEgPSAwCmxjZF9wd21fbm90X3VzZWQgPSAwCmxjZF9wd21fY2ggPSAxCmxj ZF9wd21fZnJlcSA9IDAKbGNkX3B3bV9wb2wgPSAwCmxjZF9tYXhfYnJpZ2h0ID0gMjQwCmxjZF9t aW5fYnJpZ2h0ID0gNjQKbGNkX2lmID0gMApsY2RfaGJwID0gMApsY2RfaHQgPSAwCmxjZF92YnAg PSAwCmxjZF92dCA9IDAKbGNkX3ZzcHcgPSAwCmxjZF9oc3B3ID0gMApsY2RfaHZfaWYgPSAwCmxj ZF9odl9zbW9kZSA9IDAKbGNkX2h2X3M4ODhfaWYgPSAwCmxjZF9odl9zeXV2X2lmID0gMApsY2Rf bHZkc19jaCA9IDAKbGNkX2x2ZHNfbW9kZSA9IDAKbGNkX2x2ZHNfYml0d2lkdGggPSAwCmxjZF9s dmRzX2lvX2Nyb3NzID0gMApsY2RfY3B1X2lmID0gMApsY2RfZnJtID0gMApsY2RfaW9fY2ZnMCA9 IDAKbGNkX2dhbW1hX2NvcnJlY3Rpb25fZW4gPSAwCmxjZF9nYW1tYV90YmxfMCA9IDB4MApsY2Rf Z2FtbWFfdGJsXzEgPSAweDEwMTAxCmxjZF9nYW1tYV90YmxfMjU1ID0gMHhmZmZmZmYKbGNkX2Js X2VuX3VzZWQgPSAwCmxjZF9ibF9lbiA9CmxjZF9wb3dlcl91c2VkID0gMApsY2RfcG93ZXIgPQps Y2RfcHdtX3VzZWQgPSAxCmxjZF9wd20gPSBwb3J0OlBJMDM8Mj48MD48ZGVmYXVsdD48ZGVmYXVs dD4KbGNkX2dwaW9fMCA9CmxjZF9ncGlvXzEgPQpsY2RfZ3Bpb18yID0KbGNkX2dwaW9fMyA9Cmxj ZGQwID0gcG9ydDpQSDAwPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxID0gcG9ydDpQSDAx PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQyID0gcG9ydDpQSDAyPDI+PDA+PGRlZmF1bHQ+ PGRlZmF1bHQ+CmxjZGQzID0gcG9ydDpQSDAzPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ0 ID0gcG9ydDpQSDA0PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ1ID0gcG9ydDpQSDA1PDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ2ID0gcG9ydDpQSDA2PDI+PDA+PGRlZmF1bHQ+PGRl ZmF1bHQ+CmxjZGQ3ID0gcG9ydDpQSDA3PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ4ID0g cG9ydDpQSDA4PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQ5ID0gcG9ydDpQSDA5PDI+PDA+ PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxMCA9IHBvcnQ6UEgxMDwyPjwwPjxkZWZhdWx0PjxkZWZh dWx0PgpsY2RkMTEgPSBwb3J0OlBIMTE8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDEyID0g cG9ydDpQSDEyPDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxMyA9IHBvcnQ6UEgxMzwyPjww PjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTQgPSBwb3J0OlBIMTQ8Mj48MD48ZGVmYXVsdD48ZGVm YXVsdD4KbGNkZDE1ID0gcG9ydDpQSDE1PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQxNiA9 IHBvcnQ6UEgxNjwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMTcgPSBwb3J0OlBIMTc8Mj48 MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDE4ID0gcG9ydDpQSDE4PDI+PDA+PGRlZmF1bHQ+PGRl ZmF1bHQ+CmxjZGQxOSA9IHBvcnQ6UEgxOTwyPjwwPjxkZWZhdWx0PjxkZWZhdWx0PgpsY2RkMjAg PSBwb3J0OlBIMjA8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkZDIxID0gcG9ydDpQSDIxPDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGQyMiA9IHBvcnQ6UEgyMjwyPjwwPjxkZWZhdWx0Pjxk ZWZhdWx0PgpsY2RkMjMgPSBwb3J0OlBIMjM8Mj48MD48ZGVmYXVsdD48ZGVmYXVsdD4KbGNkY2xr ID0gcG9ydDpQSDI0PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGRlID0gcG9ydDpQSDI1PDI+ PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+CmxjZGhzeW5jID0gcG9ydDpQSDI2PDI+PDA+PGRlZmF1bHQ+ PGRlZmF1bHQ+CmxjZHZzeW5jID0gcG9ydDpQSDI3PDI+PDA+PGRlZmF1bHQ+PGRlZmF1bHQ+Cgpb dHZfb3V0X2RhY19wYXJhXQpkYWNfdXNlZCA9IDEKZGFjMF9zcmMgPSA0CmRhYzFfc3JjID0gNQpk YWMyX3NyYyA9IDYKZGFjM19zcmMgPSAwCgpbaGRtaV9wYXJhXQpoZG1pX3VzZWQgPSAxCgpbY2Ft ZXJhX2xpc3RfcGFyYV0KY2FtZXJhX2xpc3RfcGFyYV91c2VkID0gMQpvdjc2NzAgPSAwCmdjMDMw OCA9IDEKZ3QyMDA1ID0gMQpoaTcwNCA9IDAKc3AwODM4ID0gMAptdDltMTEyID0gMAptdDltMTEz ID0gMApvdjI2NTUgPSAwCmhpMjUzID0gMApnYzAzMDcgPSAwCm10OWQxMTIgPSAwCm92NTY0MCA9 IDAKZ2MyMDE1ID0gMApvdjI2NDMgPSAwCmdjMDMyOSA9IDAKZ2MwMzA5ID0gMAp0dnA1MTUwID0g MApzNWs0ZWMgPSAwCm92NTY1MF9tdjkzMzUgPSAwCnNpdjEyMWQgPSAwCmdjMjAzNSA9IDAKCltj c2kwX3BhcmFdCmNzaV91c2VkID0gMApjc2lfZGV2X3F0eSA9IDIKY3NpX3N0YnlfbW9kZSA9IDAK Y3NpX21uYW1lID0gImdjMDMwOCIKY3NpX3R3aV9pZCA9IDEKY3NpX3R3aV9hZGRyID0gMHg0Mgpj c2lfaWYgPSAwCmNzaV92ZmxpcCA9IDAKY3NpX2hmbGlwID0gMApjc2lfaW92ZGQgPSAiYXhwMjBf cGxsIgpjc2lfYXZkZCA9ICIiCmNzaV9kdmRkID0gIiIKY3NpX3ZvbF9pb3ZkZCA9IDI4MDAKY3Np X3ZvbF9kdmRkID0KY3NpX3ZvbF9hdmRkID0KY3NpX2ZsYXNoX3BvbCA9IDAKY3NpX21uYW1lX2Ig PSAiZ3QyMDA1Igpjc2lfdHdpX2lkX2IgPSAxCmNzaV90d2lfYWRkcl9iID0gMHg3OApjc2lfaWZf YiA9IDAKY3NpX3ZmbGlwX2IgPSAwCmNzaV9oZmxpcF9iID0gMApjc2lfaW92ZGRfYiA9ICJheHAy MF9wbGwiCmNzaV9hdmRkX2IgPSAiIgpjc2lfZHZkZF9iID0gIiIKY3NpX3ZvbF9pb3ZkZF9iID0g MjgwMApjc2lfdm9sX2F2ZGRfYiA9CmNzaV92b2xfZHZkZF9iID0KY3NpX2ZsYXNoX3BvbF9iID0g MApjc2lfcGNrID0gcG9ydDpQRTAwPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9j ayA9IHBvcnQ6UEUwMTwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfaHN5bmMgPSBw b3J0OlBFMDI8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX3ZzeW5jID0gcG9ydDpQ RTAzPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9kMCA9IHBvcnQ6UEUwNDwzPjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfZDEgPSBwb3J0OlBFMDU8Mz48ZGVmYXVsdD48 ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2QyID0gcG9ydDpQRTA2PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+CmNzaV9kMyA9IHBvcnQ6UEUwNzwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0 Pgpjc2lfZDQgPSBwb3J0OlBFMDg8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2Q1 ID0gcG9ydDpQRTA5PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9kNiA9IHBvcnQ6 UEUxMDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfZDcgPSBwb3J0OlBFMTE8Mz48 ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX3Jlc2V0ID0gcG9ydDpQSDE0PDE+PGRlZmF1 bHQ+PGRlZmF1bHQ+PDA+CmNzaV9wb3dlcl9lbiA9IHBvcnQ6UEgxNzwxPjxkZWZhdWx0PjxkZWZh dWx0PjwwPgpjc2lfc3RieSA9IHBvcnQ6UEgxOTwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgpjc2lf Zmxhc2ggPQpjc2lfYWZfZW4gPQpjc2lfcmVzZXRfYiA9IHBvcnQ6UEgxNDwxPjxkZWZhdWx0Pjxk ZWZhdWx0PjwwPgpjc2lfcG93ZXJfZW5fYiA9IHBvcnQ6UEgxNzwxPjxkZWZhdWx0PjxkZWZhdWx0 PjwwPgpjc2lfc3RieV9iID0gcG9ydDpQSDE4PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDA+CmNzaV9m bGFzaF9iID0KY3NpX2FmX2VuX2IgPQoKW2NzaTFfcGFyYV0KY3NpX3VzZWQgPSAwCmNzaV9kZXZf cXR5ID0gMQpjc2lfc3RieV9tb2RlID0gMApjc2lfbW5hbWUgPSAiZ2MwMzA4Igpjc2lfaWYgPSAw CmNzaV9pb3ZkZCA9ICJheHAyMF9wbGwiCmNzaV9hdmRkID0gIiIKY3NpX2R2ZGQgPSAiIgpjc2lf dm9sX2lvdmRkID0gMjgwMApjc2lfdm9sX2R2ZGQgPQpjc2lfdm9sX2F2ZGQgPQpjc2lfdmZsaXAg PSAwCmNzaV9oZmxpcCA9IDAKY3NpX2ZsYXNoX3BvbCA9IDAKY3NpX2ZhY2luZyA9IDEKY3NpX3R3 aV9pZCA9IDEKY3NpX3R3aV9hZGRyID0gMHg0Mgpjc2lfcGNrID0gcG9ydDpQRzAwPDM+PGRlZmF1 bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9jayA9IHBvcnQ6UEcwMTwzPjxkZWZhdWx0PjxkZWZh dWx0PjxkZWZhdWx0Pgpjc2lfaHN5bmMgPSBwb3J0OlBHMDI8Mz48ZGVmYXVsdD48ZGVmYXVsdD48 ZGVmYXVsdD4KY3NpX3ZzeW5jID0gcG9ydDpQRzAzPDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1 bHQ+CmNzaV9kMCA9IHBvcnQ6UEcwNDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lf ZDEgPSBwb3J0OlBHMDU8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2QyID0gcG9y dDpQRzA2PDM+PGRlZmF1bHQ+PGRlZmF1bHQ+PGRlZmF1bHQ+CmNzaV9kMyA9IHBvcnQ6UEcwNzwz PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgpjc2lfZDQgPSBwb3J0OlBHMDg8Mz48ZGVmYXVs dD48ZGVmYXVsdD48ZGVmYXVsdD4KY3NpX2Q1ID0gcG9ydDpQRzA5PDM+PGRlZmF1bHQ+PGRlZmF1 bHQ+PGRlZmF1bHQ+CmNzaV9kNiA9IHBvcnQ6UEcxMDwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0Pgpjc2lfZDcgPSBwb3J0OlBHMTE8Mz48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KY3Np X3Jlc2V0ID0gcG9ydDpQSDEzPDE+PGRlZmF1bHQ+PGRlZmF1bHQ+PDA+CmNzaV9wb3dlcl9lbiA9 IHBvcnQ6UEgxNjwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgpjc2lfc3RieSA9IHBvcnQ6UEgxOTwx PjxkZWZhdWx0PjxkZWZhdWx0PjwwPgoKW3R2b3V0X3BhcmFdCnR2b3V0X3VzZWQgPSAxCnR2b3V0 X2NoYW5uZWxfbnVtID0gMQoKW3R2aW5fcGFyYV0KdHZpbl91c2VkID0gMAp0dmluX2NoYW5uZWxf bnVtID0gNAoKW3B3bTBfcGFyYV0KcHdtX3VzZWQgPSAxCnB3bV9wZXJpb2QgPSAyMApwd21fZHV0 eV9wZXJjZW50ID0gNTAKCltzYXRhX3BhcmFdCnNhdGFfdXNlZCA9IDEKc2F0YV9wb3dlcl9lbiA9 IHBvcnQ6UEgxMjwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgoKW21tYzBfcGFyYV0Kc2RjX3VzZWQg PSAxCnNkY19kZXRtb2RlID0gMQpzZGNfYnVzd2lkdGggPSA0CnNkY19jbGsgPSBwb3J0OlBGMDI8 Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2NtZCA9IHBvcnQ6UEYwMzwyPjwxPjwyPjxkZWZhdWx0Pgpz ZGNfZDAgPSBwb3J0OlBGMDE8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2QxID0gcG9ydDpQRjAwPDI+ PDE+PDI+PGRlZmF1bHQ+CnNkY19kMiA9IHBvcnQ6UEYwNTwyPjwxPjwyPjxkZWZhdWx0PgpzZGNf ZDMgPSBwb3J0OlBGMDQ8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2RldCA9IHBvcnQ6UEgwMTwwPjwx PjxkZWZhdWx0PjxkZWZhdWx0PgpzZGNfdXNlX3dwID0gMApzZGNfd3AgPQpzZGNfaXNpbyA9IDAK c2RjX3JlZ3VsYXRvciA9ICJub25lIgoKW21tYzFfcGFyYV0Kc2RjX3VzZWQgPSAwCnNkY19kZXRt b2RlID0gNApzZGNfYnVzd2lkdGggPSA0CnNkY19jbGsgPSBwb3J0OlBHMDA8Mj48MT48Mj48ZGVm YXVsdD4Kc2RjX2NtZCA9IHBvcnQ6UEcwMTwyPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDAgPSBwb3J0 OlBHMDI8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2QxID0gcG9ydDpQRzAzPDI+PDE+PDI+PGRlZmF1 bHQ+CnNkY19kMiA9IHBvcnQ6UEcwNDwyPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDMgPSBwb3J0OlBH MDU8Mj48MT48Mj48ZGVmYXVsdD4Kc2RjX2RldCA9CnNkY191c2Vfd3AgPSAwCnNkY193cCA9CnNk Y19pc2lvID0gMApzZGNfcmVndWxhdG9yID0gIm5vbmUiCgpbbW1jMl9wYXJhXQpzZGNfdXNlZCA9 IDAKc2RjX2RldG1vZGUgPSAzCnNkY19idXN3aWR0aCA9IDQKc2RjX2NtZCA9IHBvcnQ6UEMwNjwz PjwxPjwyPjxkZWZhdWx0PgpzZGNfY2xrID0gcG9ydDpQQzA3PDM+PDE+PDI+PGRlZmF1bHQ+CnNk Y19kMCA9IHBvcnQ6UEMwODwzPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDEgPSBwb3J0OlBDMDk8Mz48 MT48Mj48ZGVmYXVsdD4Kc2RjX2QyID0gcG9ydDpQQzEwPDM+PDE+PDI+PGRlZmF1bHQ+CnNkY19k MyA9IHBvcnQ6UEMxMTwzPjwxPjwyPjxkZWZhdWx0PgpzZGNfZGV0ID0Kc2RjX3VzZV93cCA9IDAK c2RjX3dwID0Kc2RjX2lzaW8gPSAwCnNkY19yZWd1bGF0b3IgPSAibm9uZSIKClttbWMzX3BhcmFd CnNkY191c2VkID0gMQpzZGNfZGV0bW9kZSA9IDQKc2RjX2J1c3dpZHRoID0gNApzZGNfY21kID0g cG9ydDpQSTA0PDI+PDE+PDI+PGRlZmF1bHQ+CnNkY19jbGsgPSBwb3J0OlBJMDU8Mj48MT48Mj48 ZGVmYXVsdD4Kc2RjX2QwID0gcG9ydDpQSTA2PDI+PDE+PDI+PGRlZmF1bHQ+CnNkY19kMSA9IHBv cnQ6UEkwNzwyPjwxPjwyPjxkZWZhdWx0PgpzZGNfZDIgPSBwb3J0OlBJMDg8Mj48MT48Mj48ZGVm YXVsdD4Kc2RjX2QzID0gcG9ydDpQSTA5PDI+PDE+PDI+PGRlZmF1bHQ+CnNkY19kZXQgPQpzZGNf dXNlX3dwID0gMApzZGNfd3AgPQpzZGNfaXNpbyA9IDEKc2RjX3JlZ3VsYXRvciA9ICJub25lIgoK W21zX3BhcmFdCm1zX3VzZWQgPSAwCm1zX2JzID0gcG9ydDpQSDA2PDU+PGRlZmF1bHQ+PGRlZmF1 bHQ+PGRlZmF1bHQ+Cm1zX2NsayA9IHBvcnQ6UEgwNzw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0Pgptc19kMCA9IHBvcnQ6UEgwODw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19k MSA9IHBvcnQ6UEgwOTw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19kMiA9IHBvcnQ6 UEgxMDw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19kMyA9IHBvcnQ6UEgxMTw1Pjxk ZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0Pgptc19kZXQgPQoKW3NtY19wYXJhXQpzbWNfdXNlZCA9 IDAKc21jX3JzdCA9IHBvcnQ6UEgxMzw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzbWNf dnBwZW4gPSBwb3J0OlBIMTQ8NT48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc21jX3ZwcHAg PSBwb3J0OlBIMTU8NT48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc21jX2RldCA9IHBvcnQ6 UEgxNjw1PjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzbWNfdmNjZW4gPSBwb3J0OlBIMTc8 NT48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4Kc21jX3NjayA9IHBvcnQ6UEgxODw1PjxkZWZh dWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpzbWNfc2RhID0gcG9ydDpQSDE5PDU+PGRlZmF1bHQ+PGRl ZmF1bHQ+PGRlZmF1bHQ+CgpbcHMyXzBfcGFyYV0KcHMyX3VzZWQgPSAwCnBzMl9zY2wgPSBwb3J0 OlBJMjA8Mj48MT48ZGVmYXVsdD48ZGVmYXVsdD4KcHMyX3NkYSA9IHBvcnQ6UEkyMTwyPjwxPjxk ZWZhdWx0PjxkZWZhdWx0PgoKW3BzMl8xX3BhcmFdCnBzMl91c2VkID0gMApwczJfc2NsID0gcG9y dDpQSTE0PDM+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnBzMl9zZGEgPSBwb3J0OlBJMTU8Mz48MT48 ZGVmYXVsdD48ZGVmYXVsdD4KCltjYW5fcGFyYV0KY2FuX3VzZWQgPSAwCmNhbl90eCA9IHBvcnQ6 UEExNjwzPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpjYW5fcnggPSBwb3J0OlBBMTc8Mz48 ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KCltrZXlwYWRfcGFyYV0Ka3BfdXNlZCA9IDAKa3Bf aW5fc2l6ZSA9IDgKa3Bfb3V0X3NpemUgPSA4CmtwX2luMCA9IHBvcnQ6UEgwODw0PjwxPjxkZWZh dWx0PjxkZWZhdWx0PgprcF9pbjEgPSBwb3J0OlBIMDk8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4K a3BfaW4yID0gcG9ydDpQSDEwPDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CmtwX2luMyA9IHBvcnQ6 UEgxMTw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9pbjQgPSBwb3J0OlBIMTQ8ND48MT48ZGVm YXVsdD48ZGVmYXVsdD4Ka3BfaW41ID0gcG9ydDpQSDE1PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+ CmtwX2luNiA9IHBvcnQ6UEgxNjw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9pbjcgPSBwb3J0 OlBIMTc8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4Ka3Bfb3V0MCA9IHBvcnQ6UEgxODw0PjwxPjxk ZWZhdWx0PjxkZWZhdWx0PgprcF9vdXQxID0gcG9ydDpQSDE5PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1 bHQ+CmtwX291dDIgPSBwb3J0OlBIMjI8ND48MT48ZGVmYXVsdD48ZGVmYXVsdD4Ka3Bfb3V0MyA9 IHBvcnQ6UEgyMzw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9vdXQ0ID0gcG9ydDpQSDI0PDQ+ PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CmtwX291dDUgPSBwb3J0OlBIMjU8ND48MT48ZGVmYXVsdD48 ZGVmYXVsdD4Ka3Bfb3V0NiA9IHBvcnQ6UEgyNjw0PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgprcF9v dXQ3ID0gcG9ydDpQSDI3PDQ+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CgpbdXNiYzBdCnVzYl91c2Vk ID0gMQp1c2JfcG9ydF90eXBlID0gMgp1c2JfZGV0ZWN0X3R5cGUgPSAxCnVzYl9pZF9ncGlvID0g cG9ydDpQSDE5PDA+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+CnVzYl9kZXRfdmJ1c19ncGlvID0gcG9y dDpQSDIyPDE+PDA+PGRlZmF1bHQ+PDA+CnVzYl9kcnZfdmJ1c19ncGlvID0gcG9ydDpQSDE3PDE+ PDA+PGRlZmF1bHQ+PDA+CnVzYl9yZXN0cmljdF9ncGlvID0gcG9ydDpQSDAwPDE+PDA+PGRlZmF1 bHQ+PDA+CnVzYl9ob3N0X2luaXRfc3RhdGUgPSAxCnVzYl9yZXN0cmljX2ZsYWcgPSAwCnVzYl9y ZXN0cmljX3ZvbHRhZ2UgPSAzNTUwMDAwCnVzYl9yZXN0cmljX2NhcGFjaXR5ID0gNQoKW3VzYmMx XQp1c2JfdXNlZCA9IDEKdXNiX3BvcnRfdHlwZSA9IDEKdXNiX2RldGVjdF90eXBlID0gMAp1c2Jf ZHJ2X3ZidXNfZ3BpbyA9IHBvcnQ6UEgwNjwxPjwwPjxkZWZhdWx0PjwwPgp1c2JfcmVzdHJpY3Rf Z3BpbyA9CnVzYl9ob3N0X2luaXRfc3RhdGUgPSAxCnVzYl9yZXN0cmljX2ZsYWcgPSAwCgpbdXNi YzJdCnVzYl91c2VkID0gMQp1c2JfcG9ydF90eXBlID0gMQp1c2JfZGV0ZWN0X3R5cGUgPSAwCnVz Yl9kcnZfdmJ1c19ncGlvID0gcG9ydDpQSDAzPDE+PDA+PGRlZmF1bHQ+PDA+CnVzYl9yZXN0cmlj dF9ncGlvID0KdXNiX2hvc3RfaW5pdF9zdGF0ZSA9IDEKdXNiX3Jlc3RyaWNfZmxhZyA9IDAKClt1 c2JfZmVhdHVyZV0KdmVuZG9yX2lkID0gNjM1MwptYXNzX3N0b3JhZ2VfaWQgPSAxCmFkYl9pZCA9 IDIKbWFudWZhY3R1cmVyX25hbWUgPSAiVVNCIERldmVsb3BlciIKcHJvZHVjdF9uYW1lID0gIkFu ZHJvaWQiCnNlcmlhbF9udW1iZXIgPSAiMjAwODA0MTEiCgpbbXNjX2ZlYXR1cmVdCnZlbmRvcl9u YW1lID0gIlVTQiAyLjAiCnByb2R1Y3RfbmFtZSA9ICJVU0IgRmxhc2ggRHJpdmVyIgpyZWxlYXNl ID0gMTAwCmx1bnMgPSAzCgpbZ3NlbnNvcl9wYXJhXQpnc2Vuc29yX3VzZWQgPSAwCmdzZW5zb3Jf dHdpX2lkID0gMQpnc2Vuc29yX2ludDEgPQpnc2Vuc29yX2ludDIgPQoKW2dzZW5zb3JfbGlzdF9w YXJhXQpnc2Vuc29yX2RldF91c2VkID0gMQpibWEyNTAgPSAxCm1tYTg0NTIgPSAxCm1tYTc2NjAg PSAxCm1tYTg2NXggPSAxCmFmYTc1MCA9IDEKbGlzM2RlX2FjYyA9IDEKbGlzM2RoX2FjYyA9IDEK a3h0aWsgPSAxCmRtYXJkMTAgPSAwCmRtYXJkMDYgPSAxCm14YzYyMnggPSAxCmZ4b3M4NzAwID0g MQpsc20zMDNkID0gMQoKW2dwc19wYXJhXQpncHNfdXNlZCA9IDAKZ3BzX3NwaV9pZCA9IDIKZ3Bz X3NwaV9jc19udW0gPSAwCmdwc19scmFkYyA9IDEKZ3BzX2NsayA9IHBvcnQ6UEkwMDwyPjxkZWZh dWx0PjxkZWZhdWx0PjxkZWZhdWx0PgpncHNfc2lnbiA9IHBvcnQ6UEkwMTwyPjxkZWZhdWx0Pjxk ZWZhdWx0PjxkZWZhdWx0PgpncHNfbWFnID0gcG9ydDpQSTAyPDI+PGRlZmF1bHQ+PGRlZmF1bHQ+ PGRlZmF1bHQ+Cmdwc192Y2NfZW4gPSBwb3J0OlBDMjI8MT48ZGVmYXVsdD48ZGVmYXVsdD48MD4K Z3BzX29zY19lbiA9IHBvcnQ6UEkxNDwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgpncHNfcnhfZW4g PSBwb3J0OlBJMTU8MT48ZGVmYXVsdD48ZGVmYXVsdD48MD4KClt3aWZpX3BhcmFdCndpZmlfdXNl ZCA9IDEKd2lmaV9zZGNfaWQgPSAzCndpZmlfdXNiY19pZCA9IDIKd2lmaV91c2JjX3R5cGUgPSAx CndpZmlfbW9kX3NlbCA9IDcKd2lmaV9wb3dlciA9ICIiCmFwNnh4eF93bF9yZWdvbiA9IHBvcnQ6 UEgwOTwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgphcDZ4eHhfYnRfcmVnb24gPSBwb3J0OlBIMTg8 MT48ZGVmYXVsdD48ZGVmYXVsdD48MD4KYXA2eHh4X2J0X3dha2UgPSBwb3J0OlBIMjQ8MT48ZGVm YXVsdD48ZGVmYXVsdD48MD4KYXA2eHh4X2J0X2hvc3Rfd2FrZSA9IHBvcnQ6UEgyNTwwPjxkZWZh dWx0PjxkZWZhdWx0PjwwPgphcDZ4eHhfbHBvID0gcG9ydDpQSTEyPDQ+PDE+PGRlZmF1bHQ+PDE+ CgpbdXNiX3dpZmlfcGFyYV0KdXNiX3dpZmlfdXNlZCA9IDAKdXNiX3dpZmlfdXNiY19udW0gPSAy CgpbM2dfcGFyYV0KM2dfdXNlZCA9IDAKM2dfdXNiY19udW0gPSAyCjNnX3VhcnRfbnVtID0gMAoz Z19wd3IgPQozZ193YWtldXAgPQozZ19pbnQgPQoKW2d5X3BhcmFdCmd5X3VzZWQgPSAwCmd5X3R3 aV9pZCA9IDEKZ3lfdHdpX2FkZHIgPSAwCmd5X2ludDEgPSBwb3J0OlBIMTg8Nj48MT48ZGVmYXVs dD48ZGVmYXVsdD4KZ3lfaW50MiA9IHBvcnQ6UEgxOTw2PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoK W2xzX3BhcmFdCmxzX3VzZWQgPSAwCmxzX3R3aV9pZCA9IDEKbHNfdHdpX2FkZHIgPSAwCmxzX2lu dCA9IHBvcnQ6UEgyMDw2PjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW2NvbXBhc3NfcGFyYV0KY29t cGFzc191c2VkID0gMApjb21wYXNzX3R3aV9pZCA9IDEKY29tcGFzc190d2lfYWRkciA9IDAKY29t cGFzc19pbnQgPSBwb3J0OlBJMTM8Nj48MT48ZGVmYXVsdD48ZGVmYXVsdD4KCltidF9wYXJhXQpi dF91c2VkID0gMQpidF91YXJ0X2lkID0gMgoKW2kyc19wYXJhXQppMnNfdXNlZCA9IDEKaTJzX2No YW5uZWwgPSAyCmkyc19tY2xrID0gcG9ydDpQQjA1PDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+Cmky c19iY2xrID0gcG9ydDpQQjA2PDI+PDE+PGRlZmF1bHQ+PGRlZmF1bHQ+Cmkyc19scmNsayA9IHBv cnQ6UEIwNzwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgppMnNfZG91dDAgPSBwb3J0OlBCMDg8Mj48 MT48ZGVmYXVsdD48ZGVmYXVsdD4KaTJzX2RvdXQxID0KaTJzX2RvdXQyID0KaTJzX2RvdXQzID0K aTJzX2RpbiA9IHBvcnQ6UEIxMjwyPjwxPjxkZWZhdWx0PjxkZWZhdWx0PgoKW3NwZGlmX3BhcmFd CnNwZGlmX3VzZWQgPSAxCnNwZGlmX21jbGsgPQpzcGRpZl9kb3V0ID0gcG9ydDpQQjEzPDQ+PDE+ PGRlZmF1bHQ+PGRlZmF1bHQ+CnNwZGlmX2RpbiA9CgpbYXVkaW9fcGFyYV0KYXVkaW9fdXNlZCA9 IDEKYXVkaW9fcGFfY3RybCA9IHBvcnQ6UEgxNTwxPjxkZWZhdWx0PjxkZWZhdWx0PjwwPgoKW3N3 aXRjaF9wYXJhXQpzd2l0Y2hfdXNlZCA9IDEKCltpcl9wYXJhXQppcl91c2VkID0gMQppcjBfcngg PSBwb3J0OlBCMDQ8Mj48ZGVmYXVsdD48ZGVmYXVsdD48ZGVmYXVsdD4KCltwbXVfcGFyYV0KcG11 X3VzZWQgPSAxCnBtdV90d2lfYWRkciA9IDUyCnBtdV90d2lfaWQgPSAwCnBtdV9pcnFfaWQgPSAz MgpwbXVfYmF0dGVyeV9yZGMgPSAxMjAKcG11X2JhdHRlcnlfY2FwID0gMjEwMApwbXVfaW5pdF9j aGdjdXIgPSAzMDAKcG11X2Vhcmx5c3VzcGVuZF9jaGdjdXIgPSA2MDAKcG11X3N1c3BlbmRfY2hn Y3VyID0gMTAwMApwbXVfcmVzdW1lX2NoZ2N1ciA9IDMwMApwbXVfc2h1dGRvd25fY2hnY3VyID0g MTAwMApwbXVfaW5pdF9jaGd2b2wgPSA0MjAwCnBtdV9pbml0X2NoZ2VuZF9yYXRlID0gMTUKcG11 X2luaXRfY2hnX2VuYWJsZWQgPSAxCnBtdV9pbml0X2FkY19mcmVxID0gMTAwCnBtdV9pbml0X2Fk Y19mcmVxYyA9IDEwMApwbXVfaW5pdF9jaGdfcHJldGltZSA9IDUwCnBtdV9pbml0X2NoZ19jc3R0 aW1lID0gNzIwCnBtdV9iYXRfcGFyYTEgPSAwCnBtdV9iYXRfcGFyYTIgPSAwCnBtdV9iYXRfcGFy YTMgPSAwCnBtdV9iYXRfcGFyYTQgPSAwCnBtdV9iYXRfcGFyYTUgPSA1CnBtdV9iYXRfcGFyYTYg PSAxMQpwbXVfYmF0X3BhcmE3ID0gMTMKcG11X2JhdF9wYXJhOCA9IDE1CnBtdV9iYXRfcGFyYTkg PSAxOQpwbXVfYmF0X3BhcmExMCA9IDMyCnBtdV9iYXRfcGFyYTExID0gNTAKcG11X2JhdF9wYXJh MTIgPSA1OApwbXVfYmF0X3BhcmExMyA9IDcxCnBtdV9iYXRfcGFyYTE0ID0gODEKcG11X2JhdF9w YXJhMTUgPSA4OQpwbXVfYmF0X3BhcmExNiA9IDEwMApwbXVfdXNidm9sX2xpbWl0ID0gMQpwbXVf dXNiY3VyX2xpbWl0ID0gMApwbXVfdXNidm9sID0gNDAwMApwbXVfdXNiY3VyID0gMApwbXVfdXNi dm9sX3BjID0gNDIwMApwbXVfdXNiY3VyX3BjID0gMApwbXVfcHdyb2ZmX3ZvbCA9IDMzMDAKcG11 X3B3cm9uX3ZvbCA9IDI5MDAKcG11X3Bla29mZl90aW1lID0gNjAwMApwbXVfcGVrb2ZmX2VuID0g MQpwbXVfcGVrbG9uZ190aW1lID0gMTUwMApwbXVfcGVrb25fdGltZSA9IDEwMDAKcG11X3B3cm9r X3RpbWUgPSA2NApwbXVfcHdybm9lX3RpbWUgPSAyMDAwCnBtdV9pbnRvdHBfZW4gPSAxCnBtdV91 c2VkMiA9IDAKcG11X2FkcGRldCA9IHBvcnQ6UEgwMjwwPjxkZWZhdWx0PjxkZWZhdWx0PjxkZWZh dWx0PgpwbXVfaW5pdF9jaGdjdXIyID0gNDAwCnBtdV9lYXJseXN1c3BlbmRfY2hnY3VyMiA9IDYw MApwbXVfc3VzcGVuZF9jaGdjdXIyID0gMTIwMApwbXVfcmVzdW1lX2NoZ2N1cjIgPSA0MDAKcG11 X3NodXRkb3duX2NoZ2N1cjIgPSAxMjAwCnBtdV9zdXNwZW5kcHdyb2ZmX3ZvbCA9IDM1MDAKcG11 X2JhdGRldGVuID0gMQpwbXVfYmFja3VwZW4gPSAxCgpbcmVjb3Zlcnlfa2V5XQprZXlfbWluID0g NAprZXlfbWF4ID0gNDAKCltkdmZzX3RhYmxlXQptYXhfZnJlcSA9IDkxMjAwMDAwMAptaW5fZnJl cSA9IDcyMDAwMDAwMApub3JtYWxfZnJlcSA9IDcyMDAwMDAwMApMVl9jb3VudCA9IDcKTFYxX2Zy ZXEgPSAxMDA4MDAwMDAwCkxWMV92b2x0ID0gMTQ1MApMVjJfZnJlcSA9IDkxMjAwMDAwMApMVjJf dm9sdCA9IDE0MjUKTFYzX2ZyZXEgPSA4NjQwMDAwMDAKTFYzX3ZvbHQgPSAxMzUwCkxWNF9mcmVx ID0gNzIwMDAwMDAwCkxWNF92b2x0ID0gMTI1MApMVjVfZnJlcSA9IDUyODAwMDAwMApMVjVfdm9s dCA9IDExNTAKTFY2X2ZyZXEgPSAzMTIwMDAwMDAKTFY2X3ZvbHQgPSAxMTAwCkxWN19mcmVxID0g MTQ0MDAwMDAwCkxWN192b2x0ID0gMTA1MAoKW2Jvb3RfZGlzcF0Kb3V0cHV0X3R5cGUgPSAzCm91 dHB1dF9tb2RlID0gNAphdXRvX2hwZCA9IDEKCg== ------=_Part_20226_971071809.1407352669442 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 ------=_Part_20226_971071809.1407352669442-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 19:20:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 19:20: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 1XF6lP-00014Q-H5; Wed, 06 Aug 2014 19:20:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF6lO-00014B-Rz for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 19:20:43 +0000 Received: from [85.158.137.68:13372] by server-9.bemta-3.messagelabs.com id C7/2B-30790-A0082E35; Wed, 06 Aug 2014 19:20:42 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-7.tower-31.messagelabs.com!1407352840!12267480!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12695 invoked from network); 6 Aug 2014 19:20:40 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-7.tower-31.messagelabs.com with SMTP; 6 Aug 2014 19:20:40 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d58 with ME id bXLf1o01u1EBZFu03XLfSX; Wed, 06 Aug 2014 21:20:39 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 21:20:39 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 21:20:39 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> In-Reply-To: <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0935173248711747119==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0935173248711747119== Content-Type: multipart/alternative; boundary="----=_Part_20276_1011447948.1407352839920" ------=_Part_20276_1011447948.1407352839920 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ 14.526] Initializing built-in extension MIT-SCREEN-SAVER [ 14.658] (EE) open /dev/dri/card0: No such file or directory [ 14.662] (EE) open /dev/fb0: No such file or directory [ 14.662] (EE) No devices detected. [ 14.666] (EE) open /dev/dri/card0: No such file or directory [ 14.667] (EE) open /dev/fb0: No such file or directory [ 14.667] (EE) No devices detected. [ 14.667] (EE)=20 [ 14.667] (EE) no screens found(EE)=20 [ 14.668] (EE)=20 [ 14.668] (EE) Please also check the log file at "/var/log/Xorg.0.log" for = additional information. [ 14.668] (EE)=20 > Message du 06/08/14 20:14 > De : "Gilles DALMAS"=20 > A : "Thomas Leonard"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > > i have installed lxde because i don't know if there was a graphic environ= ment. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 ------=_Part_20276_1011447948.1407352839920 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

[ 14.526] Initializing built-in extension MIT-SCREEN-SAVER
[ 14.658= ] (EE) open /dev/dri/card0: No such file or directory
[ 14.662] (EE) o= pen /dev/fb0: No such file or directory
[ 14.662] (EE) No devices dete= cted.
[ 14.666] (EE) open /dev/dri/card0: No such file or directory[ 14.667] (EE) open /dev/fb0: No such file or directory
[ 14.667] (= EE) No devices detected.
[ 14.667] (EE)
[ 14.667] (EE) no screen= s found(EE)
[ 14.668] (EE)
[ 14.668] (EE) Please also check the= log file at "/var/log/Xorg.0.log" for additional information.
[ 14.66= 8] (EE)





> Message du 06/08/14 20:14
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "Thomas Leonard" <talex5@gma= il.com>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
>

> i have installed lxde because i don't know if there was a graphic e= nvironment.




> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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.xe= nproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mira= geos-devel

------=_Part_20276_1011447948.1407352839920-- --===============0935173248711747119== 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 --===============0935173248711747119==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 06 19:20:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 06 Aug 2014 19:20: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 1XF6lP-00014Q-H5; Wed, 06 Aug 2014 19:20:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XF6lO-00014B-Rz for mirageos-devel@lists.xenproject.org; Wed, 06 Aug 2014 19:20:43 +0000 Received: from [85.158.137.68:13372] by server-9.bemta-3.messagelabs.com id C7/2B-30790-A0082E35; Wed, 06 Aug 2014 19:20:42 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-7.tower-31.messagelabs.com!1407352840!12267480!1 X-Originating-IP: [80.12.242.125] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12695 invoked from network); 6 Aug 2014 19:20:40 -0000 Received: from smtp03.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.125) by server-7.tower-31.messagelabs.com with SMTP; 6 Aug 2014 19:20:40 -0000 Received: from wwinf1c13 ([10.223.79.57]) by mwinf5d58 with ME id bXLf1o01u1EBZFu03XLfSX; Wed, 06 Aug 2014 21:20:39 +0200 X-ME-Helo: wwinf1c13 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Wed, 06 Aug 2014 21:20:39 +0200 X-ME-IP: 90.15.1.71 Date: Wed, 6 Aug 2014 21:20:39 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> In-Reply-To: <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.1.71] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0935173248711747119==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============0935173248711747119== Content-Type: multipart/alternative; boundary="----=_Part_20276_1011447948.1407352839920" ------=_Part_20276_1011447948.1407352839920 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ 14.526] Initializing built-in extension MIT-SCREEN-SAVER [ 14.658] (EE) open /dev/dri/card0: No such file or directory [ 14.662] (EE) open /dev/fb0: No such file or directory [ 14.662] (EE) No devices detected. [ 14.666] (EE) open /dev/dri/card0: No such file or directory [ 14.667] (EE) open /dev/fb0: No such file or directory [ 14.667] (EE) No devices detected. [ 14.667] (EE)=20 [ 14.667] (EE) no screens found(EE)=20 [ 14.668] (EE)=20 [ 14.668] (EE) Please also check the log file at "/var/log/Xorg.0.log" for = additional information. [ 14.668] (EE)=20 > Message du 06/08/14 20:14 > De : "Gilles DALMAS"=20 > A : "Thomas Leonard"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > > i have installed lxde because i don't know if there was a graphic environ= ment. > Message du 06/08/14 17:05 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > On 6 August 2014 15:45, Gilles DALMAS wrote: > > hello, > > > > normally, with the cubie.img file of xen-arm-builder, is it possible to= have > > an graphical interface ? lxde or other ? >=20 > Did you try it? Did you get an error? >=20 >=20 > --=20 > 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 ------=_Part_20276_1011447948.1407352839920 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

[ 14.526] Initializing built-in extension MIT-SCREEN-SAVER
[ 14.658= ] (EE) open /dev/dri/card0: No such file or directory
[ 14.662] (EE) o= pen /dev/fb0: No such file or directory
[ 14.662] (EE) No devices dete= cted.
[ 14.666] (EE) open /dev/dri/card0: No such file or directory[ 14.667] (EE) open /dev/fb0: No such file or directory
[ 14.667] (= EE) No devices detected.
[ 14.667] (EE)
[ 14.667] (EE) no screen= s found(EE)
[ 14.668] (EE)
[ 14.668] (EE) Please also check the= log file at "/var/log/Xorg.0.log" for additional information.
[ 14.66= 8] (EE)





> Message du 06/08/14 20:14
> De : "Gilles DALMA= S" <gdalmas@wanadoo.fr>
> A : "Thomas Leonard" <talex5@gma= il.com>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
>

> i have installed lxde because i don't know if there was a graphic e= nvironment.




> Message du 06/08/14 17:05
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> On 6 August 2014 15:4= 5, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> > hello,> >
> > normally, with the cubie.img file of xen-arm-bu= ilder, is it possible to have
> > an graphical interface ? lxde = or other ?
>
> Did you try it? Did you get an error?
= >
>
> --
> 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.xe= nproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mira= geos-devel

------=_Part_20276_1011447948.1407352839920-- --===============0935173248711747119== 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 --===============0935173248711747119==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 08:06:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 08: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 1XFIiS-00079H-8m; Thu, 07 Aug 2014 08:06:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFIiR-00079B-7U for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 08:06:27 +0000 Received: from [85.158.143.35:30052] by server-2.bemta-4.messagelabs.com id F7/75-04525-28333E35; Thu, 07 Aug 2014 08:06:26 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-10.tower-21.messagelabs.com!1407398785!13986491!1 X-Originating-IP: [80.12.242.132] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23061 invoked from network); 7 Aug 2014 08:06:25 -0000 Received: from smtp10.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.132) by server-10.tower-21.messagelabs.com with SMTP; 7 Aug 2014 08:06:25 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d19 with ME id bk6P1o00L0xMosS03k6Psl; Thu, 07 Aug 2014 10:06:23 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 10:06:23 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 10:06:23 +0200 (CEST) From: Gilles DALMAS To: "Vincent B." , mirageos-devel@lists.xenproject.org Message-ID: <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> In-Reply-To: <53E09685.7030304@luminar.eu.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-REPLYTO: |~| Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8070852488903207128==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8070852488903207128== Content-Type: multipart/alternative; boundary="----=_Part_3575_1812206595.1407398783559" ------=_Part_3575_1812206595.1407398783559 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable it's sure that if the xen team, stay on the mainline kernel, there will nev= er a nand support. > Message du 05/08/14 10:32 > De : "Vincent B."=20 > A : mirageos-devel@lists.xenproject.org > Copie =C3=A0 :=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 04/08/2014 15:53, Gilles DALMAS wrote: > > In terms of the nand, on page: > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61 > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and thi= s is the > > 3.4.61 version of the kernel, how is it that this option does not appea= r in the > > following versions of the kernel? if I add it manually in the config fi= le, is it > > processed? > >=20 >=20 > There is no sunxi NAND support yet for the mainline linux Kernel. Work is > ongoing, though. >=20 > Vincent >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ------=_Part_3575_1812206595.1407398783559 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

it's sure that if the xen team, stay on the mainline kernel, there will = never a nand support.




> Message du 05/08/14 10:32
> De : "Vincent B." = <vb@luminar.eu.org>
> A : mirageos-devel@lists.xenproject.org=
> Copie =C3=A0 :
> Objet : Re: [MirageOS-devel] mirage os= on cubietruck nand detection
>
> On 04/08/2014 15:53, Gil= les DALMAS wrote:
> > In terms of the nand, on page:
> &= gt; https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61
> > there is for example the line CONFIG_SUNX= I_NAND_PARTITION =3D y and this is the
> > 3.4.61 version of the= kernel, how is it that this option does not appear in the
> > f= ollowing versions of the kernel? if I add it manually in the config file, i= s it
> > processed?
> >
>
> There i= s no sunxi NAND support yet for the mainline linux Kernel. Work is
>= ; ongoing, though.
>
> Vincent
>
> ______= _________________________________________
> MirageOS-devel mailing = list
> MirageOS-devel@lists.xenproject.org
> http://lists.x= enproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> ------=_Part_3575_1812206595.1407398783559-- --===============8070852488903207128== 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 --===============8070852488903207128==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 08:06:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 08: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 1XFIiS-00079H-8m; Thu, 07 Aug 2014 08:06:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFIiR-00079B-7U for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 08:06:27 +0000 Received: from [85.158.143.35:30052] by server-2.bemta-4.messagelabs.com id F7/75-04525-28333E35; Thu, 07 Aug 2014 08:06:26 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-10.tower-21.messagelabs.com!1407398785!13986491!1 X-Originating-IP: [80.12.242.132] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23061 invoked from network); 7 Aug 2014 08:06:25 -0000 Received: from smtp10.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.132) by server-10.tower-21.messagelabs.com with SMTP; 7 Aug 2014 08:06:25 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d19 with ME id bk6P1o00L0xMosS03k6Psl; Thu, 07 Aug 2014 10:06:23 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 10:06:23 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 10:06:23 +0200 (CEST) From: Gilles DALMAS To: "Vincent B." , mirageos-devel@lists.xenproject.org Message-ID: <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> In-Reply-To: <53E09685.7030304@luminar.eu.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~||~| X-WUM-REPLYTO: |~| Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8070852488903207128==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8070852488903207128== Content-Type: multipart/alternative; boundary="----=_Part_3575_1812206595.1407398783559" ------=_Part_3575_1812206595.1407398783559 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable it's sure that if the xen team, stay on the mainline kernel, there will nev= er a nand support. > Message du 05/08/14 10:32 > De : "Vincent B."=20 > A : mirageos-devel@lists.xenproject.org > Copie =C3=A0 :=20 > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 > On 04/08/2014 15:53, Gilles DALMAS wrote: > > In terms of the nand, on page: > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61 > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and thi= s is the > > 3.4.61 version of the kernel, how is it that this option does not appea= r in the > > following versions of the kernel? if I add it manually in the config fi= le, is it > > processed? > >=20 >=20 > There is no sunxi NAND support yet for the mainline linux Kernel. Work is > ongoing, though. >=20 > Vincent >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > ------=_Part_3575_1812206595.1407398783559 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

it's sure that if the xen team, stay on the mainline kernel, there will = never a nand support.




> Message du 05/08/14 10:32
> De : "Vincent B." = <vb@luminar.eu.org>
> A : mirageos-devel@lists.xenproject.org=
> Copie =C3=A0 :
> Objet : Re: [MirageOS-devel] mirage os= on cubietruck nand detection
>
> On 04/08/2014 15:53, Gil= les DALMAS wrote:
> > In terms of the nand, on page:
> &= gt; https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/ke= rnel.config.3.4.61
> > there is for example the line CONFIG_SUNX= I_NAND_PARTITION =3D y and this is the
> > 3.4.61 version of the= kernel, how is it that this option does not appear in the
> > f= ollowing versions of the kernel? if I add it manually in the config file, i= s it
> > processed?
> >
>
> There i= s no sunxi NAND support yet for the mainline linux Kernel. Work is
>= ; ongoing, though.
>
> Vincent
>
> ______= _________________________________________
> MirageOS-devel mailing = list
> MirageOS-devel@lists.xenproject.org
> http://lists.x= enproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> ------=_Part_3575_1812206595.1407398783559-- --===============8070852488903207128== 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 --===============8070852488903207128==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 08:10:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 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 1XFIm8-0007Mh-6S; Thu, 07 Aug 2014 08:10:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFIm7-0007MX-Ai for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 08:10:15 +0000 Received: from [85.158.137.68:40634] by server-3.bemta-3.messagelabs.com id FD/63-22751-66433E35; Thu, 07 Aug 2014 08:10:14 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-11.tower-31.messagelabs.com!1407399012!12350857!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1466 invoked from network); 7 Aug 2014 08:10:12 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-11.tower-31.messagelabs.com with SMTP; 7 Aug 2014 08:10:12 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d17 with ME id bkAC1o0030xMosS03kACFv; Thu, 07 Aug 2014 10:10:12 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 10:10:12 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 10:10:12 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2833861606109677924==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2833861606109677924== Content-Type: multipart/alternative; boundary="----=_Part_3701_778563129.1407399012129" ------=_Part_3701_778563129.1407399012129 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable nobody knows where this error come from? > Message du 06/08/14 10:53 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > > the guest system can only be started in this mode. there is a problems wi= th this mode ? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is= started. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > > > =C2=A0 > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS"=20 > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, > > > I have this error when i execute : > > > =C2=A0 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create:= how=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:= qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or= directory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk v= dev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk v= dev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or director= y > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device = model pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comple= te, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogr= ess: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destro= y > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2 > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > =C2=A0 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu= -system-x86 > > > =C2=A0 > >=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 > > ------=_Part_3701_778563129.1407399012129 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

nobody knows where this error come from?




> Message du 06/08/14 10:53
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> the guest system can only be started in this mode. there is a probl= ems with this mode ?
>
>
>
>
><= /p>

> Message du 06/08/14 10:21
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > my xl file :
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # Example HVM guest configuratio= n
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> > #
> > # This is a fairly minimal example of w= hat is required for an
> > # HVM guest. For a more complete guid= e see xl.cfg(5)
> >
> > # This configures an HVM rat= her than PV guest
> > builder =3D "hvm"
> >
>= ; > # Guest name
> > name =3D "Xp"
> >
> = > # 128-bit UUID for the domain as a hexadecimal number.
> > = # Use "uuidgen" to generate one if required.
> > # The default b= ehavior is to generate a new UUID each time the guest is started.
>= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> &= gt; #viridian =3D 1
> >
> > # Initial memory allocat= ion (MB)
> > memory =3D 512
> >
> > # Max= imum memory (MB)
> > # If this is greater than `memory' then the= slack will start ballooned
> > # (this assumes guest kernel sup= port for ballooning)
> > #maxmem =3D 512
> >
&g= t; > # Number of VCPUS
> > vcpus =3D 2
> >
&= gt; > # Network devices
> > # A list of 'vifspec' entries as = described in
> > # docs/misc/xl-network-configuration.markdown> > vif =3D [ 'bridge=3Dbr0' ]
> >
> > # D= isk Devices
> > # A list of `diskspec' entries as described in> > # docs/misc/xl-disk-configuration.txt
> > disk =3D= [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D 1=
> > #vnc =3D 1
> >
> >

> > =C2=A0

> Message du 06/08/14 10:03
> > > De : "Gi= lles DALMAS" <gdalmas@wanadoo.fr>
> > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Copie =C3=A0 :
> > > Objet : [Mira= geOS-devel] error when i create hvm guest
> > >
> &g= t; >

> > > hello,

> > > I have this error when i execute :

> > > =C2=A0

> > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf=
> > Parsing config from /etc/xen/xl.conf
> > libxl: = debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil= ) callback=3D(nil) poller=3D0x32578
> > libxl: verbose: libxl_cr= eate.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, us= e qemu-xen-traditional instead: No such file or directory
> > li= bxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3D= xvda spec.backend=3Dunknown
> > libxl: error: libxl_device.c:265= :libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/= guest-linux-1: No such file or directory
> > libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
> > libxl: error: libxl.c:1421:libx= l__destroy_domid: libxl__destroy_device_model failed for 9
> > l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, r= c=3D-3
> > libxl: debug: libxl_create.c:1356:do_domain_create: a= o 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
> > libxl: d= ebug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> = > xc: debug: hypercall buffer: total allocations:26 total releases:26> > xc: debug: hypercall buffer: current allocations:0 maximum all= ocations:2
> > xc: debug: hypercall buffer: cache current size:2=
> > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > =C2=A0

> > > i have a cubietruck arm and i have installed qemu-system-= arm and qemu-system-x86

> > > =C2=A0


> >
> >
> > ___________________________= ____________________
> > MirageOS-devel mailing list
> &= gt; MirageOS-devel@l= ists.xenproject.org
> > http://lists.xenproject.org/cgi= -bin/mailman/listinfo/mirageos-devel
> >
> >
_______________________________________________
>= > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenpro= ject.org
> > http://lists.xenproject.org/c= gi-bin/mailman/listinfo/mirageos-devel
> >
------=_Part_3701_778563129.1407399012129-- --===============2833861606109677924== 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 --===============2833861606109677924==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 08:10:18 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 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 1XFIm8-0007Mh-6S; Thu, 07 Aug 2014 08:10:16 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFIm7-0007MX-Ai for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 08:10:15 +0000 Received: from [85.158.137.68:40634] by server-3.bemta-3.messagelabs.com id FD/63-22751-66433E35; Thu, 07 Aug 2014 08:10:14 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-11.tower-31.messagelabs.com!1407399012!12350857!1 X-Originating-IP: [80.12.242.131] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1466 invoked from network); 7 Aug 2014 08:10:12 -0000 Received: from smtp09.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.131) by server-11.tower-31.messagelabs.com with SMTP; 7 Aug 2014 08:10:12 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d17 with ME id bkAC1o0030xMosS03kACFv; Thu, 07 Aug 2014 10:10:12 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 10:10:12 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 10:10:12 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2833861606109677924==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2833861606109677924== Content-Type: multipart/alternative; boundary="----=_Part_3701_778563129.1407399012129" ------=_Part_3701_778563129.1407399012129 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable nobody knows where this error come from? > Message du 06/08/14 10:53 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > -anil > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: >=20 > > the guest system can only be started in this mode. there is a problems wi= th this mode ? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:21 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > >=20 > > > > my xl file : > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # Example HVM guest configuration > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > # > > # This is a fairly minimal example of what is required for an > > # HVM guest. For a more complete guide see xl.cfg(5) > >=20 > > # This configures an HVM rather than PV guest > > builder =3D "hvm" > >=20 > > # Guest name > > name =3D "Xp" > >=20 > > # 128-bit UUID for the domain as a hexadecimal number. > > # Use "uuidgen" to generate one if required. > > # The default behavior is to generate a new UUID each time the guest is= started. > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > >=20 > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > # enlightenment interfaces. Turning this on can improve Windows guest > > # performance and is therefore recommended > > #viridian =3D 1 > >=20 > > # Initial memory allocation (MB) > > memory =3D 512 > >=20 > > # Maximum memory (MB) > > # If this is greater than `memory' then the slack will start ballooned > > # (this assumes guest kernel support for ballooning) > > #maxmem =3D 512 > >=20 > > # Number of VCPUS > > vcpus =3D 2 > >=20 > > # Network devices > > # A list of 'vifspec' entries as described in > > # docs/misc/xl-network-configuration.markdown > > vif =3D [ 'bridge=3Dbr0' ] > >=20 > > # Disk Devices > > # A list of `diskspec' entries as described in > > # docs/misc/xl-disk-configuration.txt > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > >=20 > > # Guest VGA console configuration, either SDL or VNC > > sdl =3D 1 > > #vnc =3D 1 > >=20 > > > > =C2=A0 > Message du 06/08/14 10:03 > > > De : "Gilles DALMAS"=20 > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > Copie =C3=A0 :=20 > > > Objet : [MirageOS-devel] error when i create hvm guest > > >=20 > > > > > > hello, > > > I have this error when i execute : > > > =C2=A0 > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > Parsing config from /etc/xen/xl.conf > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create:= how=3D(nil) callback=3D(nil) poller=3D0x32578 > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault:= qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or= directory > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk v= dev=3Dxvda spec.backend=3Dunknown > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk v= dev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or director= y > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device = model pid in /local/domain/9/image/device-model-pid > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_= model failed for 9 > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comple= te, rc=3D-3 > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogr= ess: poller=3D0x32578, flags=3Dic > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destro= y > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:= 2 > > xc: debug: hypercall buffer: cache current size:2 > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > =C2=A0 > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu= -system-x86 > > > =C2=A0 > >=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 > > ------=_Part_3701_778563129.1407399012129 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

nobody knows where this error come from?




> Message du 06/08/14 10:53
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>
>= ;

> the guest system can only be started in this mode. there is a probl= ems with this mode ?
>
>
>
>
><= /p>

> Message du 06/08/14 10:21
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > my xl file :
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # Example HVM guest configuratio= n
> > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
> > #
> > # This is a fairly minimal example of w= hat is required for an
> > # HVM guest. For a more complete guid= e see xl.cfg(5)
> >
> > # This configures an HVM rat= her than PV guest
> > builder =3D "hvm"
> >
>= ; > # Guest name
> > name =3D "Xp"
> >
> = > # 128-bit UUID for the domain as a hexadecimal number.
> > = # Use "uuidgen" to generate one if required.
> > # The default b= ehavior is to generate a new UUID each time the guest is started.
>= > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> &= gt; #viridian =3D 1
> >
> > # Initial memory allocat= ion (MB)
> > memory =3D 512
> >
> > # Max= imum memory (MB)
> > # If this is greater than `memory' then the= slack will start ballooned
> > # (this assumes guest kernel sup= port for ballooning)
> > #maxmem =3D 512
> >
&g= t; > # Number of VCPUS
> > vcpus =3D 2
> >
&= gt; > # Network devices
> > # A list of 'vifspec' entries as = described in
> > # docs/misc/xl-network-configuration.markdown> > vif =3D [ 'bridge=3Dbr0' ]
> >
> > # D= isk Devices
> > # A list of `diskspec' entries as described in> > # docs/misc/xl-disk-configuration.txt
> > disk =3D= [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D 1=
> > #vnc =3D 1
> >
> >

> > =C2=A0

> Message du 06/08/14 10:03
> > > De : "Gi= lles DALMAS" <gdalmas@wanadoo.fr>
> > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Copie =C3=A0 :
> > > Objet : [Mira= geOS-devel] error when i create hvm guest
> > >
> &g= t; >

> > > hello,

> > > I have this error when i execute :

> > > =C2=A0

> > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf=
> > Parsing config from /etc/xen/xl.conf
> > libxl: = debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil= ) callback=3D(nil) poller=3D0x32578
> > libxl: verbose: libxl_cr= eate.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, us= e qemu-xen-traditional instead: No such file or directory
> > li= bxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3D= xvda spec.backend=3Dunknown
> > libxl: error: libxl_device.c:265= :libxl__device_disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/= guest-linux-1: No such file or directory
> > libxl: error: libxl= _dm.c:1467:kill_device_model: unable to find device model pid in /local/dom= ain/9/image/device-model-pid
> > libxl: error: libxl.c:1421:libx= l__destroy_domid: libxl__destroy_device_model failed for 9
> > l= ibxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, r= c=3D-3
> > libxl: debug: libxl_create.c:1356:do_domain_create: a= o 0x31f00: inprogress: poller=3D0x32578, flags=3Dic
> > libxl: d= ebug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> = > xc: debug: hypercall buffer: total allocations:26 total releases:26> > xc: debug: hypercall buffer: current allocations:0 maximum all= ocations:2
> > xc: debug: hypercall buffer: cache current size:2=
> > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > =C2=A0

> > > i have a cubietruck arm and i have installed qemu-system-= arm and qemu-system-x86

> > > =C2=A0


> >
> >
> > ___________________________= ____________________
> > MirageOS-devel mailing list
> &= gt; MirageOS-devel@l= ists.xenproject.org
> > http://lists.xenproject.org/cgi= -bin/mailman/listinfo/mirageos-devel
> >
> >
_______________________________________________
>= > MirageOS-devel mailing list
> > MirageOS-devel@lists.xenpro= ject.org
> > http://lists.xenproject.org/c= gi-bin/mailman/listinfo/mirageos-devel
> >
------=_Part_3701_778563129.1407399012129-- --===============2833861606109677924== 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 --===============2833861606109677924==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 08:29:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 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 1XFJ4f-00008H-QG; Thu, 07 Aug 2014 08:29:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFJ4d-000089-S8 for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 08:29:23 +0000 Received: from [85.158.139.211:55714] by server-9.bemta-5.messagelabs.com id DF/69-20744-3E833E35; Thu, 07 Aug 2014 08:29:23 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1407400161!12344297!1 X-Originating-IP: [209.85.218.45] 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 24569 invoked from network); 7 Aug 2014 08:29:22 -0000 Received: from mail-oi0-f45.google.com (HELO mail-oi0-f45.google.com) (209.85.218.45) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Aug 2014 08:29:22 -0000 Received: by mail-oi0-f45.google.com with SMTP id e131so2450685oig.32 for ; Thu, 07 Aug 2014 01:29:21 -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=yvtAafWqPt1mrW5QIctQRMGN0Nj5NH9YpLGuxfIftr4=; b=BmZLGWdo6zL0kkmtId34W2/mYCx404St186R3dbv1Cv3856TdILn0Go4mFbEgz4AHp Hw9IM32/yNU3BcCvGGKZgiSZkgXKbLZQivbSpgrdbQk675Z7o0joY76P9RtrxOxeYHKI wP1emJgIp3vn1jKTKOUbiGkE19Sn+zuUCMchjRc/0JAygyz789OrxCWkHzgTmgFhy2F1 wNbJKvOfHTnt00ajGCvzm3D6qzBgeS6lU5PofEBBO863fhSyEQol9Kp1NvFW3lBFuLqM 9niGAbzPjz2TRc6oPyUKFlmHbXzaPkOELByNLj9vWi9B8lgpxrrUa/0yMOtVN7v9w8Ij UJXg== MIME-Version: 1.0 X-Received: by 10.60.220.169 with SMTP id px9mr21107868oec.67.1407400160929; Thu, 07 Aug 2014 01:29:20 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 7 Aug 2014 01:29:20 -0700 (PDT) In-Reply-To: <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> Date: Thu, 7 Aug 2014 09:29:20 +0100 Message-ID: From: Thomas Leonard To: Gilles DALMAS Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 Q3ViaWVleiBzYXlzIGl0IHN1cHBvcnRzIGdyYXBoaWNzIChhbmQgVVNCKSwgc28gSSBzdWdnZXN0 IGNoZWNraW5nCndoYXQga2VybmVsIG9wdGlvbnMgdGhleSB1c2VkLgoKICBodHRwOi8vd3d3LmN1 YmllZXouY29tLwoKKHBhdGNoZXMgdG8gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS94ZW4tYXJt LWJ1aWxkZXIgd2VsY29tZSkKCk9uIDYgQXVndXN0IDIwMTQgMjA6MjAsIEdpbGxlcyBEQUxNQVMg PGdkYWxtYXNAd2FuYWRvby5mcj4gd3JvdGU6Cj4gWyAxNC41MjZdIEluaXRpYWxpemluZyBidWls dC1pbiBleHRlbnNpb24gTUlULVNDUkVFTi1TQVZFUgo+IFsgMTQuNjU4XSAoRUUpIG9wZW4gL2Rl di9kcmkvY2FyZDA6IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkKPiBbIDE0LjY2Ml0gKEVFKSBv cGVuIC9kZXYvZmIwOiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Cj4gWyAxNC42NjJdIChFRSkg Tm8gZGV2aWNlcyBkZXRlY3RlZC4KPiBbIDE0LjY2Nl0gKEVFKSBvcGVuIC9kZXYvZHJpL2NhcmQw OiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Cj4gWyAxNC42NjddIChFRSkgb3BlbiAvZGV2L2Zi MDogTm8gc3VjaCBmaWxlIG9yIGRpcmVjdG9yeQo+IFsgMTQuNjY3XSAoRUUpIE5vIGRldmljZXMg ZGV0ZWN0ZWQuCj4gWyAxNC42NjddIChFRSkKPiBbIDE0LjY2N10gKEVFKSBubyBzY3JlZW5zIGZv dW5kKEVFKQo+IFsgMTQuNjY4XSAoRUUpCj4gWyAxNC42NjhdIChFRSkgUGxlYXNlIGFsc28gY2hl Y2sgdGhlIGxvZyBmaWxlIGF0ICIvdmFyL2xvZy9Yb3JnLjAubG9nIiBmb3IKPiBhZGRpdGlvbmFs IGluZm9ybWF0aW9uLgo+IFsgMTQuNjY4XSAoRUUpCj4KPgo+Cj4KPgo+PiBNZXNzYWdlIGR1IDA2 LzA4LzE0IDIwOjE0Cj4+IERlIDogIkdpbGxlcyBEQUxNQVMiIDxnZGFsbWFzQHdhbmFkb28uZnI+ Cj4+IEEgOiAiVGhvbWFzIExlb25hcmQiIDx0YWxleDVAZ21haWwuY29tPgo+PiBDb3BpZSDDoCA6 ICJtaXJhZ2Vvcy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZyIKPj4gPG1pcmFnZW9zLWRldmVs QGxpc3RzLnhlbnByb2plY3Qub3JnPgo+PiBPYmpldCA6IFJlOiBbTWlyYWdlT1MtZGV2ZWxdIHgg aW50ZXJmYWNlIG9uIGN1YmlldHJ1Y2sKPj4KPj4KPgo+PiBpIGhhdmUgaW5zdGFsbGVkIGx4ZGUg YmVjYXVzZSBpIGRvbid0IGtub3cgaWYgdGhlcmUgd2FzIGEgZ3JhcGhpYwo+PiBlbnZpcm9ubWVu dC4KPgo+Cj4KPgo+PiBNZXNzYWdlIGR1IDA2LzA4LzE0IDE3OjA1Cj4+IERlIDogIlRob21hcyBM ZW9uYXJkIiA8dGFsZXg1QGdtYWlsLmNvbT4KPj4gQSA6ICJHaWxsZXMgREFMTUFTIiA8Z2RhbG1h c0B3YW5hZG9vLmZyPgo+PiBDb3BpZSDDoCA6ICJtaXJhZ2Vvcy1kZXZlbEBsaXN0cy54ZW5wcm9q ZWN0Lm9yZyIKPj4gPG1pcmFnZW9zLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnPgo+PiBPYmpl dCA6IFJlOiBbTWlyYWdlT1MtZGV2ZWxdIHggaW50ZXJmYWNlIG9uIGN1YmlldHJ1Y2sKPj4KPj4g T24gNiBBdWd1c3QgMjAxNCAxNTo0NSwgR2lsbGVzIERBTE1BUyA8Z2RhbG1hc0B3YW5hZG9vLmZy PiB3cm90ZToKPj4gPiBoZWxsbywKPj4gPgo+PiA+IG5vcm1hbGx5LCB3aXRoIHRoZSBjdWJpZS5p bWcgZmlsZSBvZiB4ZW4tYXJtLWJ1aWxkZXIsIGlzIGl0IHBvc3NpYmxlIHRvCj4+ID4gaGF2ZQo+ PiA+IGFuIGdyYXBoaWNhbCBpbnRlcmZhY2UgPyBseGRlIG9yIG90aGVyID8KPj4KPj4gRGlkIHlv dSB0cnkgaXQ/IERpZCB5b3UgZ2V0IGFuIGVycm9yPwo+Pgo+Pgo+PiAtLQo+PiBEciBUaG9tYXMg TGVvbmFyZCBodHRwOi8vMGluc3RhbGwubmV0Lwo+PiBHUEc6IDkyNDIgOTgwNyBDOTg1IDNDMDcg NDRBNiA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKPj4gR1BHOiBEQTk4IDI1QUUgQ0FEMCA4OTc1 IDdDREEgQkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCj4+Cj4KPgo+Cj4KPiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IE1pcmFnZU9TLWRldmVsIG1haWxp bmcgbGlzdAo+IE1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCj4gaHR0cDovL2xp c3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZl bAo+CgoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAgICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8K R1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYgIDhCOUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpH UEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAgQkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1k ZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0 cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vv cy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 08:29:27 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 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 1XFJ4f-00008H-QG; Thu, 07 Aug 2014 08:29:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFJ4d-000089-S8 for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 08:29:23 +0000 Received: from [85.158.139.211:55714] by server-9.bemta-5.messagelabs.com id DF/69-20744-3E833E35; Thu, 07 Aug 2014 08:29:23 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1407400161!12344297!1 X-Originating-IP: [209.85.218.45] 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 24569 invoked from network); 7 Aug 2014 08:29:22 -0000 Received: from mail-oi0-f45.google.com (HELO mail-oi0-f45.google.com) (209.85.218.45) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 7 Aug 2014 08:29:22 -0000 Received: by mail-oi0-f45.google.com with SMTP id e131so2450685oig.32 for ; Thu, 07 Aug 2014 01:29:21 -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=yvtAafWqPt1mrW5QIctQRMGN0Nj5NH9YpLGuxfIftr4=; b=BmZLGWdo6zL0kkmtId34W2/mYCx404St186R3dbv1Cv3856TdILn0Go4mFbEgz4AHp Hw9IM32/yNU3BcCvGGKZgiSZkgXKbLZQivbSpgrdbQk675Z7o0joY76P9RtrxOxeYHKI wP1emJgIp3vn1jKTKOUbiGkE19Sn+zuUCMchjRc/0JAygyz789OrxCWkHzgTmgFhy2F1 wNbJKvOfHTnt00ajGCvzm3D6qzBgeS6lU5PofEBBO863fhSyEQol9Kp1NvFW3lBFuLqM 9niGAbzPjz2TRc6oPyUKFlmHbXzaPkOELByNLj9vWi9B8lgpxrrUa/0yMOtVN7v9w8Ij UJXg== MIME-Version: 1.0 X-Received: by 10.60.220.169 with SMTP id px9mr21107868oec.67.1407400160929; Thu, 07 Aug 2014 01:29:20 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 7 Aug 2014 01:29:20 -0700 (PDT) In-Reply-To: <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> Date: Thu, 7 Aug 2014 09:29:20 +0100 Message-ID: From: Thomas Leonard To: Gilles DALMAS Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 Q3ViaWVleiBzYXlzIGl0IHN1cHBvcnRzIGdyYXBoaWNzIChhbmQgVVNCKSwgc28gSSBzdWdnZXN0 IGNoZWNraW5nCndoYXQga2VybmVsIG9wdGlvbnMgdGhleSB1c2VkLgoKICBodHRwOi8vd3d3LmN1 YmllZXouY29tLwoKKHBhdGNoZXMgdG8gaHR0cHM6Ly9naXRodWIuY29tL21pcmFnZS94ZW4tYXJt LWJ1aWxkZXIgd2VsY29tZSkKCk9uIDYgQXVndXN0IDIwMTQgMjA6MjAsIEdpbGxlcyBEQUxNQVMg PGdkYWxtYXNAd2FuYWRvby5mcj4gd3JvdGU6Cj4gWyAxNC41MjZdIEluaXRpYWxpemluZyBidWls dC1pbiBleHRlbnNpb24gTUlULVNDUkVFTi1TQVZFUgo+IFsgMTQuNjU4XSAoRUUpIG9wZW4gL2Rl di9kcmkvY2FyZDA6IE5vIHN1Y2ggZmlsZSBvciBkaXJlY3RvcnkKPiBbIDE0LjY2Ml0gKEVFKSBv cGVuIC9kZXYvZmIwOiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Cj4gWyAxNC42NjJdIChFRSkg Tm8gZGV2aWNlcyBkZXRlY3RlZC4KPiBbIDE0LjY2Nl0gKEVFKSBvcGVuIC9kZXYvZHJpL2NhcmQw OiBObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Cj4gWyAxNC42NjddIChFRSkgb3BlbiAvZGV2L2Zi MDogTm8gc3VjaCBmaWxlIG9yIGRpcmVjdG9yeQo+IFsgMTQuNjY3XSAoRUUpIE5vIGRldmljZXMg ZGV0ZWN0ZWQuCj4gWyAxNC42NjddIChFRSkKPiBbIDE0LjY2N10gKEVFKSBubyBzY3JlZW5zIGZv dW5kKEVFKQo+IFsgMTQuNjY4XSAoRUUpCj4gWyAxNC42NjhdIChFRSkgUGxlYXNlIGFsc28gY2hl Y2sgdGhlIGxvZyBmaWxlIGF0ICIvdmFyL2xvZy9Yb3JnLjAubG9nIiBmb3IKPiBhZGRpdGlvbmFs IGluZm9ybWF0aW9uLgo+IFsgMTQuNjY4XSAoRUUpCj4KPgo+Cj4KPgo+PiBNZXNzYWdlIGR1IDA2 LzA4LzE0IDIwOjE0Cj4+IERlIDogIkdpbGxlcyBEQUxNQVMiIDxnZGFsbWFzQHdhbmFkb28uZnI+ Cj4+IEEgOiAiVGhvbWFzIExlb25hcmQiIDx0YWxleDVAZ21haWwuY29tPgo+PiBDb3BpZSDDoCA6 ICJtaXJhZ2Vvcy1kZXZlbEBsaXN0cy54ZW5wcm9qZWN0Lm9yZyIKPj4gPG1pcmFnZW9zLWRldmVs QGxpc3RzLnhlbnByb2plY3Qub3JnPgo+PiBPYmpldCA6IFJlOiBbTWlyYWdlT1MtZGV2ZWxdIHgg aW50ZXJmYWNlIG9uIGN1YmlldHJ1Y2sKPj4KPj4KPgo+PiBpIGhhdmUgaW5zdGFsbGVkIGx4ZGUg YmVjYXVzZSBpIGRvbid0IGtub3cgaWYgdGhlcmUgd2FzIGEgZ3JhcGhpYwo+PiBlbnZpcm9ubWVu dC4KPgo+Cj4KPgo+PiBNZXNzYWdlIGR1IDA2LzA4LzE0IDE3OjA1Cj4+IERlIDogIlRob21hcyBM ZW9uYXJkIiA8dGFsZXg1QGdtYWlsLmNvbT4KPj4gQSA6ICJHaWxsZXMgREFMTUFTIiA8Z2RhbG1h c0B3YW5hZG9vLmZyPgo+PiBDb3BpZSDDoCA6ICJtaXJhZ2Vvcy1kZXZlbEBsaXN0cy54ZW5wcm9q ZWN0Lm9yZyIKPj4gPG1pcmFnZW9zLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnPgo+PiBPYmpl dCA6IFJlOiBbTWlyYWdlT1MtZGV2ZWxdIHggaW50ZXJmYWNlIG9uIGN1YmlldHJ1Y2sKPj4KPj4g T24gNiBBdWd1c3QgMjAxNCAxNTo0NSwgR2lsbGVzIERBTE1BUyA8Z2RhbG1hc0B3YW5hZG9vLmZy PiB3cm90ZToKPj4gPiBoZWxsbywKPj4gPgo+PiA+IG5vcm1hbGx5LCB3aXRoIHRoZSBjdWJpZS5p bWcgZmlsZSBvZiB4ZW4tYXJtLWJ1aWxkZXIsIGlzIGl0IHBvc3NpYmxlIHRvCj4+ID4gaGF2ZQo+ PiA+IGFuIGdyYXBoaWNhbCBpbnRlcmZhY2UgPyBseGRlIG9yIG90aGVyID8KPj4KPj4gRGlkIHlv dSB0cnkgaXQ/IERpZCB5b3UgZ2V0IGFuIGVycm9yPwo+Pgo+Pgo+PiAtLQo+PiBEciBUaG9tYXMg TGVvbmFyZCBodHRwOi8vMGluc3RhbGwubmV0Lwo+PiBHUEc6IDkyNDIgOTgwNyBDOTg1IDNDMDcg NDRBNiA4QjlBIEFFMDcgODI4MCA1OUE1IDNDQzEKPj4gR1BHOiBEQTk4IDI1QUUgQ0FEMCA4OTc1 IDdDREEgQkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCj4+Cj4KPgo+Cj4KPiBfX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IE1pcmFnZU9TLWRldmVsIG1haWxp bmcgbGlzdAo+IE1pcmFnZU9TLWRldmVsQGxpc3RzLnhlbnByb2plY3Qub3JnCj4gaHR0cDovL2xp c3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZl bAo+CgoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAgICAgICAgaHR0cDovLzBpbnN0YWxsLm5ldC8K R1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYgIDhCOUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpH UEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAgQkQ4RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpNaXJhZ2VPUy1k ZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0 cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby9taXJhZ2Vv cy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 09:59:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 09:59: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 1XFKTR-0002sk-2d; Thu, 07 Aug 2014 09:59:05 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFKTM-0002rU-J9 for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 09:59:00 +0000 Received: from [193.109.254.147:26393] by server-12.bemta-14.messagelabs.com id 39/5C-23840-3ED43E35; Thu, 07 Aug 2014 09:58:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1407405538!14189720!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19901 invoked from network); 7 Aug 2014 09:58:58 -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; 7 Aug 2014 09:58:58 -0000 Received: (qmail 32189 invoked by uid 634); 7 Aug 2014 09:58:57 -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; Thu, 07 Aug 2014 10:58:54 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> Date: Thu, 7 Aug 2014 10:58:53 +0100 Message-Id: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> To: Gilles DALMAS 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] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8408953583113633422==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8408953583113633422== Content-Type: multipart/alternative; boundary="Apple-Mail=_9DB1A328-A76E-4006-99B6-67C957542078" --Apple-Mail=_9DB1A328-A76E-4006-99B6-67C957542078 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Gilles, It looks like you are trying to install an x86_64 virtual machine image = onto an ARM Xen host. This will not work... -anil On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: > nobody knows where this error come from? >=20 >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:53 > > De : "Anil Madhavapeddy" > > A : "Gilles DALMAS" > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > > This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode. Are you trying to boot an x86 guest on = ARM? >=20 > > > -anil >=20 > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > >=20 > > > > the guest system can only be started in this mode. there is a = problems with this mode ? > >=20 > >=20 > >=20 > >=20 > > >=20 > > Message du 06/08/14 10:21 > > > De : "Anil Madhavapeddy" > > > A : "Gilles DALMAS" > > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > > Why are you trying to create an HVM guest on Xen/ARM? You should just = be using the default PV mode on ARM to launch guests. >=20 > > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > > >=20 > > > > > > my xl file : > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # Example HVM guest configuration > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # > > > # This is a fairly minimal example of what is required for an > > > # HVM guest. For a more complete guide see xl.cfg(5) > > >=20 > > > # This configures an HVM rather than PV guest > > > builder =3D "hvm" > > >=20 > > > # Guest name > > > name =3D "Xp" > > >=20 > > > # 128-bit UUID for the domain as a hexadecimal number. > > > # Use "uuidgen" to generate one if required. > > > # The default behavior is to generate a new UUID each time the = guest is started. > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > >=20 > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > # enlightenment interfaces. Turning this on can improve Windows = guest > > > # performance and is therefore recommended > > > #viridian =3D 1 > > >=20 > > > # Initial memory allocation (MB) > > > memory =3D 512 > > >=20 > > > # Maximum memory (MB) > > > # If this is greater than `memory' then the slack will start = ballooned > > > # (this assumes guest kernel support for ballooning) > > > #maxmem =3D 512 > > >=20 > > > # Number of VCPUS > > > vcpus =3D 2 > > >=20 > > > # Network devices > > > # A list of 'vifspec' entries as described in > > > # docs/misc/xl-network-configuration.markdown > > > vif =3D [ 'bridge=3Dbr0' ] > > >=20 > > > # Disk Devices > > > # A list of `diskspec' entries as described in > > > # docs/misc/xl-disk-configuration.txt > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > >=20 > > > # Guest VGA console configuration, either SDL or VNC > > > sdl =3D 1 > > > #vnc =3D 1 > > >=20 > > > >=20 > > > =20 >=20 > > Message du 06/08/14 10:03 > > > > De : "Gilles DALMAS" > > > > A : "mirageos-devel@lists.xenproject.org" = > > > > Copie =E0 :=20 > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > > > > > hello, >=20 > > > > I have this error when i execute : >=20 > > > > =20 >=20 > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > Parsing config from /etc/xen/xl.conf > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: = create: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or directory > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: = Disk vdev=3Dxvda spec.backend=3Dunknown > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: = Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or = directory > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find = device model pid in /local/domain/9/image/device-model-pid > > > libxl: error: libxl.c:1421:libxl__destroy_domid: = libxl__destroy_device_model failed for 9 > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: = complete, rc=3D-3 > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: = inprogress: poller=3D0x32578, flags=3Dic > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: = destroy > > > xc: debug: hypercall buffer: total allocations:26 total = releases:26 > > > xc: debug: hypercall buffer: current allocations:0 maximum = allocations:2 > > > xc: debug: hypercall buffer: cache current size:2 > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > > > =20 >=20 > > > > i have a cubietruck arm and i have installed qemu-system-arm and = qemu-system-x86 >=20 > > > > =20 >=20 >=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=_9DB1A328-A76E-4006-99B6-67C957542078 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Gilles,

It looks like you are trying to install an = x86_64 virtual machine image onto an ARM Xen host.  This will not = work...

-anil

On 7 Aug = 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

nobody knows where this error come from?


=

> Message du 06/08/14 10:53
> De : "Anil = Madhavapeddy" <anil@recoil.org>
> A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] error when i = create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode.  Are you trying to boot an x86 guest = on ARM?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
>
>

> the guest system can only be started in this mode. there is = a problems with this mode ?
>
>
>
> =
>

> Message du 06/08/14 10:21
> > De : = "Anil Madhavapeddy" <anil@recoil.org>
> > A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > Objet : Re: [MirageOS-devel] error = when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM?  You = should just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> >
> >

> > my xl file :
> > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # = Example HVM guest configuration
> > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > = #
> > # This is a fairly minimal example of what is required = for an
> > # HVM guest. For a more complete guide see = xl.cfg(5)
> >
> > # This configures an HVM rather = than PV guest
> > builder =3D "hvm"
> >
> > = # Guest name
> > name =3D "Xp"
> >
> > # = 128-bit UUID for the domain as a hexadecimal number.
> > # Use = "uuidgen" to generate one if required.
> > # The default = behavior is to generate a new UUID each time the guest is = started.
> > #uuid =3D = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # = Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # = enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> = > #viridian =3D 1
> >
> > # Initial memory = allocation (MB)
> > memory =3D 512
> >
> > # = Maximum memory (MB)
> > # If this is greater than `memory' then = the slack will start ballooned
> > # (this assumes guest kernel = support for ballooning)
> > #maxmem =3D 512
> > =
> > # Number of VCPUS
> > vcpus =3D 2
> > =
> > # Network devices
> > # A list of 'vifspec' = entries as described in
> > # = docs/misc/xl-network-configuration.markdown
> > vif =3D [ = 'bridge=3Dbr0' ]
> >
> > # Disk Devices
> > = # A list of `diskspec' entries as described in
> > # = docs/misc/xl-disk-configuration.txt
> > disk =3D [ = '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D = 1
> > #vnc =3D 1
> >
> >

> > =  

> Message du 06/08/14 10:03
> > > De = : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > > A : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > > Copie =E0 :
> > > = Objet : [MirageOS-devel] error when i create hvm guest
> > > =
> > >

> > > hello,

> > > I have this error when i = execute :

> > >  

> > > = mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
> > = Parsing config from /etc/xen/xl.conf
> > libxl: debug: = libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil) = callback=3D(nil) poller=3D0x32578
> > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or = directory
> > libxl: debug: = libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda = spec.backend=3Dunknown
> > libxl: error: = libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda = failed to stat: /dev/vg0/guest-linux-1: No such file or = directory
> > libxl: error: libxl_dm.c:1467:kill_device_model: = unable to find device model pid in = /local/domain/9/image/device-model-pid
> > libxl: error: = libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed = for 9
> > libxl: debug: libxl_event.c:1591:libxl__ao_complete: = ao 0x31f00: complete, rc=3D-3
> > libxl: debug: = libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: = poller=3D0x32578, flags=3Dic
> > libxl: debug: = libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> > = xc: debug: hypercall buffer: total allocations:26 total = releases:26
> > xc: debug: hypercall buffer: current = allocations:0 maximum allocations:2
> > xc: debug: hypercall = buffer: cache current size:2
> > xc: debug: hypercall buffer: = cache hits:22 misses:2 toobig:2

> > >  

> = > > i have a cubietruck arm and i have installed qemu-system-arm = and qemu-system-x86

> > >  


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

= --Apple-Mail=_9DB1A328-A76E-4006-99B6-67C957542078-- --===============8408953583113633422== 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 --===============8408953583113633422==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 09:59:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 09:59: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 1XFKTR-0002sk-2d; Thu, 07 Aug 2014 09:59:05 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFKTM-0002rU-J9 for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 09:59:00 +0000 Received: from [193.109.254.147:26393] by server-12.bemta-14.messagelabs.com id 39/5C-23840-3ED43E35; Thu, 07 Aug 2014 09:58:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1407405538!14189720!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19901 invoked from network); 7 Aug 2014 09:58:58 -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; 7 Aug 2014 09:58:58 -0000 Received: (qmail 32189 invoked by uid 634); 7 Aug 2014 09:58:57 -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; Thu, 07 Aug 2014 10:58:54 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> Date: Thu, 7 Aug 2014 10:58:53 +0100 Message-Id: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> To: Gilles DALMAS 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] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8408953583113633422==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8408953583113633422== Content-Type: multipart/alternative; boundary="Apple-Mail=_9DB1A328-A76E-4006-99B6-67C957542078" --Apple-Mail=_9DB1A328-A76E-4006-99B6-67C957542078 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Gilles, It looks like you are trying to install an x86_64 virtual machine image = onto an ARM Xen host. This will not work... -anil On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: > nobody knows where this error come from? >=20 >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:53 > > De : "Anil Madhavapeddy" > > A : "Gilles DALMAS" > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > > This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode. Are you trying to boot an x86 guest on = ARM? >=20 > > > -anil >=20 > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > >=20 > > > > the guest system can only be started in this mode. there is a = problems with this mode ? > >=20 > >=20 > >=20 > >=20 > > >=20 > > Message du 06/08/14 10:21 > > > De : "Anil Madhavapeddy" > > > A : "Gilles DALMAS" > > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > > Why are you trying to create an HVM guest on Xen/ARM? You should just = be using the default PV mode on ARM to launch guests. >=20 > > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > > >=20 > > > > > > my xl file : > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # Example HVM guest configuration > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # > > > # This is a fairly minimal example of what is required for an > > > # HVM guest. For a more complete guide see xl.cfg(5) > > >=20 > > > # This configures an HVM rather than PV guest > > > builder =3D "hvm" > > >=20 > > > # Guest name > > > name =3D "Xp" > > >=20 > > > # 128-bit UUID for the domain as a hexadecimal number. > > > # Use "uuidgen" to generate one if required. > > > # The default behavior is to generate a new UUID each time the = guest is started. > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > >=20 > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > # enlightenment interfaces. Turning this on can improve Windows = guest > > > # performance and is therefore recommended > > > #viridian =3D 1 > > >=20 > > > # Initial memory allocation (MB) > > > memory =3D 512 > > >=20 > > > # Maximum memory (MB) > > > # If this is greater than `memory' then the slack will start = ballooned > > > # (this assumes guest kernel support for ballooning) > > > #maxmem =3D 512 > > >=20 > > > # Number of VCPUS > > > vcpus =3D 2 > > >=20 > > > # Network devices > > > # A list of 'vifspec' entries as described in > > > # docs/misc/xl-network-configuration.markdown > > > vif =3D [ 'bridge=3Dbr0' ] > > >=20 > > > # Disk Devices > > > # A list of `diskspec' entries as described in > > > # docs/misc/xl-disk-configuration.txt > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > >=20 > > > # Guest VGA console configuration, either SDL or VNC > > > sdl =3D 1 > > > #vnc =3D 1 > > >=20 > > > >=20 > > > =20 >=20 > > Message du 06/08/14 10:03 > > > > De : "Gilles DALMAS" > > > > A : "mirageos-devel@lists.xenproject.org" = > > > > Copie =E0 :=20 > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > > > > > hello, >=20 > > > > I have this error when i execute : >=20 > > > > =20 >=20 > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > Parsing config from /etc/xen/xl.conf > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: = create: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or directory > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: = Disk vdev=3Dxvda spec.backend=3Dunknown > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: = Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or = directory > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find = device model pid in /local/domain/9/image/device-model-pid > > > libxl: error: libxl.c:1421:libxl__destroy_domid: = libxl__destroy_device_model failed for 9 > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: = complete, rc=3D-3 > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: = inprogress: poller=3D0x32578, flags=3Dic > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: = destroy > > > xc: debug: hypercall buffer: total allocations:26 total = releases:26 > > > xc: debug: hypercall buffer: current allocations:0 maximum = allocations:2 > > > xc: debug: hypercall buffer: cache current size:2 > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > > > =20 >=20 > > > > i have a cubietruck arm and i have installed qemu-system-arm and = qemu-system-x86 >=20 > > > > =20 >=20 >=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=_9DB1A328-A76E-4006-99B6-67C957542078 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Gilles,

It looks like you are trying to install an = x86_64 virtual machine image onto an ARM Xen host.  This will not = work...

-anil

On 7 Aug = 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

nobody knows where this error come from?


=

> Message du 06/08/14 10:53
> De : "Anil = Madhavapeddy" <anil@recoil.org>
> A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] error when i = create hvm guest
>
>
This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode.  Are you trying to boot an x86 guest = on ARM?

>
-anil

> On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
>
>

> the guest system can only be started in this mode. there is = a problems with this mode ?
>
>
>
> =
>

> Message du 06/08/14 10:21
> > De : = "Anil Madhavapeddy" <anil@recoil.org>
> > A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > Objet : Re: [MirageOS-devel] error = when i create hvm guest
> >
> >
Why are you trying to create an HVM guest on Xen/ARM?  You = should just be using the default PV mode on ARM to launch guests.

> > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> >
> >

> > my xl file :
> > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > # = Example HVM guest configuration
> > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > = #
> > # This is a fairly minimal example of what is required = for an
> > # HVM guest. For a more complete guide see = xl.cfg(5)
> >
> > # This configures an HVM rather = than PV guest
> > builder =3D "hvm"
> >
> > = # Guest name
> > name =3D "Xp"
> >
> > # = 128-bit UUID for the domain as a hexadecimal number.
> > # Use = "uuidgen" to generate one if required.
> > # The default = behavior is to generate a new UUID each time the guest is = started.
> > #uuid =3D = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> >
> > # = Enable Microsoft Hyper-V compatibile paravirtualisation /
> > # = enlightenment interfaces. Turning this on can improve Windows = guest
> > # performance and is therefore recommended
> = > #viridian =3D 1
> >
> > # Initial memory = allocation (MB)
> > memory =3D 512
> >
> > # = Maximum memory (MB)
> > # If this is greater than `memory' then = the slack will start ballooned
> > # (this assumes guest kernel = support for ballooning)
> > #maxmem =3D 512
> > =
> > # Number of VCPUS
> > vcpus =3D 2
> > =
> > # Network devices
> > # A list of 'vifspec' = entries as described in
> > # = docs/misc/xl-network-configuration.markdown
> > vif =3D [ = 'bridge=3Dbr0' ]
> >
> > # Disk Devices
> > = # A list of `diskspec' entries as described in
> > # = docs/misc/xl-disk-configuration.txt
> > disk =3D [ = '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> >
> > # = Guest VGA console configuration, either SDL or VNC
> > sdl =3D = 1
> > #vnc =3D 1
> >
> >

> > =  

> Message du 06/08/14 10:03
> > > De = : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > > A : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > > Copie =E0 :
> > > = Objet : [MirageOS-devel] error when i create hvm guest
> > > =
> > >

> > > hello,

> > > I have this error when i = execute :

> > >  

> > > = mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
> > = Parsing config from /etc/xen/xl.conf
> > libxl: debug: = libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil) = callback=3D(nil) poller=3D0x32578
> > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or = directory
> > libxl: debug: = libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda = spec.backend=3Dunknown
> > libxl: error: = libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda = failed to stat: /dev/vg0/guest-linux-1: No such file or = directory
> > libxl: error: libxl_dm.c:1467:kill_device_model: = unable to find device model pid in = /local/domain/9/image/device-model-pid
> > libxl: error: = libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed = for 9
> > libxl: debug: libxl_event.c:1591:libxl__ao_complete: = ao 0x31f00: complete, rc=3D-3
> > libxl: debug: = libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: = poller=3D0x32578, flags=3Dic
> > libxl: debug: = libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> > = xc: debug: hypercall buffer: total allocations:26 total = releases:26
> > xc: debug: hypercall buffer: current = allocations:0 maximum allocations:2
> > xc: debug: hypercall = buffer: cache current size:2
> > xc: debug: hypercall buffer: = cache hits:22 misses:2 toobig:2

> > >  

> = > > i have a cubietruck arm and i have installed qemu-system-arm = and qemu-system-x86

> > >  


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

= --Apple-Mail=_9DB1A328-A76E-4006-99B6-67C957542078-- --===============8408953583113633422== 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 --===============8408953583113633422==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 10:00:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 10:00: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 1XFKUu-00030b-BG; Thu, 07 Aug 2014 10:00:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFKUs-00030W-Tu for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 10:00:35 +0000 Received: from [193.109.254.147:11809] by server-9.bemta-14.messagelabs.com id 1E/E9-31535-24E43E35; Thu, 07 Aug 2014 10:00:34 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1407405632!14260830!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13048 invoked from network); 7 Aug 2014 10:00:32 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-27.messagelabs.com with SMTP; 7 Aug 2014 10:00:32 -0000 Received: (qmail 11569 invoked by uid 634); 7 Aug 2014 10:00:32 -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; Thu, 07 Aug 2014 11:00:31 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> Date: Thu, 7 Aug 2014 11:00:30 +0100 Message-Id: <1255BAA1-D9B1-41DC-96BB-EA00BE63B1AA@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> To: Gilles DALMAS 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 os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3529815838950012541==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3529815838950012541== Content-Type: multipart/alternative; boundary="Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117" --Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Gilles, If you look at the mainlining page for Sunxi that I pointed you at: http://linux-sunxi.org/Linux_mainlining_effort Search for "NAND", which is a work in progress under the DMA engine. = You can get in touch with the folk doing this work to indicate your = interest and offer testing help if they do have patches against = mainline. -anil On 7 Aug 2014, at 09:06, Gilles DALMAS wrote: > it's sure that if the xen team, stay on the mainline kernel, there = will never a nand support. >=20 >=20 >=20 >=20 >=20 > > Message du 05/08/14 10:32 > > De : "Vincent B." > > A : mirageos-devel@lists.xenproject.org > > Copie =E0 :=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 04/08/2014 15:53, Gilles DALMAS wrote: > > > In terms of the nand, on page: > > > = https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kerne= l.config.3.4.61 > > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y = and this is the > > > 3.4.61 version of the kernel, how is it that this option does not = appear in the > > > following versions of the kernel? if I add it manually in the = config file, is it > > > processed? > > >=20 > >=20 > > There is no sunxi NAND support yet for the mainline linux Kernel. = Work is > > ongoing, though. > >=20 > > Vincent > >=20 > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Gilles,

If you look at the mainlining page for Sunxi = that I pointed you at:


Search for = "NAND", which is a work in progress under the DMA engine.  You can = get in touch with the folk doing this work to indicate your interest and = offer testing help if they do have patches against = mainline.

-anil

On 7 = Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

it's sure that if the xen team, stay on the mainline = kernel, there will never a nand support.




> Message du 05/08/14 10:32
> De : "Vincent = B." <vb@luminar.eu.org>
> A : = mirageos-devel@lists.x= enproject.org
> Copie =E0 :
> Objet : Re: = [MirageOS-devel] mirage os on cubietruck nand detection
>
> = On 04/08/2014 15:53, Gilles DALMAS wrote:
> > In terms of the = nand, on page:
> > https://github.com/igorpecovnik/Cubietruck-Debian= /blob/master/config/kernel.config.3.4.61
> > there is for = example the line CONFIG_SUNXI_NAND_PARTITION =3D y and this is = the
> > 3.4.61 version of the kernel, how is it that this = option does not appear in the
> > following versions of the = kernel? if I add it manually in the config file, is it
> > = processed?
> >
>
> There is no sunxi NAND support = yet for the mainline linux Kernel. Work is
> ongoing, = though.
>
> Vincent
>
> = _______________________________________________
> MirageOS-devel = mailing list
> MirageOS-devel@lists.x= enproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel=
> =
_______________________________________________
MirageOS-d= evel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117-- --===============3529815838950012541== 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 --===============3529815838950012541==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 10:00:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 10:00: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 1XFKUu-00030b-BG; Thu, 07 Aug 2014 10:00:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFKUs-00030W-Tu for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 10:00:35 +0000 Received: from [193.109.254.147:11809] by server-9.bemta-14.messagelabs.com id 1E/E9-31535-24E43E35; Thu, 07 Aug 2014 10:00:34 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1407405632!14260830!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13048 invoked from network); 7 Aug 2014 10:00:32 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-27.messagelabs.com with SMTP; 7 Aug 2014 10:00:32 -0000 Received: (qmail 11569 invoked by uid 634); 7 Aug 2014 10:00:32 -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; Thu, 07 Aug 2014 11:00:31 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> Date: Thu, 7 Aug 2014 11:00:30 +0100 Message-Id: <1255BAA1-D9B1-41DC-96BB-EA00BE63B1AA@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> To: Gilles DALMAS 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 os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3529815838950012541==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3529815838950012541== Content-Type: multipart/alternative; boundary="Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117" --Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Gilles, If you look at the mainlining page for Sunxi that I pointed you at: http://linux-sunxi.org/Linux_mainlining_effort Search for "NAND", which is a work in progress under the DMA engine. = You can get in touch with the folk doing this work to indicate your = interest and offer testing help if they do have patches against = mainline. -anil On 7 Aug 2014, at 09:06, Gilles DALMAS wrote: > it's sure that if the xen team, stay on the mainline kernel, there = will never a nand support. >=20 >=20 >=20 >=20 >=20 > > Message du 05/08/14 10:32 > > De : "Vincent B." > > A : mirageos-devel@lists.xenproject.org > > Copie =E0 :=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 04/08/2014 15:53, Gilles DALMAS wrote: > > > In terms of the nand, on page: > > > = https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/kerne= l.config.3.4.61 > > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y = and this is the > > > 3.4.61 version of the kernel, how is it that this option does not = appear in the > > > following versions of the kernel? if I add it manually in the = config file, is it > > > processed? > > >=20 > >=20 > > There is no sunxi NAND support yet for the mainline linux Kernel. = Work is > > ongoing, though. > >=20 > > Vincent > >=20 > > _______________________________________________ > > MirageOS-devel mailing list > > MirageOS-devel@lists.xenproject.org > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Gilles,

If you look at the mainlining page for Sunxi = that I pointed you at:


Search for = "NAND", which is a work in progress under the DMA engine.  You can = get in touch with the folk doing this work to indicate your interest and = offer testing help if they do have patches against = mainline.

-anil

On 7 = Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

it's sure that if the xen team, stay on the mainline = kernel, there will never a nand support.




> Message du 05/08/14 10:32
> De : "Vincent = B." <vb@luminar.eu.org>
> A : = mirageos-devel@lists.x= enproject.org
> Copie =E0 :
> Objet : Re: = [MirageOS-devel] mirage os on cubietruck nand detection
>
> = On 04/08/2014 15:53, Gilles DALMAS wrote:
> > In terms of the = nand, on page:
> > https://github.com/igorpecovnik/Cubietruck-Debian= /blob/master/config/kernel.config.3.4.61
> > there is for = example the line CONFIG_SUNXI_NAND_PARTITION =3D y and this is = the
> > 3.4.61 version of the kernel, how is it that this = option does not appear in the
> > following versions of the = kernel? if I add it manually in the config file, is it
> > = processed?
> >
>
> There is no sunxi NAND support = yet for the mainline linux Kernel. Work is
> ongoing, = though.
>
> Vincent
>
> = _______________________________________________
> MirageOS-devel = mailing list
> MirageOS-devel@lists.x= enproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel=
> =
_______________________________________________
MirageOS-d= evel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_86F5B3CC-69E2-47FA-90B4-B705D221D117-- --===============3529815838950012541== 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 --===============3529815838950012541==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 11:09:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 11:09: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 1XFLZJ-000540-7M; Thu, 07 Aug 2014 11:09:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFLZH-00053P-OP for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 11:09:11 +0000 Received: from [85.158.139.211:56178] by server-11.bemta-5.messagelabs.com id DE/DE-31757-75E53E35; Thu, 07 Aug 2014 11:09:11 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-206.messagelabs.com!1407409749!4825613!1 X-Originating-IP: [80.12.242.133] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8832 invoked from network); 7 Aug 2014 11:09:09 -0000 Received: from smtp11.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.133) by server-3.tower-206.messagelabs.com with SMTP; 7 Aug 2014 11:09:09 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d21 with ME id bn991o0010xMosS03n99RS; Thu, 07 Aug 2014 13:09:09 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 13:09:09 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 13:09:09 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <1152518083.7680.1407409749137.JavaMail.www@wwinf1c20> In-Reply-To: References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3091872652134358625==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3091872652134358625== Content-Type: multipart/alternative; boundary="----=_Part_7679_8629376.1407409749130" ------=_Part_7679_8629376.1407409749130 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable not evident, most options kernel version 3.4 does not exist in the mainline= , and I have not yet found a patch. > Message du 07/08/14 10:29 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > Cubieez says it supports graphics (and USB), so I suggest checking > what kernel options they used. >=20 > http://www.cubieez.com/ >=20 > (patches to https://github.com/mirage/xen-arm-builder welcome) >=20 > On 6 August 2014 20:20, Gilles DALMAS wrote: > > [ 14.526] Initializing built-in extension MIT-SCREEN-SAVER > > [ 14.658] (EE) open /dev/dri/card0: No such file or directory > > [ 14.662] (EE) open /dev/fb0: No such file or directory > > [ 14.662] (EE) No devices detected. > > [ 14.666] (EE) open /dev/dri/card0: No such file or directory > > [ 14.667] (EE) open /dev/fb0: No such file or directory > > [ 14.667] (EE) No devices detected. > > [ 14.667] (EE) > > [ 14.667] (EE) no screens found(EE) > > [ 14.668] (EE) > > [ 14.668] (EE) Please also check the log file at "/var/log/Xorg.0.log" = for > > additional information. > > [ 14.668] (EE) > > > > > > > > > > > >> Message du 06/08/14 20:14 > >> De : "Gilles DALMAS"=20 > >> A : "Thomas Leonard"=20 > >> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" > >>=20 > >> Objet : Re: [MirageOS-devel] x interface on cubietruck > >> > >> > > > >> i have installed lxde because i don't know if there was a graphic > >> environment. > > > > > > > > > >> Message du 06/08/14 17:05 > >> De : "Thomas Leonard"=20 > >> A : "Gilles DALMAS"=20 > >> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" > >>=20 > >> Objet : Re: [MirageOS-devel] x interface on cubietruck > >> > >> On 6 August 2014 15:45, Gilles DALMAS wrote: > >> > hello, > >> > > >> > normally, with the cubie.img file of xen-arm-builder, is it possible= to > >> > have > >> > an graphical interface ? lxde or other ? > >> > >> Did you try it? Did you get an error? > >> > >> > >> -- > >> 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 > > >=20 >=20 >=20 > --=20 > 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 > ------=_Part_7679_8629376.1407409749130 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

not evident, most options kernel version 3.4 does not exist in the mainl= ine, and I have not yet found a patch.




> Message du 07/08/14 10:29
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> Cubieez says it suppo= rts graphics (and USB), so I suggest checking
> what kernel options= they used.
>
> http://www.cubieez.com/
>
&g= t; (patches to https://github.com/mirage/xen-arm-builder welcome)
>=
> On 6 August 2014 20:20, Gilles DALMAS <gdalmas@wanadoo.fr>= ; wrote:
> > [ 14.526] Initializing built-in extension MIT-SCREE= N-SAVER
> > [ 14.658] (EE) open /dev/dri/card0: No such file or = directory
> > [ 14.662] (EE) open /dev/fb0: No such file or dire= ctory
> > [ 14.662] (EE) No devices detected.
> > [ 1= 4.666] (EE) open /dev/dri/card0: No such file or directory
> > [= 14.667] (EE) open /dev/fb0: No such file or directory
> > [ 14.= 667] (EE) No devices detected.
> > [ 14.667] (EE)
> >= [ 14.667] (EE) no screens found(EE)
> > [ 14.668] (EE)
>= ; > [ 14.668] (EE) Please also check the log file at "/var/log/Xorg.0.lo= g" for
> > additional information.
> > [ 14.668] (EE)=
> >
> >
> >
> >
> >=
> >> Message du 06/08/14 20:14
> >> De : "Gill= es DALMAS" <gdalmas@wanadoo.fr>
> >> A : "Thomas Leonar= d" <talex5@gmail.com>
> >> Copie =C3=A0 : "mirageos-dev= el@lists.xenproject.org"
> >> <mirageos-devel@lists.xenpro= ject.org>
> >> Objet : Re: [MirageOS-devel] x interface on= cubietruck
> >>
> >>
> >
> = >> i have installed lxde because i don't know if there was a graphic<= br />> >> environment.
> >
> >
> >= ;
> >
> >> Message du 06/08/14 17:05
> >= ;> De : "Thomas Leonard" <talex5@gmail.com>
> >> A := "Gilles DALMAS" <gdalmas@wanadoo.fr>
> >> Copie =C3=A0= : "mirageos-devel@lists.xenproject.org"
> >> <mirageos-de= vel@lists.xenproject.org>
> >> Objet : Re: [MirageOS-devel= ] x interface on cubietruck
> >>
> >> On 6 Augu= st 2014 15:45, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;> > hello,
> >> >
> >> > normally= , with the cubie.img file of xen-arm-builder, is it possible to
> &= gt;> > have
> >> > an graphical interface ? lxde or = other ?
> >>
> >> Did you try it? Did you get a= n error?
> >>
> >>
> >> --
&= gt; >> 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
> >>
&= gt; >
> >
> >
> >
> > ______= _________________________________________
> > MirageOS-devel mai= ling list
> > MirageOS-devel@lists.xenproject.org
> >= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
&= gt; >
>
>
>
> --
> 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
>
------=_Part_7679_8629376.1407409749130-- --===============3091872652134358625== 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 --===============3091872652134358625==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 11:09:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 11:09: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 1XFLZJ-000540-7M; Thu, 07 Aug 2014 11:09:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFLZH-00053P-OP for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 11:09:11 +0000 Received: from [85.158.139.211:56178] by server-11.bemta-5.messagelabs.com id DE/DE-31757-75E53E35; Thu, 07 Aug 2014 11:09:11 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-206.messagelabs.com!1407409749!4825613!1 X-Originating-IP: [80.12.242.133] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8832 invoked from network); 7 Aug 2014 11:09:09 -0000 Received: from smtp11.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.133) by server-3.tower-206.messagelabs.com with SMTP; 7 Aug 2014 11:09:09 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d21 with ME id bn991o0010xMosS03n99RS; Thu, 07 Aug 2014 13:09:09 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 13:09:09 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 13:09:09 +0200 (CEST) From: Gilles DALMAS To: Thomas Leonard Message-ID: <1152518083.7680.1407409749137.JavaMail.www@wwinf1c20> In-Reply-To: References: <401808437.13886.1407336302479.JavaMail.www@wwinf1c13> <485795564.19008.1407348842500.JavaMail.www@wwinf1c13> <2072596031.20277.1407352839921.JavaMail.www@wwinf1c13> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] x interface on cubietruck X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3091872652134358625==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3091872652134358625== Content-Type: multipart/alternative; boundary="----=_Part_7679_8629376.1407409749130" ------=_Part_7679_8629376.1407409749130 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable not evident, most options kernel version 3.4 does not exist in the mainline= , and I have not yet found a patch. > Message du 07/08/14 10:29 > De : "Thomas Leonard"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] x interface on cubietruck >=20 > Cubieez says it supports graphics (and USB), so I suggest checking > what kernel options they used. >=20 > http://www.cubieez.com/ >=20 > (patches to https://github.com/mirage/xen-arm-builder welcome) >=20 > On 6 August 2014 20:20, Gilles DALMAS wrote: > > [ 14.526] Initializing built-in extension MIT-SCREEN-SAVER > > [ 14.658] (EE) open /dev/dri/card0: No such file or directory > > [ 14.662] (EE) open /dev/fb0: No such file or directory > > [ 14.662] (EE) No devices detected. > > [ 14.666] (EE) open /dev/dri/card0: No such file or directory > > [ 14.667] (EE) open /dev/fb0: No such file or directory > > [ 14.667] (EE) No devices detected. > > [ 14.667] (EE) > > [ 14.667] (EE) no screens found(EE) > > [ 14.668] (EE) > > [ 14.668] (EE) Please also check the log file at "/var/log/Xorg.0.log" = for > > additional information. > > [ 14.668] (EE) > > > > > > > > > > > >> Message du 06/08/14 20:14 > >> De : "Gilles DALMAS"=20 > >> A : "Thomas Leonard"=20 > >> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" > >>=20 > >> Objet : Re: [MirageOS-devel] x interface on cubietruck > >> > >> > > > >> i have installed lxde because i don't know if there was a graphic > >> environment. > > > > > > > > > >> Message du 06/08/14 17:05 > >> De : "Thomas Leonard"=20 > >> A : "Gilles DALMAS"=20 > >> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" > >>=20 > >> Objet : Re: [MirageOS-devel] x interface on cubietruck > >> > >> On 6 August 2014 15:45, Gilles DALMAS wrote: > >> > hello, > >> > > >> > normally, with the cubie.img file of xen-arm-builder, is it possible= to > >> > have > >> > an graphical interface ? lxde or other ? > >> > >> Did you try it? Did you get an error? > >> > >> > >> -- > >> 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 > > >=20 >=20 >=20 > --=20 > 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 > ------=_Part_7679_8629376.1407409749130 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

not evident, most options kernel version 3.4 does not exist in the mainl= ine, and I have not yet found a patch.




> Message du 07/08/14 10:29
> De : "Thomas Leona= rd" <talex5@gmail.com>
> A : "Gilles DALMAS" <gdalmas@wana= doo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org" &= lt;mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageOS-= devel] x interface on cubietruck
>
> Cubieez says it suppo= rts graphics (and USB), so I suggest checking
> what kernel options= they used.
>
> http://www.cubieez.com/
>
&g= t; (patches to https://github.com/mirage/xen-arm-builder welcome)
>=
> On 6 August 2014 20:20, Gilles DALMAS <gdalmas@wanadoo.fr>= ; wrote:
> > [ 14.526] Initializing built-in extension MIT-SCREE= N-SAVER
> > [ 14.658] (EE) open /dev/dri/card0: No such file or = directory
> > [ 14.662] (EE) open /dev/fb0: No such file or dire= ctory
> > [ 14.662] (EE) No devices detected.
> > [ 1= 4.666] (EE) open /dev/dri/card0: No such file or directory
> > [= 14.667] (EE) open /dev/fb0: No such file or directory
> > [ 14.= 667] (EE) No devices detected.
> > [ 14.667] (EE)
> >= [ 14.667] (EE) no screens found(EE)
> > [ 14.668] (EE)
>= ; > [ 14.668] (EE) Please also check the log file at "/var/log/Xorg.0.lo= g" for
> > additional information.
> > [ 14.668] (EE)=
> >
> >
> >
> >
> >=
> >> Message du 06/08/14 20:14
> >> De : "Gill= es DALMAS" <gdalmas@wanadoo.fr>
> >> A : "Thomas Leonar= d" <talex5@gmail.com>
> >> Copie =C3=A0 : "mirageos-dev= el@lists.xenproject.org"
> >> <mirageos-devel@lists.xenpro= ject.org>
> >> Objet : Re: [MirageOS-devel] x interface on= cubietruck
> >>
> >>
> >
> = >> i have installed lxde because i don't know if there was a graphic<= br />> >> environment.
> >
> >
> >= ;
> >
> >> Message du 06/08/14 17:05
> >= ;> De : "Thomas Leonard" <talex5@gmail.com>
> >> A := "Gilles DALMAS" <gdalmas@wanadoo.fr>
> >> Copie =C3=A0= : "mirageos-devel@lists.xenproject.org"
> >> <mirageos-de= vel@lists.xenproject.org>
> >> Objet : Re: [MirageOS-devel= ] x interface on cubietruck
> >>
> >> On 6 Augu= st 2014 15:45, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> &g= t;> > hello,
> >> >
> >> > normally= , with the cubie.img file of xen-arm-builder, is it possible to
> &= gt;> > have
> >> > an graphical interface ? lxde or = other ?
> >>
> >> Did you try it? Did you get a= n error?
> >>
> >>
> >> --
&= gt; >> 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
> >>
&= gt; >
> >
> >
> >
> > ______= _________________________________________
> > MirageOS-devel mai= ling list
> > MirageOS-devel@lists.xenproject.org
> >= http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
&= gt; >
>
>
>
> --
> 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
>
------=_Part_7679_8629376.1407409749130-- --===============3091872652134358625== 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 --===============3091872652134358625==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 11:13:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 11:13: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 1XFLdh-0005YK-7r; Thu, 07 Aug 2014 11:13:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFLdf-0005YC-OX for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 11:13:43 +0000 Received: from [85.158.143.35:42267] by server-1.bemta-4.messagelabs.com id 8A/FA-05872-76F53E35; Thu, 07 Aug 2014 11:13:43 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-13.tower-21.messagelabs.com!1407410021!6723071!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1511 invoked from network); 7 Aug 2014 11:13:41 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-13.tower-21.messagelabs.com with SMTP; 7 Aug 2014 11:13:41 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d39 with ME id bnDg1o00M0xMosS03nDgoq; Thu, 07 Aug 2014 13:13:40 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 13:13:40 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 13:13:40 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5889805851367285938==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5889805851367285938== Content-Type: multipart/alternative; boundary="----=_Part_7740_553547290.1407410020944" ------=_Part_7740_553547290.1407410020944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I thought that with this hvm allow me to emulate another architecture, but = if this feature did not work on arm, I do not know how. you know a program,= allowing me to do that? without losing too much power compared to the host= machine. > Message du 07/08/14 11:58 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 >Hi Gilles, > It looks like you are trying to install an x86_64 virtual machine image ont= o an ARM Xen host. =C2=A0This will not work... > -anil > On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: > nobody knows where this error come from? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:53 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > > -anil > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > >=20 > > > > the guest system can only be started in this mode. there is a problems = with this mode ? > >=20 > >=20 > >=20 > >=20 > > > Message du 06/08/14 10:21 > > > De : "Anil Madhavapeddy"=20 > > > A : "Gilles DALMAS"=20 > > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > > >=20 > > > > > > my xl file : > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # Example HVM guest configuration > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # > > > # This is a fairly minimal example of what is required for an > > > # HVM guest. For a more complete guide see xl.cfg(5) > > >=20 > > > # This configures an HVM rather than PV guest > > > builder =3D "hvm" > > >=20 > > > # Guest name > > > name =3D "Xp" > > >=20 > > > # 128-bit UUID for the domain as a hexadecimal number. > > > # Use "uuidgen" to generate one if required. > > > # The default behavior is to generate a new UUID each time the guest = is started. > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > >=20 > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > # enlightenment interfaces. Turning this on can improve Windows guest > > > # performance and is therefore recommended > > > #viridian =3D 1 > > >=20 > > > # Initial memory allocation (MB) > > > memory =3D 512 > > >=20 > > > # Maximum memory (MB) > > > # If this is greater than `memory' then the slack will start balloone= d > > > # (this assumes guest kernel support for ballooning) > > > #maxmem =3D 512 > > >=20 > > > # Number of VCPUS > > > vcpus =3D 2 > > >=20 > > > # Network devices > > > # A list of 'vifspec' entries as described in > > > # docs/misc/xl-network-configuration.markdown > > > vif =3D [ 'bridge=3Dbr0' ] > > >=20 > > > # Disk Devices > > > # A list of `diskspec' entries as described in > > > # docs/misc/xl-disk-configuration.txt > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > >=20 > > > # Guest VGA console configuration, either SDL or VNC > > > sdl =3D 1 > > > #vnc =3D 1 > > >=20 > > > > > > =C2=A0 > Message du 06/08/14 10:03 > > > > De : "Gilles DALMAS"=20 > > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > > Copie =C3=A0 :=20 > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > > > > > hello, > > > > I have this error when i execute : > > > > =C2=A0 > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > Parsing config from /etc/xen/xl.conf > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: creat= e: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefaul= t: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file = or directory > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk= vdev=3Dxvda spec.backend=3Dunknown > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk= vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or direct= ory > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find devic= e model pid in /local/domain/9/image/device-model-pid > > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_devic= e_model failed for 9 > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comp= lete, rc=3D-3 > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inpro= gress: poller=3D0x32578, flags=3Dic > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: dest= roy > > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > > xc: debug: hypercall buffer: current allocations:0 maximum allocation= s:2 > > > xc: debug: hypercall buffer: cache current size:2 > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > > =C2=A0 > > > > i have a cubietruck arm and i have installed qemu-system-arm and qe= mu-system-x86 > > > > =C2=A0 > > >=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 > > > > ------=_Part_7740_553547290.1407410020944 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I thought that with this hvm allow me to emulate another architecture, b= ut if this feature did not work on arm, I do not know how. you know a progr= am, allowing me to do that? without losing too much power compared to the h= ost machine.




> Message du 07/08/14 11:58
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>Hi Gille= s,

>
It looks like you are trying to install an x86_64 virtual machine imag= e onto an ARM Xen host. =C2=A0This will not work...

>
-anil

>
On 7 Aug 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> nobody knows where this error come from?
>
>
>
>
>

> Message du 06/08/14 10:53
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

> >
-anil

> > On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > the guest system can only be started in this mode. there is a = problems with this mode ?
> >
> >
> > > >
> >

> Message du 06/08/14 10:21
> > > De : "An= il Madhavapeddy" <anil@recoil.org= >
> > > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > > Copie =C3=A0 : "= mirageos-devel@lists= .xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Objet = : Re: [MirageOS-devel] error when i create hvm guest
> > > > > >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>= > >
> > >

> > > my xl file :
> > > # =3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > # Example HVM gues= t configuration
> > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
> > > #
> > > # This is a= fairly minimal example of what is required for an
> > > # HV= M guest. For a more complete guide see xl.cfg(5)
> > >
= > > > # This configures an HVM rather than PV guest
> >= > builder =3D "hvm"
> > >
> > > # Guest na= me
> > > name =3D "Xp"
> > >
> > &g= t; # 128-bit UUID for the domain as a hexadecimal number.
> > &g= t; # Use "uuidgen" to generate one if required.
> > > # The d= efault behavior is to generate a new UUID each time the guest is started.> > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
&g= t; > >
> > > # Enable Microsoft Hyper-V compatibile pa= ravirtualisation /
> > > # enlightenment interfaces. Turning = this on can improve Windows guest
> > > # performance and is = therefore recommended
> > > #viridian =3D 1
> > &g= t;
> > > # Initial memory allocation (MB)
> > >= ; memory =3D 512
> > >
> > > # Maximum memory = (MB)
> > > # If this is greater than `memory' then the slack = will start ballooned
> > > # (this assumes guest kernel suppo= rt for ballooning)
> > > #maxmem =3D 512
> > > =
> > > # Number of VCPUS
> > > vcpus =3D 2
> > >
> > > # Network devices
> > > = # A list of 'vifspec' entries as described in
> > > # docs/mi= sc/xl-network-configuration.markdown
> > > vif =3D [ 'bridge= =3Dbr0' ]
> > >
> > > # Disk Devices
>= > > # A list of `diskspec' entries as described in
> > &g= t; # docs/misc/xl-disk-configuration.txt
> > > disk =3D [ '/d= ev/vg0/guest-linux-1,raw,xvda,rw' ]
> > >
> > >= ; # Guest VGA console configuration, either SDL or VNC
> > > = sdl =3D 1
> > > #vnc =3D 1
> > >
> >= ; >

> > > =C2=A0

> Message du 06/08/14 10:03
> > > > De = : "Gilles DALMAS" <gdalmas@wanadoo= .fr>
> > > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> > > > Copie =C3=A0 :
> > &g= t; > Objet : [MirageOS-devel] error when i create hvm guest
> &g= t; > >
> > > >

> > > > hello,

> > > > I have this error when i execute :

> > > > =C2=A0

> > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl= .conf
> > > Parsing config from /etc/xen/xl.conf
> &g= t; > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: cre= ate: how=3D(nil) callback=3D(nil) poller=3D0x32578
> > > libx= l: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xe= n is unavailable, use qemu-xen-traditional instead: No such file or directo= ry
> > > libxl: debug: libxl_device.c:251:libxl__device_disk_= set_backend: Disk vdev=3Dxvda spec.backend=3Dunknown
> > > li= bxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3D= xvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory
> > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to = find device model pid in /local/domain/9/image/device-model-pid
> &= gt; > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_de= vice_model failed for 9
> > > libxl: debug: libxl_event.c:159= 1:libxl__ao_complete: ao 0x31f00: complete, rc=3D-3
> > > lib= xl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: po= ller=3D0x32578, flags=3Dic
> > > libxl: debug: libxl_event.c:= 1563:libxl__ao__destroy: ao 0x31f00: destroy
> > > xc: debug:= hypercall buffer: total allocations:26 total releases:26
> > &g= t; xc: debug: hypercall buffer: current allocations:0 maximum allocations:2=
> > > xc: debug: hypercall buffer: cache current size:2
> > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > > =C2=A0

> > > > i have a cubietruck arm and i have installed qemu-sy= stem-arm and qemu-system-x86

> > > > =C2=A0


> > >
> > >
> > > ____________= ___________________________________
> > > MirageOS-devel mail= ing list
> > > MirageOS-devel@lists.xenproject.org
> > > h= ttp://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > >
> > >
_______________________________________________
>= > > MirageOS-devel mailing list
> > > MirageOS-devel@li= sts.xenproject.org
> > > http://lists.x= enproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> = > >

>
------=_Part_7740_553547290.1407410020944-- --===============5889805851367285938== 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 --===============5889805851367285938==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 11:13:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 11:13: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 1XFLdh-0005YK-7r; Thu, 07 Aug 2014 11:13:45 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFLdf-0005YC-OX for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 11:13:43 +0000 Received: from [85.158.143.35:42267] by server-1.bemta-4.messagelabs.com id 8A/FA-05872-76F53E35; Thu, 07 Aug 2014 11:13:43 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-13.tower-21.messagelabs.com!1407410021!6723071!1 X-Originating-IP: [80.12.242.126] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1511 invoked from network); 7 Aug 2014 11:13:41 -0000 Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by server-13.tower-21.messagelabs.com with SMTP; 7 Aug 2014 11:13:41 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d39 with ME id bnDg1o00M0xMosS03nDgoq; Thu, 07 Aug 2014 13:13:40 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 13:13:40 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 13:13:40 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> In-Reply-To: References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============5889805851367285938==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5889805851367285938== Content-Type: multipart/alternative; boundary="----=_Part_7740_553547290.1407410020944" ------=_Part_7740_553547290.1407410020944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I thought that with this hvm allow me to emulate another architecture, but = if this feature did not work on arm, I do not know how. you know a program,= allowing me to do that? without losing too much power compared to the host= machine. > Message du 07/08/14 11:58 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 >Hi Gilles, > It looks like you are trying to install an x86_64 virtual machine image ont= o an ARM Xen host. =C2=A0This will not work... > -anil > On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: > nobody knows where this error come from? >=20 >=20 >=20 >=20 > > Message du 06/08/14 10:53 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > > -anil > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > >=20 > > > > the guest system can only be started in this mode. there is a problems = with this mode ? > >=20 > >=20 > >=20 > >=20 > > > Message du 06/08/14 10:21 > > > De : "Anil Madhavapeddy"=20 > > > A : "Gilles DALMAS"=20 > > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > > >=20 > > > > > > my xl file : > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # Example HVM guest configuration > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > # > > > # This is a fairly minimal example of what is required for an > > > # HVM guest. For a more complete guide see xl.cfg(5) > > >=20 > > > # This configures an HVM rather than PV guest > > > builder =3D "hvm" > > >=20 > > > # Guest name > > > name =3D "Xp" > > >=20 > > > # 128-bit UUID for the domain as a hexadecimal number. > > > # Use "uuidgen" to generate one if required. > > > # The default behavior is to generate a new UUID each time the guest = is started. > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > >=20 > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > # enlightenment interfaces. Turning this on can improve Windows guest > > > # performance and is therefore recommended > > > #viridian =3D 1 > > >=20 > > > # Initial memory allocation (MB) > > > memory =3D 512 > > >=20 > > > # Maximum memory (MB) > > > # If this is greater than `memory' then the slack will start balloone= d > > > # (this assumes guest kernel support for ballooning) > > > #maxmem =3D 512 > > >=20 > > > # Number of VCPUS > > > vcpus =3D 2 > > >=20 > > > # Network devices > > > # A list of 'vifspec' entries as described in > > > # docs/misc/xl-network-configuration.markdown > > > vif =3D [ 'bridge=3Dbr0' ] > > >=20 > > > # Disk Devices > > > # A list of `diskspec' entries as described in > > > # docs/misc/xl-disk-configuration.txt > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > >=20 > > > # Guest VGA console configuration, either SDL or VNC > > > sdl =3D 1 > > > #vnc =3D 1 > > >=20 > > > > > > =C2=A0 > Message du 06/08/14 10:03 > > > > De : "Gilles DALMAS"=20 > > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > > Copie =C3=A0 :=20 > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > > > > > hello, > > > > I have this error when i execute : > > > > =C2=A0 > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > Parsing config from /etc/xen/xl.conf > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: creat= e: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefaul= t: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file = or directory > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk= vdev=3Dxvda spec.backend=3Dunknown > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk= vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or direct= ory > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find devic= e model pid in /local/domain/9/image/device-model-pid > > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_devic= e_model failed for 9 > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: comp= lete, rc=3D-3 > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inpro= gress: poller=3D0x32578, flags=3Dic > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: dest= roy > > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > > xc: debug: hypercall buffer: current allocations:0 maximum allocation= s:2 > > > xc: debug: hypercall buffer: cache current size:2 > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > > =C2=A0 > > > > i have a cubietruck arm and i have installed qemu-system-arm and qe= mu-system-x86 > > > > =C2=A0 > > >=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 > > > > ------=_Part_7740_553547290.1407410020944 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I thought that with this hvm allow me to emulate another architecture, b= ut if this feature did not work on arm, I do not know how. you know a progr= am, allowing me to do that? without losing too much power compared to the h= ost machine.




> Message du 07/08/14 11:58
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>Hi Gille= s,

>
It looks like you are trying to install an x86_64 virtual machine imag= e onto an ARM Xen host. =C2=A0This will not work...

>
-anil

>
On 7 Aug 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> nobody knows where this error come from?
>
>
>
>
>

> Message du 06/08/14 10:53
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

> >
-anil

> > On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
> >=
> >

> > the guest system can only be started in this mode. there is a = problems with this mode ?
> >
> >
> > > >
> >

> Message du 06/08/14 10:21
> > > De : "An= il Madhavapeddy" <anil@recoil.org= >
> > > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > > Copie =C3=A0 : "= mirageos-devel@lists= .xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Objet = : Re: [MirageOS-devel] error when i create hvm guest
> > > > > >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>= > >
> > >

> > > my xl file :
> > > # =3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > # Example HVM gues= t configuration
> > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
> > > #
> > > # This is a= fairly minimal example of what is required for an
> > > # HV= M guest. For a more complete guide see xl.cfg(5)
> > >
= > > > # This configures an HVM rather than PV guest
> >= > builder =3D "hvm"
> > >
> > > # Guest na= me
> > > name =3D "Xp"
> > >
> > &g= t; # 128-bit UUID for the domain as a hexadecimal number.
> > &g= t; # Use "uuidgen" to generate one if required.
> > > # The d= efault behavior is to generate a new UUID each time the guest is started.> > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
&g= t; > >
> > > # Enable Microsoft Hyper-V compatibile pa= ravirtualisation /
> > > # enlightenment interfaces. Turning = this on can improve Windows guest
> > > # performance and is = therefore recommended
> > > #viridian =3D 1
> > &g= t;
> > > # Initial memory allocation (MB)
> > >= ; memory =3D 512
> > >
> > > # Maximum memory = (MB)
> > > # If this is greater than `memory' then the slack = will start ballooned
> > > # (this assumes guest kernel suppo= rt for ballooning)
> > > #maxmem =3D 512
> > > =
> > > # Number of VCPUS
> > > vcpus =3D 2
> > >
> > > # Network devices
> > > = # A list of 'vifspec' entries as described in
> > > # docs/mi= sc/xl-network-configuration.markdown
> > > vif =3D [ 'bridge= =3Dbr0' ]
> > >
> > > # Disk Devices
>= > > # A list of `diskspec' entries as described in
> > &g= t; # docs/misc/xl-disk-configuration.txt
> > > disk =3D [ '/d= ev/vg0/guest-linux-1,raw,xvda,rw' ]
> > >
> > >= ; # Guest VGA console configuration, either SDL or VNC
> > > = sdl =3D 1
> > > #vnc =3D 1
> > >
> >= ; >

> > > =C2=A0

> Message du 06/08/14 10:03
> > > > De = : "Gilles DALMAS" <gdalmas@wanadoo= .fr>
> > > > A : "mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenpro= ject.org>
> > > > Copie =C3=A0 :
> > &g= t; > Objet : [MirageOS-devel] error when i create hvm guest
> &g= t; > >
> > > >

> > > > hello,

> > > > I have this error when i execute :

> > > > =C2=A0

> > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl= .conf
> > > Parsing config from /etc/xen/xl.conf
> &g= t; > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: cre= ate: how=3D(nil) callback=3D(nil) poller=3D0x32578
> > > libx= l: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xe= n is unavailable, use qemu-xen-traditional instead: No such file or directo= ry
> > > libxl: debug: libxl_device.c:251:libxl__device_disk_= set_backend: Disk vdev=3Dxvda spec.backend=3Dunknown
> > > li= bxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3D= xvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory
> > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to = find device model pid in /local/domain/9/image/device-model-pid
> &= gt; > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_de= vice_model failed for 9
> > > libxl: debug: libxl_event.c:159= 1:libxl__ao_complete: ao 0x31f00: complete, rc=3D-3
> > > lib= xl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: po= ller=3D0x32578, flags=3Dic
> > > libxl: debug: libxl_event.c:= 1563:libxl__ao__destroy: ao 0x31f00: destroy
> > > xc: debug:= hypercall buffer: total allocations:26 total releases:26
> > &g= t; xc: debug: hypercall buffer: current allocations:0 maximum allocations:2=
> > > xc: debug: hypercall buffer: cache current size:2
> > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > > =C2=A0

> > > > i have a cubietruck arm and i have installed qemu-sy= stem-arm and qemu-system-x86

> > > > =C2=A0


> > >
> > >
> > > ____________= ___________________________________
> > > MirageOS-devel mail= ing list
> > > MirageOS-devel@lists.xenproject.org
> > > h= ttp://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > >
> > >
_______________________________________________
>= > > MirageOS-devel mailing list
> > > MirageOS-devel@li= sts.xenproject.org
> > > http://lists.x= enproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> = > >

>
------=_Part_7740_553547290.1407410020944-- --===============5889805851367285938== 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 --===============5889805851367285938==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 11:18:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 11:18: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 1XFLiT-0005dE-PI; Thu, 07 Aug 2014 11:18:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFLiT-0005d9-1Q for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 11:18:41 +0000 Received: from [193.109.254.147:8510] by server-1.bemta-14.messagelabs.com id 6A/DA-24760-09063E35; Thu, 07 Aug 2014 11:18:40 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-9.tower-27.messagelabs.com!1407410319!14284665!1 X-Originating-IP: [80.12.242.123] 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 25456 invoked from network); 7 Aug 2014 11:18:39 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-9.tower-27.messagelabs.com with SMTP; 7 Aug 2014 11:18:39 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d01 with ME id bnJe1o00C0xMosS03nJe1l; Thu, 07 Aug 2014 13:18:38 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 13:18:38 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 13:18:38 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <399931700.7855.1407410318674.JavaMail.www@wwinf1c20> In-Reply-To: <1255BAA1-D9B1-41DC-96BB-EA00BE63B1AA@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> <1255BAA1-D9B1-41DC-96BB-EA00BE63B1AA@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~||~| X-WUM-REPLYTO: |~| Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6807953569718310280==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6807953569718310280== Content-Type: multipart/alternative; boundary="----=_Part_7854_2144824206.1407410318667" ------=_Part_7854_2144824206.1407410318667 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ok, I will inquire.=C2=A0 thank you anil =C2=A0 =C2=A0 > Message du 07/08/14 12:00 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "Vincent B." , mirageos-devel@lists.xenproject.org > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 >Hi Gilles, > If you look at the mainlining page for Sunxi that I pointed you at: > http://linux-sunxi.org/Linux_mainlining_effort > Search for "NAND", which is a work in progress under the DMA engine. =C2=A0= You can get in touch with the folk doing this work to indicate your interes= t and offer testing help if they do have patches against mainline. > -anil > On 7 Aug 2014, at 09:06, Gilles DALMAS wrote: > it's sure that if the xen team, stay on the mainline kernel, there will n= ever a nand support. >=20 >=20 >=20 >=20 > > Message du 05/08/14 10:32 > > De : "Vincent B."=20 > > A : mirageos-devel@lists.xenproject.org > > Copie =C3=A0 :=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 04/08/2014 15:53, Gilles DALMAS wrote: > > > In terms of the nand, on page: > > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/= kernel.config.3.4.61 > > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and t= his is the > > > 3.4.61 version of the kernel, how is it that this option does not app= ear in the > > > following versions of the kernel? if I add it manually in the config = file, is it > > > processed? > > >=20 > >=20 > > There is no sunxi NAND support yet for the mainline linux Kernel. Work = is > > ongoing, though. > >=20 > > Vincent > >=20 > > _______________________________________________ > > 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 > > ------=_Part_7854_2144824206.1407410318667 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

ok, I will inquire.=C2=A0

thank you anil

=C2=A0

=C2=A0

> Message du 07/08/14 12:00
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "Vincent B." <vb@luminar.eu.org>= ;, mirageos-devel@lists.xenproject.org
> Objet : Re: [MirageOS-deve= l] mirage os on cubietruck nand detection
>
>Hi Gilles,

>
If you look at the mainlining page for Sunxi that I pointed you at:

>

>
Search for "NAND", which is a work in progress under the DMA engine. = =C2=A0You can get in touch with the folk doing this work to indicate your i= nterest and offer testing help if they do have patches against mainline.

>
-anil

>
On 7 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> it's sure that if the xen team, stay on the mainline kernel, there = will never a nand support.
>
>
>
>
>

> Message du 05/08/14 10:32
> > De : "Vincent= B." <vb@luminar.eu.org>
> > A : mira= geos-devel@lists.xenproject.org
> > Copie =C3=A0 :
>= ; > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection<= br />> >
> > On 04/08/2014 15:53, Gilles DALMAS wrote:> > > In terms of the nand, on page:
> > > https://github.com/igorpecovnik/Cubietruck-Debian/blob= /master/config/kernel.config.3.4.61
> > > there is for ex= ample the line CONFIG_SUNXI_NAND_PARTITION =3D y and this is the
> = > > 3.4.61 version of the kernel, how is it that this option does not= appear in the
> > > following versions of the kernel? if I a= dd it manually in the config file, is it
> > > processed?
> > >
> >
> > There is no sunxi NAND sup= port yet for the mainline linux Kernel. Work is
> > ongoing, tho= ugh.
> >
> > Vincent
> >
> > = _______________________________________________
> > MirageOS-dev= el mailing list
> > MirageOS-devel@lists.xenproject.org
> > ht= tp://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
= > >
_______________________________________________
> MirageOS-devel ma= iling list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.= org/cgi-bin/mailman/listinfo/mirageos-devel
>

>
------=_Part_7854_2144824206.1407410318667-- --===============6807953569718310280== 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 --===============6807953569718310280==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 11:18:42 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 11:18: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 1XFLiT-0005dE-PI; Thu, 07 Aug 2014 11:18:41 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFLiT-0005d9-1Q for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 11:18:41 +0000 Received: from [193.109.254.147:8510] by server-1.bemta-14.messagelabs.com id 6A/DA-24760-09063E35; Thu, 07 Aug 2014 11:18:40 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-9.tower-27.messagelabs.com!1407410319!14284665!1 X-Originating-IP: [80.12.242.123] 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 25456 invoked from network); 7 Aug 2014 11:18:39 -0000 Received: from smtp01.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.123) by server-9.tower-27.messagelabs.com with SMTP; 7 Aug 2014 11:18:39 -0000 Received: from wwinf1c20 ([10.223.79.44]) by mwinf5d01 with ME id bnJe1o00C0xMosS03nJe1l; Thu, 07 Aug 2014 13:18:38 +0200 X-ME-Helo: wwinf1c20 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Thu, 07 Aug 2014 13:18:38 +0200 X-ME-IP: 90.15.132.120 Date: Thu, 7 Aug 2014 13:18:38 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <399931700.7855.1407410318674.JavaMail.www@wwinf1c20> In-Reply-To: <1255BAA1-D9B1-41DC-96BB-EA00BE63B1AA@recoil.org> References: <1198925117.5996.1407080074697.JavaMail.www@wwinf1h10> <5965C781-0DAB-48C8-B879-E5A30DFFAE25@recoil.org> <1597795059.11954.1407157422728.JavaMail.www@wwinf1p23> <245057971.13157.1407160433408.JavaMail.www@wwinf1p23> <53E09685.7030304@luminar.eu.org> <2143160411.3576.1407398783559.JavaMail.www@wwinf1c20> <1255BAA1-D9B1-41DC-96BB-EA00BE63B1AA@recoil.org> MIME-Version: 1.0 X-Originating-IP: [90.15.132.120] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~||~| X-WUM-REPLYTO: |~| Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] mirage os on cubietruck nand detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6807953569718310280==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6807953569718310280== Content-Type: multipart/alternative; boundary="----=_Part_7854_2144824206.1407410318667" ------=_Part_7854_2144824206.1407410318667 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ok, I will inquire.=C2=A0 thank you anil =C2=A0 =C2=A0 > Message du 07/08/14 12:00 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "Vincent B." , mirageos-devel@lists.xenproject.org > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection >=20 >Hi Gilles, > If you look at the mainlining page for Sunxi that I pointed you at: > http://linux-sunxi.org/Linux_mainlining_effort > Search for "NAND", which is a work in progress under the DMA engine. =C2=A0= You can get in touch with the folk doing this work to indicate your interes= t and offer testing help if they do have patches against mainline. > -anil > On 7 Aug 2014, at 09:06, Gilles DALMAS wrote: > it's sure that if the xen team, stay on the mainline kernel, there will n= ever a nand support. >=20 >=20 >=20 >=20 > > Message du 05/08/14 10:32 > > De : "Vincent B."=20 > > A : mirageos-devel@lists.xenproject.org > > Copie =C3=A0 :=20 > > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection > >=20 > > On 04/08/2014 15:53, Gilles DALMAS wrote: > > > In terms of the nand, on page: > > > https://github.com/igorpecovnik/Cubietruck-Debian/blob/master/config/= kernel.config.3.4.61 > > > there is for example the line CONFIG_SUNXI_NAND_PARTITION =3D y and t= his is the > > > 3.4.61 version of the kernel, how is it that this option does not app= ear in the > > > following versions of the kernel? if I add it manually in the config = file, is it > > > processed? > > >=20 > >=20 > > There is no sunxi NAND support yet for the mainline linux Kernel. Work = is > > ongoing, though. > >=20 > > Vincent > >=20 > > _______________________________________________ > > 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 > > ------=_Part_7854_2144824206.1407410318667 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

ok, I will inquire.=C2=A0

thank you anil

=C2=A0

=C2=A0

> Message du 07/08/14 12:00
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "Vincent B." <vb@luminar.eu.org>= ;, mirageos-devel@lists.xenproject.org
> Objet : Re: [MirageOS-deve= l] mirage os on cubietruck nand detection
>
>Hi Gilles,

>
If you look at the mainlining page for Sunxi that I pointed you at:

>

>
Search for "NAND", which is a work in progress under the DMA engine. = =C2=A0You can get in touch with the folk doing this work to indicate your i= nterest and offer testing help if they do have patches against mainline.

>
-anil

>
On 7 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> it's sure that if the xen team, stay on the mainline kernel, there = will never a nand support.
>
>
>
>
>

> Message du 05/08/14 10:32
> > De : "Vincent= B." <vb@luminar.eu.org>
> > A : mira= geos-devel@lists.xenproject.org
> > Copie =C3=A0 :
>= ; > Objet : Re: [MirageOS-devel] mirage os on cubietruck nand detection<= br />> >
> > On 04/08/2014 15:53, Gilles DALMAS wrote:> > > In terms of the nand, on page:
> > > https://github.com/igorpecovnik/Cubietruck-Debian/blob= /master/config/kernel.config.3.4.61
> > > there is for ex= ample the line CONFIG_SUNXI_NAND_PARTITION =3D y and this is the
> = > > 3.4.61 version of the kernel, how is it that this option does not= appear in the
> > > following versions of the kernel? if I a= dd it manually in the config file, is it
> > > processed?
> > >
> >
> > There is no sunxi NAND sup= port yet for the mainline linux Kernel. Work is
> > ongoing, tho= ugh.
> >
> > Vincent
> >
> > = _______________________________________________
> > MirageOS-dev= el mailing list
> > MirageOS-devel@lists.xenproject.org
> > ht= tp://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
= > >
_______________________________________________
> MirageOS-devel ma= iling list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.= org/cgi-bin/mailman/listinfo/mirageos-devel
>

>
------=_Part_7854_2144824206.1407410318667-- --===============6807953569718310280== 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 --===============6807953569718310280==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 12:29:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 12: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 1XFMpK-0008WS-Tk; Thu, 07 Aug 2014 12:29:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFMpJ-0008WN-Aq for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 12:29:49 +0000 Received: from [85.158.143.35:59323] by server-1.bemta-4.messagelabs.com id 03/2E-05872-C3173E35; Thu, 07 Aug 2014 12:29:48 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1407414587!14017556!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 16447 invoked from network); 7 Aug 2014 12:29:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-5.tower-21.messagelabs.com with SMTP; 7 Aug 2014 12:29:47 -0000 X-IronPort-AV: E=Sophos;i="5.01,817,1400025600"; d="scan'208";a="23767862" From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] wireshark capture of failed download from mirage-www on ARM Thread-Index: AQHPpYuIBxgRhFqKh0q2qXEpVAjF9pur4VKAgAE8hwCAACuggIAAKDCAgAHa7wCAAUUzAIAAwr0AgACmcgCAB/EbAIALHdUA Date: Thu, 7 Aug 2014 12:29:46 +0000 Message-ID: <476A0FE5-67CC-439F-9E7D-1057B6D28AD7@citrix.com> References: <36D06E0F-8336-4142-80BF-29586554A9C5@nottingham.ac.uk> <53088F2B-1AC3-4D35-BB37-247337690798@nottingham.ac.uk> <5BD43696-D536-4690-A628-98C88C1A0479@citrix.com> <90A2FFCA-A5F3-44A4-AC9F-F31C1B04AD6E@recoil.org> <46605CC2-8C25-460E-9963-76DDC59B6802@recoil.org> <1C889C81-6EAA-4A21-AE47-6D825F6E93FB@citrix.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <7BC5C420A503574DAE29EAF58786C3E1@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] wireshark capture of failed download from mirage-www on ARM X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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, Sorry for the delay replying! On 31 Jul 2014, at 11:44, Thomas Leonard wrote: > On 26 July 2014 10:27, David Scott wrote: >> = >> = >> On Saturday, July 26, 2014, Anil Madhavapeddy wrote: >>> = >>> On 25 Jul 2014, at 04:54, Thomas Leonard wrote: >>>> = >>>> Here's a slightly better work-around: >>>> = >>>> = >>>> https://github.com/talex5/mirage-tcpip/commit/9f7e0a628ebd1cece7d0fb97= 9273a96be78233ad >>>> = >>>> It changes the TCP packet splitting code so that the second part of >>>> the page is copied to a new IO page. This avoids sending the same >>>> physical page to Linux twice (which is what doesn't work). >>>> = >>>> With this, the previous hack can be reverted. >>>> = >>>> In my testing, this increased the streaming TCP download speed from 56 >>>> KB/s to 3.9 MB/s on the CubieTruck. >>> = >>> This is certainly a fix that works, but I'm loath to insert an unnecess= ary >>> copy in the TCP stack just because of a limitation in Xen/ARM (that will >>> go >>> away in Xen 4.5, I expect). >>> = >>> Could we keep track of the active grants in the Gnttab libary, and forc= e a >>> page duplication at that point instead? That would fix it for any other >>> Cstruct consumers as well, and be a more logical place to insert Xen >>> version detection in the future to remove the extra copy if not needed. >> = >> = >> If the problem is granting the same page twice, would it be enough to >> maintain a map of page address to (grant index * refount), and then >> "grant_access" could return the existing grant id and bump the refcount?= I >> think we just need to share the grant, rather than duplicate the page. (= Is >> that right?) > = > How would that fit in with the current API? It looks like you first > allocate a gntref (an int) and then use that to share the page: > = > val get : unit -> gntref Lwt.t > = > val grant_access : domid:int -> writable:bool -> gntref -> Io_page.t -> = unit Yeah looking at it I think that interface is a bit too =91raw=92. Unfortuna= tely =91type gntref =3D int=92 in the interface so clients are free to do t= hings like ``` ignore(RX.Proto_64.write ~id ~gref:(Int32.of_int gref) slot) ``` I had been hoping to exploit the observation that (I think all) users call = =91grant_access=92 before serialising the grant reference into the ring met= adata slot. My evil/cunning plan had been to allocate a fresh grant in =91g= et()=92 as normal, but then swizzle it inside =91grant_access=92 if it turn= s out that a grant has already been allocated in that page. However I would= need to change the implementation of =91type gntref=92 to make this work := -( Anyway, looking at the current users in mirage-{block,net}-xen, I can see 2= users of the low-level API: 1. granting access to the metadata ring on startup e.g. ``` let allocate_ring ~domid =3D let page =3D Io_page.get 1 in let x =3D Io_page.to_cstruct page in lwt gnt =3D Gnt.Gntshr.get () in for i =3D 0 to Cstruct.len x - 1 do Cstruct.set_uint8 x i 0 done; Gnt.Gntshr.grant_access ~domid ~writable:true gnt page; return (gnt, x) ``` 2. granting access to pages for I/O e.g. ``` let refill_requests nf =3D let num =3D Ring.Rpc.Front.get_free_requests nf.rx_fring in if num > 0 then lwt grefs =3D Gnt.Gntshr.get_n num in let pages =3D Io_page.pages num in List.iter (fun (gref, page) -> let id =3D gref mod (1 lsl 16) in Gnt.Gntshr.grant_access ~domid:nf.backend_id ~writable:true gref p= age; Hashtbl.add nf.rx_map id (gref, page); let slot_id =3D Ring.Rpc.Front.next_req_id nf.rx_fring in let slot =3D Ring.Rpc.Front.slot nf.rx_fring slot_id in ignore(RX.Proto_64.write ~id ~gref:(Int32.of_int gref) slot) ) (List.combine grefs pages); if Ring.Rpc.Front.push_requests_and_check_notify nf.rx_fring then notify nf (); return () else return () ``` We=92ve already got a =91with_grants=92 function but this doesn=92t work fo= r these cases because they both want to =91leak=92 the grants (they are cle= aned up elsewhere). Perhaps we should make an API (=91return_grants=92 =91a= lloc_grants=92?) which combines =91get_n=92 and =91grant_access=92? Do you know if the bug is likely to be fixed in the backend in a reasonable= timeframe? Or is it worth changing the API soon so we could make a workaro= und in the frontend? 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 Aug 07 12:29:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 12: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 1XFMpK-0008WS-Tk; Thu, 07 Aug 2014 12:29:50 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFMpJ-0008WN-Aq for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 12:29:49 +0000 Received: from [85.158.143.35:59323] by server-1.bemta-4.messagelabs.com id 03/2E-05872-C3173E35; Thu, 07 Aug 2014 12:29:48 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1407414587!14017556!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 16447 invoked from network); 7 Aug 2014 12:29:47 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-5.tower-21.messagelabs.com with SMTP; 7 Aug 2014 12:29:47 -0000 X-IronPort-AV: E=Sophos;i="5.01,817,1400025600"; d="scan'208";a="23767862" From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] wireshark capture of failed download from mirage-www on ARM Thread-Index: AQHPpYuIBxgRhFqKh0q2qXEpVAjF9pur4VKAgAE8hwCAACuggIAAKDCAgAHa7wCAAUUzAIAAwr0AgACmcgCAB/EbAIALHdUA Date: Thu, 7 Aug 2014 12:29:46 +0000 Message-ID: <476A0FE5-67CC-439F-9E7D-1057B6D28AD7@citrix.com> References: <36D06E0F-8336-4142-80BF-29586554A9C5@nottingham.ac.uk> <53088F2B-1AC3-4D35-BB37-247337690798@nottingham.ac.uk> <5BD43696-D536-4690-A628-98C88C1A0479@citrix.com> <90A2FFCA-A5F3-44A4-AC9F-F31C1B04AD6E@recoil.org> <46605CC2-8C25-460E-9963-76DDC59B6802@recoil.org> <1C889C81-6EAA-4A21-AE47-6D825F6E93FB@citrix.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <7BC5C420A503574DAE29EAF58786C3E1@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] wireshark capture of failed download from mirage-www on ARM X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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, Sorry for the delay replying! On 31 Jul 2014, at 11:44, Thomas Leonard wrote: > On 26 July 2014 10:27, David Scott wrote: >> = >> = >> On Saturday, July 26, 2014, Anil Madhavapeddy wrote: >>> = >>> On 25 Jul 2014, at 04:54, Thomas Leonard wrote: >>>> = >>>> Here's a slightly better work-around: >>>> = >>>> = >>>> https://github.com/talex5/mirage-tcpip/commit/9f7e0a628ebd1cece7d0fb97= 9273a96be78233ad >>>> = >>>> It changes the TCP packet splitting code so that the second part of >>>> the page is copied to a new IO page. This avoids sending the same >>>> physical page to Linux twice (which is what doesn't work). >>>> = >>>> With this, the previous hack can be reverted. >>>> = >>>> In my testing, this increased the streaming TCP download speed from 56 >>>> KB/s to 3.9 MB/s on the CubieTruck. >>> = >>> This is certainly a fix that works, but I'm loath to insert an unnecess= ary >>> copy in the TCP stack just because of a limitation in Xen/ARM (that will >>> go >>> away in Xen 4.5, I expect). >>> = >>> Could we keep track of the active grants in the Gnttab libary, and forc= e a >>> page duplication at that point instead? That would fix it for any other >>> Cstruct consumers as well, and be a more logical place to insert Xen >>> version detection in the future to remove the extra copy if not needed. >> = >> = >> If the problem is granting the same page twice, would it be enough to >> maintain a map of page address to (grant index * refount), and then >> "grant_access" could return the existing grant id and bump the refcount?= I >> think we just need to share the grant, rather than duplicate the page. (= Is >> that right?) > = > How would that fit in with the current API? It looks like you first > allocate a gntref (an int) and then use that to share the page: > = > val get : unit -> gntref Lwt.t > = > val grant_access : domid:int -> writable:bool -> gntref -> Io_page.t -> = unit Yeah looking at it I think that interface is a bit too =91raw=92. Unfortuna= tely =91type gntref =3D int=92 in the interface so clients are free to do t= hings like ``` ignore(RX.Proto_64.write ~id ~gref:(Int32.of_int gref) slot) ``` I had been hoping to exploit the observation that (I think all) users call = =91grant_access=92 before serialising the grant reference into the ring met= adata slot. My evil/cunning plan had been to allocate a fresh grant in =91g= et()=92 as normal, but then swizzle it inside =91grant_access=92 if it turn= s out that a grant has already been allocated in that page. However I would= need to change the implementation of =91type gntref=92 to make this work := -( Anyway, looking at the current users in mirage-{block,net}-xen, I can see 2= users of the low-level API: 1. granting access to the metadata ring on startup e.g. ``` let allocate_ring ~domid =3D let page =3D Io_page.get 1 in let x =3D Io_page.to_cstruct page in lwt gnt =3D Gnt.Gntshr.get () in for i =3D 0 to Cstruct.len x - 1 do Cstruct.set_uint8 x i 0 done; Gnt.Gntshr.grant_access ~domid ~writable:true gnt page; return (gnt, x) ``` 2. granting access to pages for I/O e.g. ``` let refill_requests nf =3D let num =3D Ring.Rpc.Front.get_free_requests nf.rx_fring in if num > 0 then lwt grefs =3D Gnt.Gntshr.get_n num in let pages =3D Io_page.pages num in List.iter (fun (gref, page) -> let id =3D gref mod (1 lsl 16) in Gnt.Gntshr.grant_access ~domid:nf.backend_id ~writable:true gref p= age; Hashtbl.add nf.rx_map id (gref, page); let slot_id =3D Ring.Rpc.Front.next_req_id nf.rx_fring in let slot =3D Ring.Rpc.Front.slot nf.rx_fring slot_id in ignore(RX.Proto_64.write ~id ~gref:(Int32.of_int gref) slot) ) (List.combine grefs pages); if Ring.Rpc.Front.push_requests_and_check_notify nf.rx_fring then notify nf (); return () else return () ``` We=92ve already got a =91with_grants=92 function but this doesn=92t work fo= r these cases because they both want to =91leak=92 the grants (they are cle= aned up elsewhere). Perhaps we should make an API (=91return_grants=92 =91a= lloc_grants=92?) which combines =91get_n=92 and =91grant_access=92? Do you know if the bug is likely to be fixed in the backend in a reasonable= timeframe? Or is it worth changing the API soon so we could make a workaro= und in the frontend? 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 Aug 07 12:42:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 12:42: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 1XFN1Z-0000Uc-06; Thu, 07 Aug 2014 12:42:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFN1X-0000UW-8s for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 12:42:27 +0000 Received: from [193.109.254.147:27245] by server-4.bemta-14.messagelabs.com id 93/DD-23592-23473E35; Thu, 07 Aug 2014 12:42:26 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1407415344!14342790!1 X-Originating-IP: [209.85.214.169] 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 9942 invoked from network); 7 Aug 2014 12:42:25 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Aug 2014 12:42:25 -0000 Received: by mail-ob0-f169.google.com with SMTP id nu7so2865031obb.14 for ; Thu, 07 Aug 2014 05:42:23 -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=rSn8EU2yLEf5Vreu5Qv+L5tDRZAlc7l29cBnyJUyZYc=; b=PxGZICL86Sp1OUQRhAFeHOC+hPv/jI+VRxC5HF5eRlDglxVR/tCY4VzWVc8AdsLQS5 ZvfodP+FVt8LwMot/S2yJEp6td4UdWh5a3KZCxJvQJuZ7WAY8lmYdq40utHGWHvk85dX fjOJILBwVj2Wp14mrhf61/jIefIOrJgdEvwKIg+XCWCX9Ulp7ycAg/43p0zsG/+sgIGd mTXkntKJJmS+pc9L1zawW5e2rofXkFa3smT6bs4Viqfdi0KdqWZiLGMP8Wy/F4ZQ2t/s YFOpt8EKJWiWD2oJ6ZYYEw/1gT8HiC+faYXIW9S5TeTtuWoLy+QynO4O6SLpo0Pwg8+I 5z2A== MIME-Version: 1.0 X-Received: by 10.182.137.195 with SMTP id qk3mr3256488obb.5.1407415343720; Thu, 07 Aug 2014 05:42:23 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 7 Aug 2014 05:42:23 -0700 (PDT) In-Reply-To: <476A0FE5-67CC-439F-9E7D-1057B6D28AD7@citrix.com> References: <36D06E0F-8336-4142-80BF-29586554A9C5@nottingham.ac.uk> <53088F2B-1AC3-4D35-BB37-247337690798@nottingham.ac.uk> <5BD43696-D536-4690-A628-98C88C1A0479@citrix.com> <90A2FFCA-A5F3-44A4-AC9F-F31C1B04AD6E@recoil.org> <46605CC2-8C25-460E-9963-76DDC59B6802@recoil.org> <1C889C81-6EAA-4A21-AE47-6D825F6E93FB@citrix.com> <476A0FE5-67CC-439F-9E7D-1057B6D28AD7@citrix.com> Date: Thu, 7 Aug 2014 13:42:23 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] wireshark capture of failed download from mirage-www on ARM X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 T24gNyBBdWd1c3QgMjAxNCAxMzoyOSwgRGF2ZSBTY290dCA8RGF2ZS5TY290dEBjaXRyaXguY29t PiB3cm90ZToKPiBIaSwKPgo+IFNvcnJ5IGZvciB0aGUgZGVsYXkgcmVwbHlpbmchCj4KPiBPbiAz MSBKdWwgMjAxNCwgYXQgMTE6NDQsIFRob21hcyBMZW9uYXJkIDx0YWxleDVAZ21haWwuY29tPiB3 cm90ZToKPgo+PiBPbiAyNiBKdWx5IDIwMTQgMTA6MjcsIERhdmlkIFNjb3R0IDxzY290dC5kakBn bWFpbC5jb20+IHdyb3RlOgo+Pj4KPj4+Cj4+PiBPbiBTYXR1cmRheSwgSnVseSAyNiwgMjAxNCwg QW5pbCBNYWRoYXZhcGVkZHkgPGFuaWxAcmVjb2lsLm9yZz4gd3JvdGU6Cj4+Pj4KPj4+PiBPbiAy NSBKdWwgMjAxNCwgYXQgMDQ6NTQsIFRob21hcyBMZW9uYXJkIDx0YWxleDVAZ21haWwuY29tPiB3 cm90ZToKPj4+Pj4KPj4+Pj4gSGVyZSdzIGEgc2xpZ2h0bHkgYmV0dGVyIHdvcmstYXJvdW5kOgo+ Pj4+Pgo+Pj4+Pgo+Pj4+PiBodHRwczovL2dpdGh1Yi5jb20vdGFsZXg1L21pcmFnZS10Y3BpcC9j b21taXQvOWY3ZTBhNjI4ZWJkMWNlY2U3ZDBmYjk3OTI3M2E5NmJlNzgyMzNhZAo+Pj4+Pgo+Pj4+ PiBJdCBjaGFuZ2VzIHRoZSBUQ1AgcGFja2V0IHNwbGl0dGluZyBjb2RlIHNvIHRoYXQgdGhlIHNl Y29uZCBwYXJ0IG9mCj4+Pj4+IHRoZSBwYWdlIGlzIGNvcGllZCB0byBhIG5ldyBJTyBwYWdlLiBU aGlzIGF2b2lkcyBzZW5kaW5nIHRoZSBzYW1lCj4+Pj4+IHBoeXNpY2FsIHBhZ2UgdG8gTGludXgg dHdpY2UgKHdoaWNoIGlzIHdoYXQgZG9lc24ndCB3b3JrKS4KPj4+Pj4KPj4+Pj4gV2l0aCB0aGlz LCB0aGUgcHJldmlvdXMgaGFjayBjYW4gYmUgcmV2ZXJ0ZWQuCj4+Pj4+Cj4+Pj4+IEluIG15IHRl c3RpbmcsIHRoaXMgaW5jcmVhc2VkIHRoZSBzdHJlYW1pbmcgVENQIGRvd25sb2FkIHNwZWVkIGZy b20gNTYKPj4+Pj4gS0IvcyB0byAzLjkgTUIvcyBvbiB0aGUgQ3ViaWVUcnVjay4KPj4+Pgo+Pj4+ IFRoaXMgaXMgY2VydGFpbmx5IGEgZml4IHRoYXQgd29ya3MsIGJ1dCBJJ20gbG9hdGggdG8gaW5z ZXJ0IGFuIHVubmVjZXNzYXJ5Cj4+Pj4gY29weSBpbiB0aGUgVENQIHN0YWNrIGp1c3QgYmVjYXVz ZSBvZiBhIGxpbWl0YXRpb24gaW4gWGVuL0FSTSAodGhhdCB3aWxsCj4+Pj4gZ28KPj4+PiBhd2F5 IGluIFhlbiA0LjUsIEkgZXhwZWN0KS4KPj4+Pgo+Pj4+IENvdWxkIHdlIGtlZXAgdHJhY2sgb2Yg dGhlIGFjdGl2ZSBncmFudHMgaW4gdGhlIEdudHRhYiBsaWJhcnksIGFuZCBmb3JjZSBhCj4+Pj4g cGFnZSBkdXBsaWNhdGlvbiBhdCB0aGF0IHBvaW50IGluc3RlYWQ/ICBUaGF0IHdvdWxkIGZpeCBp dCBmb3IgYW55IG90aGVyCj4+Pj4gQ3N0cnVjdCBjb25zdW1lcnMgYXMgd2VsbCwgYW5kIGJlIGEg bW9yZSBsb2dpY2FsIHBsYWNlIHRvIGluc2VydCBYZW4KPj4+PiB2ZXJzaW9uIGRldGVjdGlvbiBp biB0aGUgZnV0dXJlIHRvIHJlbW92ZSB0aGUgZXh0cmEgY29weSBpZiBub3QgbmVlZGVkLgo+Pj4K Pj4+Cj4+PiBJZiB0aGUgcHJvYmxlbSBpcyBncmFudGluZyB0aGUgc2FtZSBwYWdlIHR3aWNlLCB3 b3VsZCBpdCBiZSBlbm91Z2ggdG8KPj4+IG1haW50YWluIGEgbWFwIG9mIHBhZ2UgYWRkcmVzcyB0 byAoZ3JhbnQgaW5kZXggKiByZWZvdW50KSwgYW5kIHRoZW4KPj4+ICJncmFudF9hY2Nlc3MiIGNv dWxkIHJldHVybiB0aGUgZXhpc3RpbmcgZ3JhbnQgaWQgYW5kIGJ1bXAgdGhlIHJlZmNvdW50PyBJ Cj4+PiB0aGluayB3ZSBqdXN0IG5lZWQgdG8gc2hhcmUgdGhlIGdyYW50LCByYXRoZXIgdGhhbiBk dXBsaWNhdGUgdGhlIHBhZ2UuIChJcwo+Pj4gdGhhdCByaWdodD8pCj4+Cj4+IEhvdyB3b3VsZCB0 aGF0IGZpdCBpbiB3aXRoIHRoZSBjdXJyZW50IEFQST8gSXQgbG9va3MgbGlrZSB5b3UgZmlyc3QK Pj4gYWxsb2NhdGUgYSBnbnRyZWYgKGFuIGludCkgYW5kIHRoZW4gdXNlIHRoYXQgdG8gc2hhcmUg dGhlIHBhZ2U6Cj4+Cj4+ICB2YWwgZ2V0IDogdW5pdCAtPiBnbnRyZWYgTHd0LnQKPj4KPj4gIHZh bCBncmFudF9hY2Nlc3MgOiBkb21pZDppbnQgLT4gd3JpdGFibGU6Ym9vbCAtPiBnbnRyZWYgLT4g SW9fcGFnZS50IC0+IHVuaXQKPgo+IFllYWggbG9va2luZyBhdCBpdCBJIHRoaW5rIHRoYXQgaW50 ZXJmYWNlIGlzIGEgYml0IHRvbyDigJhyYXfigJkuIFVuZm9ydHVuYXRlbHkg4oCYdHlwZSBnbnRy ZWYgPSBpbnTigJkgaW4gdGhlIGludGVyZmFjZSBzbyBjbGllbnRzIGFyZSBmcmVlIHRvIGRvIHRo aW5ncyBsaWtlCj4gYGBgCj4gICAgICAgICAgaWdub3JlKFJYLlByb3RvXzY0LndyaXRlIH5pZCB+ Z3JlZjooSW50MzIub2ZfaW50IGdyZWYpIHNsb3QpCj4gYGBgCj4gSSBoYWQgYmVlbiBob3Bpbmcg dG8gZXhwbG9pdCB0aGUgb2JzZXJ2YXRpb24gdGhhdCAoSSB0aGluayBhbGwpIHVzZXJzIGNhbGwg 4oCYZ3JhbnRfYWNjZXNz4oCZIGJlZm9yZSBzZXJpYWxpc2luZyB0aGUgZ3JhbnQgcmVmZXJlbmNl IGludG8gdGhlIHJpbmcgbWV0YWRhdGEgc2xvdC4gTXkgZXZpbC9jdW5uaW5nIHBsYW4gaGFkIGJl ZW4gdG8gYWxsb2NhdGUgYSBmcmVzaCBncmFudCBpbiDigJhnZXQoKeKAmSBhcyBub3JtYWwsIGJ1 dCB0aGVuIHN3aXp6bGUgaXQgaW5zaWRlIOKAmGdyYW50X2FjY2Vzc+KAmSBpZiBpdCB0dXJucyBv dXQgdGhhdCBhIGdyYW50IGhhcyBhbHJlYWR5IGJlZW4gYWxsb2NhdGVkIGluIHRoYXQgcGFnZS4g SG93ZXZlciBJIHdvdWxkIG5lZWQgdG8gY2hhbmdlIHRoZSBpbXBsZW1lbnRhdGlvbiBvZiDigJh0 eXBlIGdudHJlZuKAmSB0byBtYWtlIHRoaXMgd29yayA6LSgKPgo+IEFueXdheSwgbG9va2luZyBh dCB0aGUgY3VycmVudCB1c2VycyBpbiBtaXJhZ2Ute2Jsb2NrLG5ldH0teGVuLCBJIGNhbiBzZWUg MiB1c2VycyBvZiB0aGUgbG93LWxldmVsIEFQSToKPgo+ICAgMS4gZ3JhbnRpbmcgYWNjZXNzIHRv IHRoZSBtZXRhZGF0YSByaW5nIG9uIHN0YXJ0dXAgZS5nLgo+IGBgYAo+IGxldCBhbGxvY2F0ZV9y aW5nIH5kb21pZCA9Cj4gICBsZXQgcGFnZSA9IElvX3BhZ2UuZ2V0IDEgaW4KPiAgIGxldCB4ID0g SW9fcGFnZS50b19jc3RydWN0IHBhZ2UgaW4KPiAgIGx3dCBnbnQgPSBHbnQuR250c2hyLmdldCAo KSBpbgo+ICAgZm9yIGkgPSAwIHRvIENzdHJ1Y3QubGVuIHggLSAxIGRvCj4gICAgIENzdHJ1Y3Qu c2V0X3VpbnQ4IHggaSAwCj4gICBkb25lOwo+ICAgR250LkdudHNoci5ncmFudF9hY2Nlc3MgfmRv bWlkIH53cml0YWJsZTp0cnVlIGdudCBwYWdlOwo+ICAgcmV0dXJuIChnbnQsIHgpCj4gYGBgCj4g ICAyLiBncmFudGluZyBhY2Nlc3MgdG8gcGFnZXMgZm9yIEkvTyBlLmcuCj4gYGBgCj4gbGV0IHJl ZmlsbF9yZXF1ZXN0cyBuZiA9Cj4gICBsZXQgbnVtID0gUmluZy5ScGMuRnJvbnQuZ2V0X2ZyZWVf cmVxdWVzdHMgbmYucnhfZnJpbmcgaW4KPiAgIGlmIG51bSA+IDAgdGhlbgo+ICAgICBsd3QgZ3Jl ZnMgPSBHbnQuR250c2hyLmdldF9uIG51bSBpbgo+ICAgICBsZXQgcGFnZXMgPSBJb19wYWdlLnBh Z2VzIG51bSBpbgo+ICAgICBMaXN0Lml0ZXIKPiAgICAgICAoZnVuIChncmVmLCBwYWdlKSAtPgo+ ICAgICAgICAgIGxldCBpZCA9IGdyZWYgbW9kICgxIGxzbCAxNikgaW4KPiAgICAgICAgICBHbnQu R250c2hyLmdyYW50X2FjY2VzcyB+ZG9taWQ6bmYuYmFja2VuZF9pZCB+d3JpdGFibGU6dHJ1ZSBn cmVmIHBhZ2U7Cj4gICAgICAgICAgSGFzaHRibC5hZGQgbmYucnhfbWFwIGlkIChncmVmLCBwYWdl KTsKPiAgICAgICAgICBsZXQgc2xvdF9pZCA9IFJpbmcuUnBjLkZyb250Lm5leHRfcmVxX2lkIG5m LnJ4X2ZyaW5nIGluCj4gICAgICAgICAgbGV0IHNsb3QgPSBSaW5nLlJwYy5Gcm9udC5zbG90IG5m LnJ4X2ZyaW5nIHNsb3RfaWQgaW4KPiAgICAgICAgICBpZ25vcmUoUlguUHJvdG9fNjQud3JpdGUg fmlkIH5ncmVmOihJbnQzMi5vZl9pbnQgZ3JlZikgc2xvdCkKPiAgICAgICApIChMaXN0LmNvbWJp bmUgZ3JlZnMgcGFnZXMpOwo+ICAgICBpZiBSaW5nLlJwYy5Gcm9udC5wdXNoX3JlcXVlc3RzX2Fu ZF9jaGVja19ub3RpZnkgbmYucnhfZnJpbmcKPiAgICAgdGhlbiBub3RpZnkgbmYgKCk7Cj4gICAg IHJldHVybiAoKQo+ICAgZWxzZSByZXR1cm4gKCkKPiBgYGAKPgo+IFdl4oCZdmUgYWxyZWFkeSBn b3QgYSDigJh3aXRoX2dyYW50c+KAmSBmdW5jdGlvbiBidXQgdGhpcyBkb2VzbuKAmXQgd29yayBm b3IgdGhlc2UgY2FzZXMgYmVjYXVzZSB0aGV5IGJvdGggd2FudCB0byDigJhsZWFr4oCZIHRoZSBn cmFudHMgKHRoZXkgYXJlIGNsZWFuZWQgdXAgZWxzZXdoZXJlKS4gUGVyaGFwcyB3ZSBzaG91bGQg bWFrZSBhbiBBUEkgKOKAmHJldHVybl9ncmFudHPigJkg4oCYYWxsb2NfZ3JhbnRz4oCZPykgd2hp Y2ggY29tYmluZXMg4oCYZ2V0X27igJkgYW5kIOKAmGdyYW50X2FjY2Vzc+KAmT8KPgo+IERvIHlv dSBrbm93IGlmIHRoZSBidWcgaXMgbGlrZWx5IHRvIGJlIGZpeGVkIGluIHRoZSBiYWNrZW5kIGlu IGEgcmVhc29uYWJsZSB0aW1lZnJhbWU/IE9yIGlzIGl0IHdvcnRoIGNoYW5naW5nIHRoZSBBUEkg c29vbiBzbyB3ZSBjb3VsZCBtYWtlIGEgd29ya2Fyb3VuZCBpbiB0aGUgZnJvbnRlbmQ/CgpUaGVy ZSBhcmUgcGF0Y2hlcyBhZ2FpbnN0IFhlbiA0LjUgd2hpY2ggdGhleSdyZSBjdXJyZW50bHkgYmFj ay1wb3J0aW5nCnRvIFhlbiA0LjQuIEkndmUgdXBkYXRlZCB4ZW4tYXJtLWJ1aWxkZXIgdG8gdXNl IHRoZSBwYXRjaGVkIHZlcnNpb25zCm9mIFhlbiBhbmQgTGludXggYW5kIHJlYnVpbHQgdGhlIFNE IGNhcmQgaW1hZ2VzOgoKICBodHRwczovL2dpdGh1Yi5jb20vbWlyYWdlL3hlbi1hcm0tYnVpbGRl cgoKSG93ZXZlciwgdGhlcmUgYXJlIHNvbWUgcmFjZSBjb25kaXRpb25zIGluIHRoZSBuZXcgY29k ZSB0aGF0IHNlZW0gdG8KYmUgdHJpZ2dlcmVkIGlmIE1pcmFnZSBib290cyBhbmQgdGhlbiBleGl0 cyBxdWlja2x5LiBJJ20gdGVzdGluZwp2YXJpb3VzIHBhdGNoZXMgdGhleSdyZSBzZW5kaW5nOyBz ZWUgdGhpcyB0aHJlYWQ6CgogIGh0dHA6Ly9saXN0cy54ZW4ub3JnL2FyY2hpdmVzL2h0bWwveGVu LWRldmVsLzIwMTQtMDgvbXNnMDAwNTMuaHRtbAoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAgICAg ICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYgIDhC OUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAgQkQ4 RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxA bGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4v bWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 12:42:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 12:42: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 1XFN1Z-0000Uc-06; Thu, 07 Aug 2014 12:42:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFN1X-0000UW-8s for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 12:42:27 +0000 Received: from [193.109.254.147:27245] by server-4.bemta-14.messagelabs.com id 93/DD-23592-23473E35; Thu, 07 Aug 2014 12:42:26 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-27.messagelabs.com!1407415344!14342790!1 X-Originating-IP: [209.85.214.169] 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 9942 invoked from network); 7 Aug 2014 12:42:25 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 7 Aug 2014 12:42:25 -0000 Received: by mail-ob0-f169.google.com with SMTP id nu7so2865031obb.14 for ; Thu, 07 Aug 2014 05:42:23 -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=rSn8EU2yLEf5Vreu5Qv+L5tDRZAlc7l29cBnyJUyZYc=; b=PxGZICL86Sp1OUQRhAFeHOC+hPv/jI+VRxC5HF5eRlDglxVR/tCY4VzWVc8AdsLQS5 ZvfodP+FVt8LwMot/S2yJEp6td4UdWh5a3KZCxJvQJuZ7WAY8lmYdq40utHGWHvk85dX fjOJILBwVj2Wp14mrhf61/jIefIOrJgdEvwKIg+XCWCX9Ulp7ycAg/43p0zsG/+sgIGd mTXkntKJJmS+pc9L1zawW5e2rofXkFa3smT6bs4Viqfdi0KdqWZiLGMP8Wy/F4ZQ2t/s YFOpt8EKJWiWD2oJ6ZYYEw/1gT8HiC+faYXIW9S5TeTtuWoLy+QynO4O6SLpo0Pwg8+I 5z2A== MIME-Version: 1.0 X-Received: by 10.182.137.195 with SMTP id qk3mr3256488obb.5.1407415343720; Thu, 07 Aug 2014 05:42:23 -0700 (PDT) Received: by 10.76.92.5 with HTTP; Thu, 7 Aug 2014 05:42:23 -0700 (PDT) In-Reply-To: <476A0FE5-67CC-439F-9E7D-1057B6D28AD7@citrix.com> References: <36D06E0F-8336-4142-80BF-29586554A9C5@nottingham.ac.uk> <53088F2B-1AC3-4D35-BB37-247337690798@nottingham.ac.uk> <5BD43696-D536-4690-A628-98C88C1A0479@citrix.com> <90A2FFCA-A5F3-44A4-AC9F-F31C1B04AD6E@recoil.org> <46605CC2-8C25-460E-9963-76DDC59B6802@recoil.org> <1C889C81-6EAA-4A21-AE47-6D825F6E93FB@citrix.com> <476A0FE5-67CC-439F-9E7D-1057B6D28AD7@citrix.com> Date: Thu, 7 Aug 2014 13:42:23 +0100 Message-ID: From: Thomas Leonard To: Dave Scott Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] wireshark capture of failed download from mirage-www on ARM X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 T24gNyBBdWd1c3QgMjAxNCAxMzoyOSwgRGF2ZSBTY290dCA8RGF2ZS5TY290dEBjaXRyaXguY29t PiB3cm90ZToKPiBIaSwKPgo+IFNvcnJ5IGZvciB0aGUgZGVsYXkgcmVwbHlpbmchCj4KPiBPbiAz MSBKdWwgMjAxNCwgYXQgMTE6NDQsIFRob21hcyBMZW9uYXJkIDx0YWxleDVAZ21haWwuY29tPiB3 cm90ZToKPgo+PiBPbiAyNiBKdWx5IDIwMTQgMTA6MjcsIERhdmlkIFNjb3R0IDxzY290dC5kakBn bWFpbC5jb20+IHdyb3RlOgo+Pj4KPj4+Cj4+PiBPbiBTYXR1cmRheSwgSnVseSAyNiwgMjAxNCwg QW5pbCBNYWRoYXZhcGVkZHkgPGFuaWxAcmVjb2lsLm9yZz4gd3JvdGU6Cj4+Pj4KPj4+PiBPbiAy NSBKdWwgMjAxNCwgYXQgMDQ6NTQsIFRob21hcyBMZW9uYXJkIDx0YWxleDVAZ21haWwuY29tPiB3 cm90ZToKPj4+Pj4KPj4+Pj4gSGVyZSdzIGEgc2xpZ2h0bHkgYmV0dGVyIHdvcmstYXJvdW5kOgo+ Pj4+Pgo+Pj4+Pgo+Pj4+PiBodHRwczovL2dpdGh1Yi5jb20vdGFsZXg1L21pcmFnZS10Y3BpcC9j b21taXQvOWY3ZTBhNjI4ZWJkMWNlY2U3ZDBmYjk3OTI3M2E5NmJlNzgyMzNhZAo+Pj4+Pgo+Pj4+ PiBJdCBjaGFuZ2VzIHRoZSBUQ1AgcGFja2V0IHNwbGl0dGluZyBjb2RlIHNvIHRoYXQgdGhlIHNl Y29uZCBwYXJ0IG9mCj4+Pj4+IHRoZSBwYWdlIGlzIGNvcGllZCB0byBhIG5ldyBJTyBwYWdlLiBU aGlzIGF2b2lkcyBzZW5kaW5nIHRoZSBzYW1lCj4+Pj4+IHBoeXNpY2FsIHBhZ2UgdG8gTGludXgg dHdpY2UgKHdoaWNoIGlzIHdoYXQgZG9lc24ndCB3b3JrKS4KPj4+Pj4KPj4+Pj4gV2l0aCB0aGlz LCB0aGUgcHJldmlvdXMgaGFjayBjYW4gYmUgcmV2ZXJ0ZWQuCj4+Pj4+Cj4+Pj4+IEluIG15IHRl c3RpbmcsIHRoaXMgaW5jcmVhc2VkIHRoZSBzdHJlYW1pbmcgVENQIGRvd25sb2FkIHNwZWVkIGZy b20gNTYKPj4+Pj4gS0IvcyB0byAzLjkgTUIvcyBvbiB0aGUgQ3ViaWVUcnVjay4KPj4+Pgo+Pj4+ IFRoaXMgaXMgY2VydGFpbmx5IGEgZml4IHRoYXQgd29ya3MsIGJ1dCBJJ20gbG9hdGggdG8gaW5z ZXJ0IGFuIHVubmVjZXNzYXJ5Cj4+Pj4gY29weSBpbiB0aGUgVENQIHN0YWNrIGp1c3QgYmVjYXVz ZSBvZiBhIGxpbWl0YXRpb24gaW4gWGVuL0FSTSAodGhhdCB3aWxsCj4+Pj4gZ28KPj4+PiBhd2F5 IGluIFhlbiA0LjUsIEkgZXhwZWN0KS4KPj4+Pgo+Pj4+IENvdWxkIHdlIGtlZXAgdHJhY2sgb2Yg dGhlIGFjdGl2ZSBncmFudHMgaW4gdGhlIEdudHRhYiBsaWJhcnksIGFuZCBmb3JjZSBhCj4+Pj4g cGFnZSBkdXBsaWNhdGlvbiBhdCB0aGF0IHBvaW50IGluc3RlYWQ/ICBUaGF0IHdvdWxkIGZpeCBp dCBmb3IgYW55IG90aGVyCj4+Pj4gQ3N0cnVjdCBjb25zdW1lcnMgYXMgd2VsbCwgYW5kIGJlIGEg bW9yZSBsb2dpY2FsIHBsYWNlIHRvIGluc2VydCBYZW4KPj4+PiB2ZXJzaW9uIGRldGVjdGlvbiBp biB0aGUgZnV0dXJlIHRvIHJlbW92ZSB0aGUgZXh0cmEgY29weSBpZiBub3QgbmVlZGVkLgo+Pj4K Pj4+Cj4+PiBJZiB0aGUgcHJvYmxlbSBpcyBncmFudGluZyB0aGUgc2FtZSBwYWdlIHR3aWNlLCB3 b3VsZCBpdCBiZSBlbm91Z2ggdG8KPj4+IG1haW50YWluIGEgbWFwIG9mIHBhZ2UgYWRkcmVzcyB0 byAoZ3JhbnQgaW5kZXggKiByZWZvdW50KSwgYW5kIHRoZW4KPj4+ICJncmFudF9hY2Nlc3MiIGNv dWxkIHJldHVybiB0aGUgZXhpc3RpbmcgZ3JhbnQgaWQgYW5kIGJ1bXAgdGhlIHJlZmNvdW50PyBJ Cj4+PiB0aGluayB3ZSBqdXN0IG5lZWQgdG8gc2hhcmUgdGhlIGdyYW50LCByYXRoZXIgdGhhbiBk dXBsaWNhdGUgdGhlIHBhZ2UuIChJcwo+Pj4gdGhhdCByaWdodD8pCj4+Cj4+IEhvdyB3b3VsZCB0 aGF0IGZpdCBpbiB3aXRoIHRoZSBjdXJyZW50IEFQST8gSXQgbG9va3MgbGlrZSB5b3UgZmlyc3QK Pj4gYWxsb2NhdGUgYSBnbnRyZWYgKGFuIGludCkgYW5kIHRoZW4gdXNlIHRoYXQgdG8gc2hhcmUg dGhlIHBhZ2U6Cj4+Cj4+ICB2YWwgZ2V0IDogdW5pdCAtPiBnbnRyZWYgTHd0LnQKPj4KPj4gIHZh bCBncmFudF9hY2Nlc3MgOiBkb21pZDppbnQgLT4gd3JpdGFibGU6Ym9vbCAtPiBnbnRyZWYgLT4g SW9fcGFnZS50IC0+IHVuaXQKPgo+IFllYWggbG9va2luZyBhdCBpdCBJIHRoaW5rIHRoYXQgaW50 ZXJmYWNlIGlzIGEgYml0IHRvbyDigJhyYXfigJkuIFVuZm9ydHVuYXRlbHkg4oCYdHlwZSBnbnRy ZWYgPSBpbnTigJkgaW4gdGhlIGludGVyZmFjZSBzbyBjbGllbnRzIGFyZSBmcmVlIHRvIGRvIHRo aW5ncyBsaWtlCj4gYGBgCj4gICAgICAgICAgaWdub3JlKFJYLlByb3RvXzY0LndyaXRlIH5pZCB+ Z3JlZjooSW50MzIub2ZfaW50IGdyZWYpIHNsb3QpCj4gYGBgCj4gSSBoYWQgYmVlbiBob3Bpbmcg dG8gZXhwbG9pdCB0aGUgb2JzZXJ2YXRpb24gdGhhdCAoSSB0aGluayBhbGwpIHVzZXJzIGNhbGwg 4oCYZ3JhbnRfYWNjZXNz4oCZIGJlZm9yZSBzZXJpYWxpc2luZyB0aGUgZ3JhbnQgcmVmZXJlbmNl IGludG8gdGhlIHJpbmcgbWV0YWRhdGEgc2xvdC4gTXkgZXZpbC9jdW5uaW5nIHBsYW4gaGFkIGJl ZW4gdG8gYWxsb2NhdGUgYSBmcmVzaCBncmFudCBpbiDigJhnZXQoKeKAmSBhcyBub3JtYWwsIGJ1 dCB0aGVuIHN3aXp6bGUgaXQgaW5zaWRlIOKAmGdyYW50X2FjY2Vzc+KAmSBpZiBpdCB0dXJucyBv dXQgdGhhdCBhIGdyYW50IGhhcyBhbHJlYWR5IGJlZW4gYWxsb2NhdGVkIGluIHRoYXQgcGFnZS4g SG93ZXZlciBJIHdvdWxkIG5lZWQgdG8gY2hhbmdlIHRoZSBpbXBsZW1lbnRhdGlvbiBvZiDigJh0 eXBlIGdudHJlZuKAmSB0byBtYWtlIHRoaXMgd29yayA6LSgKPgo+IEFueXdheSwgbG9va2luZyBh dCB0aGUgY3VycmVudCB1c2VycyBpbiBtaXJhZ2Ute2Jsb2NrLG5ldH0teGVuLCBJIGNhbiBzZWUg MiB1c2VycyBvZiB0aGUgbG93LWxldmVsIEFQSToKPgo+ICAgMS4gZ3JhbnRpbmcgYWNjZXNzIHRv IHRoZSBtZXRhZGF0YSByaW5nIG9uIHN0YXJ0dXAgZS5nLgo+IGBgYAo+IGxldCBhbGxvY2F0ZV9y aW5nIH5kb21pZCA9Cj4gICBsZXQgcGFnZSA9IElvX3BhZ2UuZ2V0IDEgaW4KPiAgIGxldCB4ID0g SW9fcGFnZS50b19jc3RydWN0IHBhZ2UgaW4KPiAgIGx3dCBnbnQgPSBHbnQuR250c2hyLmdldCAo KSBpbgo+ICAgZm9yIGkgPSAwIHRvIENzdHJ1Y3QubGVuIHggLSAxIGRvCj4gICAgIENzdHJ1Y3Qu c2V0X3VpbnQ4IHggaSAwCj4gICBkb25lOwo+ICAgR250LkdudHNoci5ncmFudF9hY2Nlc3MgfmRv bWlkIH53cml0YWJsZTp0cnVlIGdudCBwYWdlOwo+ICAgcmV0dXJuIChnbnQsIHgpCj4gYGBgCj4g ICAyLiBncmFudGluZyBhY2Nlc3MgdG8gcGFnZXMgZm9yIEkvTyBlLmcuCj4gYGBgCj4gbGV0IHJl ZmlsbF9yZXF1ZXN0cyBuZiA9Cj4gICBsZXQgbnVtID0gUmluZy5ScGMuRnJvbnQuZ2V0X2ZyZWVf cmVxdWVzdHMgbmYucnhfZnJpbmcgaW4KPiAgIGlmIG51bSA+IDAgdGhlbgo+ICAgICBsd3QgZ3Jl ZnMgPSBHbnQuR250c2hyLmdldF9uIG51bSBpbgo+ICAgICBsZXQgcGFnZXMgPSBJb19wYWdlLnBh Z2VzIG51bSBpbgo+ICAgICBMaXN0Lml0ZXIKPiAgICAgICAoZnVuIChncmVmLCBwYWdlKSAtPgo+ ICAgICAgICAgIGxldCBpZCA9IGdyZWYgbW9kICgxIGxzbCAxNikgaW4KPiAgICAgICAgICBHbnQu R250c2hyLmdyYW50X2FjY2VzcyB+ZG9taWQ6bmYuYmFja2VuZF9pZCB+d3JpdGFibGU6dHJ1ZSBn cmVmIHBhZ2U7Cj4gICAgICAgICAgSGFzaHRibC5hZGQgbmYucnhfbWFwIGlkIChncmVmLCBwYWdl KTsKPiAgICAgICAgICBsZXQgc2xvdF9pZCA9IFJpbmcuUnBjLkZyb250Lm5leHRfcmVxX2lkIG5m LnJ4X2ZyaW5nIGluCj4gICAgICAgICAgbGV0IHNsb3QgPSBSaW5nLlJwYy5Gcm9udC5zbG90IG5m LnJ4X2ZyaW5nIHNsb3RfaWQgaW4KPiAgICAgICAgICBpZ25vcmUoUlguUHJvdG9fNjQud3JpdGUg fmlkIH5ncmVmOihJbnQzMi5vZl9pbnQgZ3JlZikgc2xvdCkKPiAgICAgICApIChMaXN0LmNvbWJp bmUgZ3JlZnMgcGFnZXMpOwo+ICAgICBpZiBSaW5nLlJwYy5Gcm9udC5wdXNoX3JlcXVlc3RzX2Fu ZF9jaGVja19ub3RpZnkgbmYucnhfZnJpbmcKPiAgICAgdGhlbiBub3RpZnkgbmYgKCk7Cj4gICAg IHJldHVybiAoKQo+ICAgZWxzZSByZXR1cm4gKCkKPiBgYGAKPgo+IFdl4oCZdmUgYWxyZWFkeSBn b3QgYSDigJh3aXRoX2dyYW50c+KAmSBmdW5jdGlvbiBidXQgdGhpcyBkb2VzbuKAmXQgd29yayBm b3IgdGhlc2UgY2FzZXMgYmVjYXVzZSB0aGV5IGJvdGggd2FudCB0byDigJhsZWFr4oCZIHRoZSBn cmFudHMgKHRoZXkgYXJlIGNsZWFuZWQgdXAgZWxzZXdoZXJlKS4gUGVyaGFwcyB3ZSBzaG91bGQg bWFrZSBhbiBBUEkgKOKAmHJldHVybl9ncmFudHPigJkg4oCYYWxsb2NfZ3JhbnRz4oCZPykgd2hp Y2ggY29tYmluZXMg4oCYZ2V0X27igJkgYW5kIOKAmGdyYW50X2FjY2Vzc+KAmT8KPgo+IERvIHlv dSBrbm93IGlmIHRoZSBidWcgaXMgbGlrZWx5IHRvIGJlIGZpeGVkIGluIHRoZSBiYWNrZW5kIGlu IGEgcmVhc29uYWJsZSB0aW1lZnJhbWU/IE9yIGlzIGl0IHdvcnRoIGNoYW5naW5nIHRoZSBBUEkg c29vbiBzbyB3ZSBjb3VsZCBtYWtlIGEgd29ya2Fyb3VuZCBpbiB0aGUgZnJvbnRlbmQ/CgpUaGVy ZSBhcmUgcGF0Y2hlcyBhZ2FpbnN0IFhlbiA0LjUgd2hpY2ggdGhleSdyZSBjdXJyZW50bHkgYmFj ay1wb3J0aW5nCnRvIFhlbiA0LjQuIEkndmUgdXBkYXRlZCB4ZW4tYXJtLWJ1aWxkZXIgdG8gdXNl IHRoZSBwYXRjaGVkIHZlcnNpb25zCm9mIFhlbiBhbmQgTGludXggYW5kIHJlYnVpbHQgdGhlIFNE IGNhcmQgaW1hZ2VzOgoKICBodHRwczovL2dpdGh1Yi5jb20vbWlyYWdlL3hlbi1hcm0tYnVpbGRl cgoKSG93ZXZlciwgdGhlcmUgYXJlIHNvbWUgcmFjZSBjb25kaXRpb25zIGluIHRoZSBuZXcgY29k ZSB0aGF0IHNlZW0gdG8KYmUgdHJpZ2dlcmVkIGlmIE1pcmFnZSBib290cyBhbmQgdGhlbiBleGl0 cyBxdWlja2x5LiBJJ20gdGVzdGluZwp2YXJpb3VzIHBhdGNoZXMgdGhleSdyZSBzZW5kaW5nOyBz ZWUgdGhpcyB0aHJlYWQ6CgogIGh0dHA6Ly9saXN0cy54ZW4ub3JnL2FyY2hpdmVzL2h0bWwveGVu LWRldmVsLzIwMTQtMDgvbXNnMDAwNTMuaHRtbAoKCi0tIApEciBUaG9tYXMgTGVvbmFyZCAgICAg ICAgaHR0cDovLzBpbnN0YWxsLm5ldC8KR1BHOiA5MjQyIDk4MDcgQzk4NSAzQzA3IDQ0QTYgIDhC OUEgQUUwNyA4MjgwIDU5QTUgM0NDMQpHUEc6IERBOTggMjVBRSBDQUQwIDg5NzUgN0NEQSAgQkQ4 RSAwNzEzIDNGOTYgQ0E3NCBEOEJBCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxA bGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4v bWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 13:04:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 13:04: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 1XFNMl-00014o-1A; Thu, 07 Aug 2014 13:04:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFNMj-00014i-Rg for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 13:04:21 +0000 Received: from [85.158.139.211:30423] by server-3.bemta-5.messagelabs.com id 7A/E7-13873-55973E35; Thu, 07 Aug 2014 13:04:21 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-12.tower-206.messagelabs.com!1407416660!12422009!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 7481 invoked from network); 7 Aug 2014 13:04:20 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Aug 2014 13:04:20 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-155-62.eduroam.wireless.private.cam.ac.uk ([172.17.155.62]:54564) 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 1XFNMi-0007BL-QU (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 07 Aug 2014 14:04:20 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> Date: Thu, 7 Aug 2014 14:04:19 +0100 Message-Id: <8FC1C2B0-F316-4CD2-887F-DC9123FF27E3@cam.ac.uk> References: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call, Thursday 7th 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 Dear all, Due to an unforeseen clash, our GoToMeeting room will be unavailable for the call today. Instead, I will set up a Google Hangout [1] and send the link to this list shortly before the call. Apologies for the inconvenience! [1] https://www.google.com/+/learnmore/hangouts/index.html Best wishes, Amir On 5 Aug 2014, at 11:16, Amir Chaudhry wrote: > Dear all, > > The Mirage call will take place on *Thursday 7th* at 4pm BST (== GMT + 1). Note the change of day for this week (again)! > > If you have points you'd like to discuss, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: > > +1 (213) 493-0008 > > Thanks, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 13:04:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 13:04: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 1XFNMl-00014o-1A; Thu, 07 Aug 2014 13:04:23 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFNMj-00014i-Rg for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 13:04:21 +0000 Received: from [85.158.139.211:30423] by server-3.bemta-5.messagelabs.com id 7A/E7-13873-55973E35; Thu, 07 Aug 2014 13:04:21 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-12.tower-206.messagelabs.com!1407416660!12422009!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 7481 invoked from network); 7 Aug 2014 13:04:20 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Aug 2014 13:04:20 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-155-62.eduroam.wireless.private.cam.ac.uk ([172.17.155.62]:54564) 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 1XFNMi-0007BL-QU (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 07 Aug 2014 14:04:20 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> Date: Thu, 7 Aug 2014 14:04:19 +0100 Message-Id: <8FC1C2B0-F316-4CD2-887F-DC9123FF27E3@cam.ac.uk> References: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call, Thursday 7th 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 Dear all, Due to an unforeseen clash, our GoToMeeting room will be unavailable for the call today. Instead, I will set up a Google Hangout [1] and send the link to this list shortly before the call. Apologies for the inconvenience! [1] https://www.google.com/+/learnmore/hangouts/index.html Best wishes, Amir On 5 Aug 2014, at 11:16, Amir Chaudhry wrote: > Dear all, > > The Mirage call will take place on *Thursday 7th* at 4pm BST (== GMT + 1). Note the change of day for this week (again)! > > If you have points you'd like to discuss, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: > > +1 (213) 493-0008 > > Thanks, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 14:56:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 14:56:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFP7A-00053U-Vw; Thu, 07 Aug 2014 14:56:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFP79-00053J-Sy for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 14:56:24 +0000 Received: from [85.158.139.211:32555] by server-7.bemta-5.messagelabs.com id 60/32-30869-79393E35; Thu, 07 Aug 2014 14:56:23 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1407423382!9584664!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 28935 invoked from network); 7 Aug 2014 14:56:22 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Aug 2014 14:56:22 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-155-62.eduroam.wireless.private.cam.ac.uk ([172.17.155.62]:55772) 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 1XFP78-0005WT-QK (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 07 Aug 2014 15:56:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <8FC1C2B0-F316-4CD2-887F-DC9123FF27E3@cam.ac.uk> Date: Thu, 7 Aug 2014 15:56:21 +0100 Message-Id: <5927E39C-6DD1-49F0-94E0-9F0C0BC04020@cam.ac.uk> References: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> <8FC1C2B0-F316-4CD2-887F-DC9123FF27E3@cam.ac.uk> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call, Thursday 7th 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 Dear all, The link for the Hangout is: https://plus.google.com/hangouts/_/eqdf7dbymspsotubdrv3ttgw7mb (I'm the only person here are the moment) Best wishes, Amir On 7 Aug 2014, at 14:04, Amir Chaudhry wrote: > Dear all, > > Due to an unforeseen clash, our GoToMeeting room will be unavailable for the call today. > Instead, I will set up a Google Hangout [1] and send the link to this list shortly before the call. > > Apologies for the inconvenience! > > [1] https://www.google.com/+/learnmore/hangouts/index.html > > Best wishes, > Amir > > On 5 Aug 2014, at 11:16, Amir Chaudhry wrote: > >> Dear all, >> >> The Mirage call will take place on *Thursday 7th* at 4pm BST (== GMT + 1). Note the change of day for this week (again)! >> >> If you have points you'd like to discuss, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. >> >> 1. Please join my meeting. >> https://www1.gotomeeting.com/join/591890401 >> >> Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: >> >> +1 (213) 493-0008 >> >> Thanks, >> Amir > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Aug 07 14:56:28 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 07 Aug 2014 14:56:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFP7A-00053U-Vw; Thu, 07 Aug 2014 14:56:24 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XFP79-00053J-Sy for mirageos-devel@lists.xenproject.org; Thu, 07 Aug 2014 14:56:24 +0000 Received: from [85.158.139.211:32555] by server-7.bemta-5.messagelabs.com id 60/32-30869-79393E35; Thu, 07 Aug 2014 14:56:23 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1407423382!9584664!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 28935 invoked from network); 7 Aug 2014 14:56:22 -0000 Received: from ppsw-41.csi.cam.ac.uk (HELO ppsw-41.csi.cam.ac.uk) (131.111.8.141) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Aug 2014 14:56:22 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-155-62.eduroam.wireless.private.cam.ac.uk ([172.17.155.62]:55772) 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 1XFP78-0005WT-QK (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Thu, 07 Aug 2014 15:56:22 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <8FC1C2B0-F316-4CD2-887F-DC9123FF27E3@cam.ac.uk> Date: Thu, 7 Aug 2014 15:56:21 +0100 Message-Id: <5927E39C-6DD1-49F0-94E0-9F0C0BC04020@cam.ac.uk> References: <3B9D6A4B-4E56-4AC6-AA82-9953EB0C7D3C@cam.ac.uk> <8FC1C2B0-F316-4CD2-887F-DC9123FF27E3@cam.ac.uk> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call, Thursday 7th 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 Dear all, The link for the Hangout is: https://plus.google.com/hangouts/_/eqdf7dbymspsotubdrv3ttgw7mb (I'm the only person here are the moment) Best wishes, Amir On 7 Aug 2014, at 14:04, Amir Chaudhry wrote: > Dear all, > > Due to an unforeseen clash, our GoToMeeting room will be unavailable for the call today. > Instead, I will set up a Google Hangout [1] and send the link to this list shortly before the call. > > Apologies for the inconvenience! > > [1] https://www.google.com/+/learnmore/hangouts/index.html > > Best wishes, > Amir > > On 5 Aug 2014, at 11:16, Amir Chaudhry wrote: > >> Dear all, >> >> The Mirage call will take place on *Thursday 7th* at 4pm BST (== GMT + 1). Note the change of day for this week (again)! >> >> If you have points you'd like to discuss, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. >> >> 1. Please join my meeting. >> https://www1.gotomeeting.com/join/591890401 >> >> Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: >> >> +1 (213) 493-0008 >> >> Thanks, >> Amir > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Aug 09 13:19:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 09 Aug 2014 13:19:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XG6YN-0003X1-Ck; Sat, 09 Aug 2014 13:19:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XG6YM-0003Ww-Lu for mirageos-devel@lists.xenproject.org; Sat, 09 Aug 2014 13:19:22 +0000 Received: from [193.109.254.147:28160] by server-10.bemta-14.messagelabs.com id D9/92-06615-9DF16E35; Sat, 09 Aug 2014 13:19:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1407590360!14721099!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10037 invoked from network); 9 Aug 2014 13:19:20 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 9 Aug 2014 13:19:20 -0000 Received: (qmail 29997 invoked by uid 634); 9 Aug 2014 13:19:19 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from 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; Sat, 09 Aug 2014 14:19:16 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> Date: Sat, 9 Aug 2014 14:19:15 +0100 Message-Id: <0A33B920-A42D-4013-9BE9-9B0E4DE158CB@recoil.org> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> To: Gilles DALMAS 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] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8938188165890803727==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8938188165890803727== Content-Type: multipart/alternative; boundary="Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D" --Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I'm afraid not. HVM is specifically a set of hardware extensions to x86 = to permit it to be virtualized more easily. Cross-architecture binaries = are out of scope for this feature, and Xen definitely doesn't support = it. You could get a slow emulation by using Qemu, but it would be very = slow indeed. If the image you're using is open-source, you could try building it = under ARM by using the relevant packages. I'm not familiar enough with = it to know if this is practical or not, but you could try the xen-users = or the project-specific mailing list. -anil On 7 Aug 2014, at 12:13, Gilles DALMAS wrote: > I thought that with this hvm allow me to emulate another architecture, = but if this feature did not work on arm, I do not know how. you know a = program, allowing me to do that? without losing too much power compared = to the host machine. >=20 >=20 >=20 >=20 >=20 > > Message du 07/08/14 11:58 > > De : "Anil Madhavapeddy" > > A : "Gilles DALMAS" > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > >Hi Gilles, >=20 > > > It looks like you are trying to install an x86_64 virtual machine = image onto an ARM Xen host. This will not work... >=20 > > > -anil >=20 > > > On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: >=20 > > nobody knows where this error come from? > >=20 > >=20 > >=20 > >=20 > > >=20 > > Message du 06/08/14 10:53 > > > De : "Anil Madhavapeddy" > > > A : "Gilles DALMAS" > > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > > This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode. Are you trying to boot an x86 guest on = ARM? >=20 > > > > -anil >=20 > > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > > >=20 > > > > > > the guest system can only be started in this mode. there is a = problems with this mode ? > > >=20 > > >=20 > > >=20 > > >=20 > > > >=20 > > Message du 06/08/14 10:21 > > > > De : "Anil Madhavapeddy" > > > > A : "Gilles DALMAS" > > > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > > Why are you trying to create an HVM guest on Xen/ARM? You should just = be using the default PV mode on ARM to launch guests. >=20 > > > > On 6 Aug 2014, at 09:06, Gilles DALMAS = wrote: > > > >=20 > > > > > > > > my xl file : > > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # Example HVM guest configuration > > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # > > > > # This is a fairly minimal example of what is required for an > > > > # HVM guest. For a more complete guide see xl.cfg(5) > > > >=20 > > > > # This configures an HVM rather than PV guest > > > > builder =3D "hvm" > > > >=20 > > > > # Guest name > > > > name =3D "Xp" > > > >=20 > > > > # 128-bit UUID for the domain as a hexadecimal number. > > > > # Use "uuidgen" to generate one if required. > > > > # The default behavior is to generate a new UUID each time the = guest is started. > > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > > >=20 > > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > > # enlightenment interfaces. Turning this on can improve Windows = guest > > > > # performance and is therefore recommended > > > > #viridian =3D 1 > > > >=20 > > > > # Initial memory allocation (MB) > > > > memory =3D 512 > > > >=20 > > > > # Maximum memory (MB) > > > > # If this is greater than `memory' then the slack will start = ballooned > > > > # (this assumes guest kernel support for ballooning) > > > > #maxmem =3D 512 > > > >=20 > > > > # Number of VCPUS > > > > vcpus =3D 2 > > > >=20 > > > > # Network devices > > > > # A list of 'vifspec' entries as described in > > > > # docs/misc/xl-network-configuration.markdown > > > > vif =3D [ 'bridge=3Dbr0' ] > > > >=20 > > > > # Disk Devices > > > > # A list of `diskspec' entries as described in > > > > # docs/misc/xl-disk-configuration.txt > > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > > >=20 > > > > # Guest VGA console configuration, either SDL or VNC > > > > sdl =3D 1 > > > > #vnc =3D 1 > > > >=20 > > > > >=20 > > > > =20 >=20 > > Message du 06/08/14 10:03 > > > > > De : "Gilles DALMAS" > > > > > A : "mirageos-devel@lists.xenproject.org" = > > > > > Copie =E0 :=20 > > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > > >=20 > > > > > > > > > > hello, >=20 > > > > > I have this error when i execute : >=20 > > > > > =20 >=20 > > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > > Parsing config from /etc/xen/xl.conf > > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: = create: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or directory > > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: = Disk vdev=3Dxvda spec.backend=3Dunknown > > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: = Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or = directory > > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find = device model pid in /local/domain/9/image/device-model-pid > > > > libxl: error: libxl.c:1421:libxl__destroy_domid: = libxl__destroy_device_model failed for 9 > > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: = complete, rc=3D-3 > > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: = inprogress: poller=3D0x32578, flags=3Dic > > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: = destroy > > > > xc: debug: hypercall buffer: total allocations:26 total = releases:26 > > > > xc: debug: hypercall buffer: current allocations:0 maximum = allocations:2 > > > > xc: debug: hypercall buffer: cache current size:2 > > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > > > > =20 >=20 > > > > > i have a cubietruck arm and i have installed qemu-system-arm = and qemu-system-x86 >=20 > > > > > =20 >=20 >=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 > > > > >=20 > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I'm = afraid not.  HVM is specifically a set of hardware extensions to = x86 to permit it to be virtualized more easily.  Cross-architecture = binaries are out of scope for this feature, and Xen definitely doesn't = support it.  You could get a slow emulation by using Qemu, but it = would be very slow indeed.

If the image you're using = is open-source, you could try building it under ARM by using the = relevant packages. I'm not familiar enough with it to know if this is = practical or not, but you could try the xen-users or the = project-specific mailing = list.

-anil

On 7 Aug = 2014, at 12:13, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

I thought that with this hvm allow me to emulate = another architecture, but if this feature did not work on arm, I do not = know how. you know a program, allowing me to do that? without losing too = much power compared to the host machine.




> Message du 07/08/14 11:58
> De : "Anil = Madhavapeddy" <anil@recoil.org>
> A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] error when i = create hvm guest
>
>Hi Gilles,

>
It looks like you are trying to install an x86_64 virtual machine = image onto an ARM Xen host.  This will not work...

>
-anil

>
On 7 Aug 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

> nobody knows where this error come from?
> =
>
>
>
>

> Message du 06/08/14 10:53
> > De : = "Anil Madhavapeddy" <anil@recoil.org>
> > A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > Objet : Re: [MirageOS-devel] error = when i create hvm guest
> >
> >
This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode.  Are you trying to boot an x86 guest = on ARM?

> >
-anil

> > On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> >
> >

> > the guest system can only be started in this mode. = there is a problems with this mode ?
> >
> >
> = >
> >
> >

> Message du 06/08/14 10:21
> > > De = : "Anil Madhavapeddy" <anil@recoil.org>
> > = > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > > Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > > Objet : Re: [MirageOS-devel] = error when i create hvm guest
> > >
> > >
Why are you trying to create an HVM guest on Xen/ARM?  You = should just be using the default PV mode on ARM to launch guests.

> > > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> > >
> > >

> > > my xl file :
> > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > = > # Example HVM guest configuration
> > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > = > #
> > > # This is a fairly minimal example of what is = required for an
> > > # HVM guest. For a more complete guide = see xl.cfg(5)
> > >
> > > # This configures an = HVM rather than PV guest
> > > builder =3D "hvm"
> = > >
> > > # Guest name
> > > name =3D = "Xp"
> > >
> > > # 128-bit UUID for the domain = as a hexadecimal number.
> > > # Use "uuidgen" to generate = one if required.
> > > # The default behavior is to generate = a new UUID each time the guest is started.
> > > #uuid =3D = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> > >
> > = > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> = > > # enlightenment interfaces. Turning this on can improve = Windows guest
> > > # performance and is therefore = recommended
> > > #viridian =3D 1
> > >
> = > > # Initial memory allocation (MB)
> > > memory =3D = 512
> > >
> > > # Maximum memory (MB)
> = > > # If this is greater than `memory' then the slack will start = ballooned
> > > # (this assumes guest kernel support for = ballooning)
> > > #maxmem =3D 512
> > >
> = > > # Number of VCPUS
> > > vcpus =3D 2
> > = >
> > > # Network devices
> > > # A list of = 'vifspec' entries as described in
> > > # = docs/misc/xl-network-configuration.markdown
> > > vif =3D [ = 'bridge=3Dbr0' ]
> > >
> > > # Disk = Devices
> > > # A list of `diskspec' entries as described = in
> > > # docs/misc/xl-disk-configuration.txt
> > = > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> > > =
> > > # Guest VGA console configuration, either SDL or = VNC
> > > sdl =3D 1
> > > #vnc =3D 1
> = > >
> > >

> > >  

> Message du 06/08/14 10:03
> > > = > De : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > > > A : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > > > Copie =E0 :
> > = > > Objet : [MirageOS-devel] error when i create hvm guest
> = > > >
> > > >

> > > > hello,

> > > > I have this = error when i execute :

> > > >  

> > = > > mirage@cubietruck:/$ sudo xl -vvv create = /etc/xen/xl.conf
> > > Parsing config from = /etc/xen/xl.conf
> > > libxl: debug: = libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil) = callback=3D(nil) poller=3D0x32578
> > > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or = directory
> > > libxl: debug: = libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda = spec.backend=3Dunknown
> > > libxl: error: = libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda = failed to stat: /dev/vg0/guest-linux-1: No such file or = directory
> > > libxl: error: = libxl_dm.c:1467:kill_device_model: unable to find device model pid in = /local/domain/9/image/device-model-pid
> > > libxl: error: = libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed = for 9
> > > libxl: debug: = libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, = rc=3D-3
> > > libxl: debug: = libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: = poller=3D0x32578, flags=3Dic
> > > libxl: debug: = libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> > = > xc: debug: hypercall buffer: total allocations:26 total = releases:26
> > > xc: debug: hypercall buffer: current = allocations:0 maximum allocations:2
> > > xc: debug: = hypercall buffer: cache current size:2
> > > xc: debug: = hypercall buffer: cache hits:22 misses:2 toobig:2

> > > = >  

> > > > i have a cubietruck arm and i have = installed qemu-system-arm and qemu-system-x86

> > > > =  


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

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

= --Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D-- --===============8938188165890803727== 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 --===============8938188165890803727==-- From mirageos-devel-bounces@lists.xenproject.org Sat Aug 09 13:19:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 09 Aug 2014 13:19:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XG6YN-0003X1-Ck; Sat, 09 Aug 2014 13:19:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XG6YM-0003Ww-Lu for mirageos-devel@lists.xenproject.org; Sat, 09 Aug 2014 13:19:22 +0000 Received: from [193.109.254.147:28160] by server-10.bemta-14.messagelabs.com id D9/92-06615-9DF16E35; Sat, 09 Aug 2014 13:19:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1407590360!14721099!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.3 required=7.0 tests=HOT_NASTY,HTML_30_40, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10037 invoked from network); 9 Aug 2014 13:19:20 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 9 Aug 2014 13:19:20 -0000 Received: (qmail 29997 invoked by uid 634); 9 Aug 2014 13:19:19 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from 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; Sat, 09 Aug 2014 14:19:16 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> Date: Sat, 9 Aug 2014 14:19:15 +0100 Message-Id: <0A33B920-A42D-4013-9BE9-9B0E4DE158CB@recoil.org> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> To: Gilles DALMAS 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] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8938188165890803727==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8938188165890803727== Content-Type: multipart/alternative; boundary="Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D" --Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I'm afraid not. HVM is specifically a set of hardware extensions to x86 = to permit it to be virtualized more easily. Cross-architecture binaries = are out of scope for this feature, and Xen definitely doesn't support = it. You could get a slow emulation by using Qemu, but it would be very = slow indeed. If the image you're using is open-source, you could try building it = under ARM by using the relevant packages. I'm not familiar enough with = it to know if this is practical or not, but you could try the xen-users = or the project-specific mailing list. -anil On 7 Aug 2014, at 12:13, Gilles DALMAS wrote: > I thought that with this hvm allow me to emulate another architecture, = but if this feature did not work on arm, I do not know how. you know a = program, allowing me to do that? without losing too much power compared = to the host machine. >=20 >=20 >=20 >=20 >=20 > > Message du 07/08/14 11:58 > > De : "Anil Madhavapeddy" > > A : "Gilles DALMAS" > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > >Hi Gilles, >=20 > > > It looks like you are trying to install an x86_64 virtual machine = image onto an ARM Xen host. This will not work... >=20 > > > -anil >=20 > > > On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: >=20 > > nobody knows where this error come from? > >=20 > >=20 > >=20 > >=20 > > >=20 > > Message du 06/08/14 10:53 > > > De : "Anil Madhavapeddy" > > > A : "Gilles DALMAS" > > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > > This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode. Are you trying to boot an x86 guest on = ARM? >=20 > > > > -anil >=20 > > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > > >=20 > > > > > > the guest system can only be started in this mode. there is a = problems with this mode ? > > >=20 > > >=20 > > >=20 > > >=20 > > > >=20 > > Message du 06/08/14 10:21 > > > > De : "Anil Madhavapeddy" > > > > A : "Gilles DALMAS" > > > > Copie =E0 : "mirageos-devel@lists.xenproject.org" = > > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > > Why are you trying to create an HVM guest on Xen/ARM? You should just = be using the default PV mode on ARM to launch guests. >=20 > > > > On 6 Aug 2014, at 09:06, Gilles DALMAS = wrote: > > > >=20 > > > > > > > > my xl file : > > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # Example HVM guest configuration > > > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # > > > > # This is a fairly minimal example of what is required for an > > > > # HVM guest. For a more complete guide see xl.cfg(5) > > > >=20 > > > > # This configures an HVM rather than PV guest > > > > builder =3D "hvm" > > > >=20 > > > > # Guest name > > > > name =3D "Xp" > > > >=20 > > > > # 128-bit UUID for the domain as a hexadecimal number. > > > > # Use "uuidgen" to generate one if required. > > > > # The default behavior is to generate a new UUID each time the = guest is started. > > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > > >=20 > > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > > # enlightenment interfaces. Turning this on can improve Windows = guest > > > > # performance and is therefore recommended > > > > #viridian =3D 1 > > > >=20 > > > > # Initial memory allocation (MB) > > > > memory =3D 512 > > > >=20 > > > > # Maximum memory (MB) > > > > # If this is greater than `memory' then the slack will start = ballooned > > > > # (this assumes guest kernel support for ballooning) > > > > #maxmem =3D 512 > > > >=20 > > > > # Number of VCPUS > > > > vcpus =3D 2 > > > >=20 > > > > # Network devices > > > > # A list of 'vifspec' entries as described in > > > > # docs/misc/xl-network-configuration.markdown > > > > vif =3D [ 'bridge=3Dbr0' ] > > > >=20 > > > > # Disk Devices > > > > # A list of `diskspec' entries as described in > > > > # docs/misc/xl-disk-configuration.txt > > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > > >=20 > > > > # Guest VGA console configuration, either SDL or VNC > > > > sdl =3D 1 > > > > #vnc =3D 1 > > > >=20 > > > > >=20 > > > > =20 >=20 > > Message du 06/08/14 10:03 > > > > > De : "Gilles DALMAS" > > > > > A : "mirageos-devel@lists.xenproject.org" = > > > > > Copie =E0 :=20 > > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > > >=20 > > > > > > > > > > hello, >=20 > > > > > I have this error when i execute : >=20 > > > > > =20 >=20 > > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > > Parsing config from /etc/xen/xl.conf > > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: = create: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or directory > > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: = Disk vdev=3Dxvda spec.backend=3Dunknown > > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: = Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or = directory > > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find = device model pid in /local/domain/9/image/device-model-pid > > > > libxl: error: libxl.c:1421:libxl__destroy_domid: = libxl__destroy_device_model failed for 9 > > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: = complete, rc=3D-3 > > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: = inprogress: poller=3D0x32578, flags=3Dic > > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: = destroy > > > > xc: debug: hypercall buffer: total allocations:26 total = releases:26 > > > > xc: debug: hypercall buffer: current allocations:0 maximum = allocations:2 > > > > xc: debug: hypercall buffer: cache current size:2 > > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 >=20 > > > > > =20 >=20 > > > > > i have a cubietruck arm and i have installed qemu-system-arm = and qemu-system-x86 >=20 > > > > > =20 >=20 >=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 > > > > >=20 > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I'm = afraid not.  HVM is specifically a set of hardware extensions to = x86 to permit it to be virtualized more easily.  Cross-architecture = binaries are out of scope for this feature, and Xen definitely doesn't = support it.  You could get a slow emulation by using Qemu, but it = would be very slow indeed.

If the image you're using = is open-source, you could try building it under ARM by using the = relevant packages. I'm not familiar enough with it to know if this is = practical or not, but you could try the xen-users or the = project-specific mailing = list.

-anil

On 7 Aug = 2014, at 12:13, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

I thought that with this hvm allow me to emulate = another architecture, but if this feature did not work on arm, I do not = know how. you know a program, allowing me to do that? without losing too = much power compared to the host machine.




> Message du 07/08/14 11:58
> De : "Anil = Madhavapeddy" <anil@recoil.org>
> A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> Objet : Re: [MirageOS-devel] error when i = create hvm guest
>
>Hi Gilles,

>
It looks like you are trying to install an x86_64 virtual machine = image onto an ARM Xen host.  This will not work...

>
-anil

>
On 7 Aug 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:

> nobody knows where this error come from?
> =
>
>
>
>

> Message du 06/08/14 10:53
> > De : = "Anil Madhavapeddy" <anil@recoil.org>
> > A : = "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > Objet : Re: [MirageOS-devel] error = when i create hvm guest
> >
> >
This mode doesn't exist on ARM: it's an option to run x86 guests in = hardware virtualisation mode.  Are you trying to boot an x86 guest = on ARM?

> >
-anil

> > On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> >
> >

> > the guest system can only be started in this mode. = there is a problems with this mode ?
> >
> >
> = >
> >
> >

> Message du 06/08/14 10:21
> > > De = : "Anil Madhavapeddy" <anil@recoil.org>
> > = > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > > Copie =E0 : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > > Objet : Re: [MirageOS-devel] = error when i create hvm guest
> > >
> > >
Why are you trying to create an HVM guest on Xen/ARM?  You = should just be using the default PV mode on ARM to launch guests.

> > > On 6 Aug 2014, at 09:06, Gilles DALMAS <gdalmas@wanadoo.fr> = wrote:
> > >
> > >

> > > my xl file :
> > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > = > # Example HVM guest configuration
> > > # = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > = > #
> > > # This is a fairly minimal example of what is = required for an
> > > # HVM guest. For a more complete guide = see xl.cfg(5)
> > >
> > > # This configures an = HVM rather than PV guest
> > > builder =3D "hvm"
> = > >
> > > # Guest name
> > > name =3D = "Xp"
> > >
> > > # 128-bit UUID for the domain = as a hexadecimal number.
> > > # Use "uuidgen" to generate = one if required.
> > > # The default behavior is to generate = a new UUID each time the guest is started.
> > > #uuid =3D = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> > >
> > = > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> = > > # enlightenment interfaces. Turning this on can improve = Windows guest
> > > # performance and is therefore = recommended
> > > #viridian =3D 1
> > >
> = > > # Initial memory allocation (MB)
> > > memory =3D = 512
> > >
> > > # Maximum memory (MB)
> = > > # If this is greater than `memory' then the slack will start = ballooned
> > > # (this assumes guest kernel support for = ballooning)
> > > #maxmem =3D 512
> > >
> = > > # Number of VCPUS
> > > vcpus =3D 2
> > = >
> > > # Network devices
> > > # A list of = 'vifspec' entries as described in
> > > # = docs/misc/xl-network-configuration.markdown
> > > vif =3D [ = 'bridge=3Dbr0' ]
> > >
> > > # Disk = Devices
> > > # A list of `diskspec' entries as described = in
> > > # docs/misc/xl-disk-configuration.txt
> > = > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> > > =
> > > # Guest VGA console configuration, either SDL or = VNC
> > > sdl =3D 1
> > > #vnc =3D 1
> = > >
> > >

> > >  

> Message du 06/08/14 10:03
> > > = > De : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> = > > > A : "mirageos-devel@lists.x= enproject.org" <mirageos-devel@lists.x= enproject.org>
> > > > Copie =E0 :
> > = > > Objet : [MirageOS-devel] error when i create hvm guest
> = > > >
> > > >

> > > > hello,

> > > > I have this = error when i execute :

> > > >  

> > = > > mirage@cubietruck:/$ sudo xl -vvv create = /etc/xen/xl.conf
> > > Parsing config from = /etc/xen/xl.conf
> > > libxl: debug: = libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=3D(nil) = callback=3D(nil) poller=3D0x32578
> > > libxl: verbose: = libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is = unavailable, use qemu-xen-traditional instead: No such file or = directory
> > > libxl: debug: = libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda = spec.backend=3Dunknown
> > > libxl: error: = libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=3Dxvda = failed to stat: /dev/vg0/guest-linux-1: No such file or = directory
> > > libxl: error: = libxl_dm.c:1467:kill_device_model: unable to find device model pid in = /local/domain/9/image/device-model-pid
> > > libxl: error: = libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed = for 9
> > > libxl: debug: = libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, = rc=3D-3
> > > libxl: debug: = libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: = poller=3D0x32578, flags=3Dic
> > > libxl: debug: = libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> > = > xc: debug: hypercall buffer: total allocations:26 total = releases:26
> > > xc: debug: hypercall buffer: current = allocations:0 maximum allocations:2
> > > xc: debug: = hypercall buffer: cache current size:2
> > > xc: debug: = hypercall buffer: cache hits:22 misses:2 toobig:2

> > > = >  

> > > > i have a cubietruck arm and i have = installed qemu-system-arm and qemu-system-x86

> > > > =  


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

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

= --Apple-Mail=_DCC1AA27-E044-48CC-BA5B-DB05924A7B6D-- --===============8938188165890803727== 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 --===============8938188165890803727==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 07:46:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 07:46: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 1XGNqB-0003th-6S; Sun, 10 Aug 2014 07:46:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGNq9-0003tc-KK for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 07:46:53 +0000 Received: from [85.158.143.35:41478] by server-3.bemta-4.messagelabs.com id E7/A7-06192-C6327E35; Sun, 10 Aug 2014 07:46:52 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-21.messagelabs.com!1407656811!11768876!1 X-Originating-IP: [80.12.242.127] X-SpamReason: No, hits=1.8 required=7.0 tests=HOT_NASTY,HTML_40_50, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2442 invoked from network); 10 Aug 2014 07:46:51 -0000 Received: from smtp05.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.127) by server-3.tower-21.messagelabs.com with SMTP; 10 Aug 2014 07:46:51 -0000 Received: from wwinf2237 ([172.22.131.111]) by mwinf5d52 with ME id cvmq1o00A2QMPtG03vmqfg; Sun, 10 Aug 2014 09:46:50 +0200 X-ME-Helo: wwinf2237 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Sun, 10 Aug 2014 09:46:50 +0200 X-ME-IP: 86.210.246.22 Date: Sun, 10 Aug 2014 09:46:50 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1372377124.1038.1407656810318.JavaMail.www@wwinf2237> In-Reply-To: <0A33B920-A42D-4013-9BE9-9B0E4DE158CB@recoil.org> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> <0A33B920-A42D-4013-9BE9-9B0E4DE158CB@recoil.org> MIME-Version: 1.0 X-Originating-IP: [86.210.246.22] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6906396712148052190==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6906396712148052190== Content-Type: multipart/alternative; boundary="----=_Part_1037_1751468479.1407656810315" ------=_Part_1037_1751468479.1407656810315 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'll try to take the kernel of boris BREZILLON to manage the nand. it's a v= ersion 3.16 rc6.=20 > Message du 09/08/14 15:19 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 >I'm afraid not. =C2=A0HVM is specifically a set of hardware extensions to = x86 to permit it to be virtualized more easily. =C2=A0Cross-architecture bi= naries are out of scope for this feature, and Xen definitely doesn't suppor= t it. =C2=A0You could get a slow emulation by using Qemu, but it would be v= ery slow indeed. > If the image you're using is open-source, you could try building it under A= RM by using the relevant packages. I'm not familiar enough with it to know = if this is practical or not, but you could try the xen-users or the project= -specific mailing list. > -anil > On 7 Aug 2014, at 12:13, Gilles DALMAS wrote: > I thought that with this hvm allow me to emulate another architecture, bu= t if this feature did not work on arm, I do not know how. you know a progra= m, allowing me to do that? without losing too much power compared to the ho= st machine. >=20 >=20 >=20 >=20 > > Message du 07/08/14 11:58 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > >Hi Gilles, > > It looks like you are trying to install an x86_64 virtual machine image ont= o an ARM Xen host. =C2=A0This will not work... > > -anil > > On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: > > nobody knows where this error come from? > >=20 > >=20 > >=20 > >=20 > > > Message du 06/08/14 10:53 > > > De : "Anil Madhavapeddy"=20 > > > A : "Gilles DALMAS"=20 > > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > > > -anil > > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > > >=20 > > > > > > the guest system can only be started in this mode. there is a problem= s with this mode ? > > >=20 > > >=20 > > >=20 > > >=20 > > > > Message du 06/08/14 10:21 > > > > De : "Anil Madhavapeddy"=20 > > > > A : "Gilles DALMAS"=20 > > > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > > > >=20 > > > > > > > > my xl file : > > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # Example HVM guest configuration > > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # > > > > # This is a fairly minimal example of what is required for an > > > > # HVM guest. For a more complete guide see xl.cfg(5) > > > >=20 > > > > # This configures an HVM rather than PV guest > > > > builder =3D "hvm" > > > >=20 > > > > # Guest name > > > > name =3D "Xp" > > > >=20 > > > > # 128-bit UUID for the domain as a hexadecimal number. > > > > # Use "uuidgen" to generate one if required. > > > > # The default behavior is to generate a new UUID each time the gues= t is started. > > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > > >=20 > > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > > # enlightenment interfaces. Turning this on can improve Windows gue= st > > > > # performance and is therefore recommended > > > > #viridian =3D 1 > > > >=20 > > > > # Initial memory allocation (MB) > > > > memory =3D 512 > > > >=20 > > > > # Maximum memory (MB) > > > > # If this is greater than `memory' then the slack will start balloo= ned > > > > # (this assumes guest kernel support for ballooning) > > > > #maxmem =3D 512 > > > >=20 > > > > # Number of VCPUS > > > > vcpus =3D 2 > > > >=20 > > > > # Network devices > > > > # A list of 'vifspec' entries as described in > > > > # docs/misc/xl-network-configuration.markdown > > > > vif =3D [ 'bridge=3Dbr0' ] > > > >=20 > > > > # Disk Devices > > > > # A list of `diskspec' entries as described in > > > > # docs/misc/xl-disk-configuration.txt > > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > > >=20 > > > > # Guest VGA console configuration, either SDL or VNC > > > > sdl =3D 1 > > > > #vnc =3D 1 > > > >=20 > > > > > > > > =C2=A0 > Message du 06/08/14 10:03 > > > > > De : "Gilles DALMAS"=20 > > > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > > > Copie =C3=A0 :=20 > > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > > >=20 > > > > > > > > > > hello, > > > > > I have this error when i execute : > > > > > =C2=A0 > > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > > Parsing config from /etc/xen/xl.conf > > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: cre= ate: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefa= ult: qemu-xen is unavailable, use qemu-xen-traditional instead: No such fil= e or directory > > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Di= sk vdev=3Dxvda spec.backend=3Dunknown > > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Di= sk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or dire= ctory > > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find dev= ice model pid in /local/domain/9/image/device-model-pid > > > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_dev= ice_model failed for 9 > > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: co= mplete, rc=3D-3 > > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inp= rogress: poller=3D0x32578, flags=3Dic > > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: de= stroy > > > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > > > xc: debug: hypercall buffer: current allocations:0 maximum allocati= ons:2 > > > > xc: debug: hypercall buffer: cache current size:2 > > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > > > =C2=A0 > > > > > i have a cubietruck arm and i have installed qemu-system-arm and = qemu-system-x86 > > > > > =C2=A0 > > > >=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 > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > ------=_Part_1037_1751468479.1407656810315 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'll try to take the kernel of boris BREZILLON to manage the nand<= /span>. it's a = version 3.16 rc6.


> Message du 09/08/14 15:19
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>I'm afra= id not. =C2=A0HVM is specifically a set of hardware extensions to x86 to pe= rmit it to be virtualized more easily. =C2=A0Cross-architecture binaries ar= e out of scope for this feature, and Xen definitely doesn't support it. =C2= =A0You could get a slow emulation by using Qemu, but it would be very slow = indeed.

>
If the image you're using is open-source, you could try building it un= der ARM by using the relevant packages. I'm not familiar enough with it to = know if this is practical or not, but you could try the xen-users or the pr= oject-specific mailing list.

>
-anil

>
On 7 Aug 2014, at 12:13, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> I thought that with this hvm allow me to emulate another architectu= re, but if this feature did not work on arm, I do not know how. you know a = program, allowing me to do that? without losing too much power compared to = the host machine.
>
>
>
>
>

> Message du 07/08/14 11:58
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >Hi G= illes,

> >
It looks like you are trying to install an x86_64 virtual machine imag= e onto an ARM Xen host. =C2=A0This will not work...

> >
-anil

> >
On 7 Aug 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> > nobody knows where this error come from?
> >
= > >
> >
> >
> >

> Message du 06/08/14 10:53
> > > De : "An= il Madhavapeddy" <anil@recoil.org= >
> > > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > > Copie =C3=A0 : "= mirageos-devel@lists= .xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Objet = : Re: [MirageOS-devel] error when i create hvm guest
> > > > > >
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

> > >
-anil

> > > On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>= > >
> > >

> > > the guest system can only be started in this mode. there = is a problems with this mode ?
> > >
> > > > > >
> > >
> > >

> Message du 06/08/14 10:21
> > > > De = : "Anil Madhavapeddy" <anil@recoil.or= g>
> > > > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > > > C= opie =C3=A0 : "mirag= eos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> &= gt; > > Objet : Re: [MirageOS-devel] error when i create hvm guest> > > >
> > > >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > > > On 6 Aug 2014, at 09:06, Gilles DALMAS <<= a href=3D"mailto:gdalmas@wanadoo.fr">gdalmas@wanadoo.fr> wrote:
> > > >
> > > >

> > > > my xl file :
> > > > # =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > # Ex= ample HVM guest configuration
> > > > # =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > #
>= ; > > > # This is a fairly minimal example of what is required for= an
> > > > # HVM guest. For a more complete guide see xl.= cfg(5)
> > > >
> > > > # This configures= an HVM rather than PV guest
> > > > builder =3D "hvm"
> > > >
> > > > # Guest name
> >= > > name =3D "Xp"
> > > >
> > > >= # 128-bit UUID for the domain as a hexadecimal number.
> > >= > # Use "uuidgen" to generate one if required.
> > > >= # The default behavior is to generate a new UUID each time the guest is st= arted.
> > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX= XXXX"
> > > >
> > > > # Enable Microsoft= Hyper-V compatibile paravirtualisation /
> > > > # enligh= tenment interfaces. Turning this on can improve Windows guest
> >= ; > > # performance and is therefore recommended
> > > = > #viridian =3D 1
> > > >
> > > > # I= nitial memory allocation (MB)
> > > > memory =3D 512
= > > > >
> > > > # Maximum memory (MB)
&g= t; > > > # If this is greater than `memory' then the slack will st= art ballooned
> > > > # (this assumes guest kernel support= for ballooning)
> > > > #maxmem =3D 512
> > &g= t; >
> > > > # Number of VCPUS
> > > >= ; vcpus =3D 2
> > > >
> > > > # Network = devices
> > > > # A list of 'vifspec' entries as described= in
> > > > # docs/misc/xl-network-configuration.markdown<= br />> > > > vif =3D [ 'bridge=3Dbr0' ]
> > > >= ;
> > > > # Disk Devices
> > > > # A lis= t of `diskspec' entries as described in
> > > > # docs/mis= c/xl-disk-configuration.txt
> > > > disk =3D [ '/dev/vg0/g= uest-linux-1,raw,xvda,rw' ]
> > > >
> > > &= gt; # Guest VGA console configuration, either SDL or VNC
> > >= ; > sdl =3D 1
> > > > #vnc =3D 1
> > > &g= t;
> > > >

> > > > =C2=A0

> Message du 06/08/14 10:03
> > > > >= ; De : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> > > > > A : "mirageos-devel@lists.xenproject.org" &l= t;mirageos-devel@lis= ts.xenproject.org>
> > > > > Copie =C3=A0 :
> > > > > Objet : [MirageOS-devel] error when i create hvm= guest
> > > > >
> > > > >

> > > > > hello,

> > > > > I have this error when i execute :

> > > > > =C2=A0

> > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/x= en/xl.conf
> > > > Parsing config from /etc/xen/xl.conf> > > > libxl: debug: libxl_create.c:1342:do_domain_create: = ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x32578
>= > > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info= _setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No = such file or directory
> > > > libxl: debug: libxl_device.= c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda spec.backend=3Dunkno= wn
> > > > libxl: error: libxl_device.c:265:libxl__device_= disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: = No such file or directory
> > > > libxl: error: libxl_dm.c= :1467:kill_device_model: unable to find device model pid in /local/domain/9= /image/device-model-pid
> > > > libxl: error: libxl.c:1421= :libxl__destroy_domid: libxl__destroy_device_model failed for 9
> &= gt; > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f= 00: complete, rc=3D-3
> > > > libxl: debug: libxl_create.c= :1356:do_domain_create: ao 0x31f00: inprogress: poller=3D0x32578, flags=3Di= c
> > > > libxl: debug: libxl_event.c:1563:libxl__ao__dest= roy: ao 0x31f00: destroy
> > > > xc: debug: hypercall buff= er: total allocations:26 total releases:26
> > > > xc: deb= ug: hypercall buffer: current allocations:0 maximum allocations:2
>= > > > xc: debug: hypercall buffer: cache current size:2
>= > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > > > =C2=A0

> > > > > i have a cubietruck arm and i have installed qe= mu-system-arm and qemu-system-x86

> > > > > =C2=A0


> > > >
> > > >
> > > &g= t; _______________________________________________
> > > >= MirageOS-devel mailing list
> > > > MirageOS-devel@lists.xenproject.org> > > > http://lists.xenproject.org/cgi-bin/mailman/li= stinfo/mirageos-devel
> > > >
> > > >= ;
_______________________________________________
>= > > > MirageOS-devel mailing list
> > >= ; > MirageO= S-devel@lists.xenproject.org
> > > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > > >

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

>
------=_Part_1037_1751468479.1407656810315-- --===============6906396712148052190== 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 --===============6906396712148052190==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 07:46:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 07:46: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 1XGNqB-0003th-6S; Sun, 10 Aug 2014 07:46:55 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGNq9-0003tc-KK for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 07:46:53 +0000 Received: from [85.158.143.35:41478] by server-3.bemta-4.messagelabs.com id E7/A7-06192-C6327E35; Sun, 10 Aug 2014 07:46:52 +0000 X-Env-Sender: gdalmas@wanadoo.fr X-Msg-Ref: server-3.tower-21.messagelabs.com!1407656811!11768876!1 X-Originating-IP: [80.12.242.127] X-SpamReason: No, hits=1.8 required=7.0 tests=HOT_NASTY,HTML_40_50, HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2442 invoked from network); 10 Aug 2014 07:46:51 -0000 Received: from smtp05.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.127) by server-3.tower-21.messagelabs.com with SMTP; 10 Aug 2014 07:46:51 -0000 Received: from wwinf2237 ([172.22.131.111]) by mwinf5d52 with ME id cvmq1o00A2QMPtG03vmqfg; Sun, 10 Aug 2014 09:46:50 +0200 X-ME-Helo: wwinf2237 X-ME-Auth: Z2RhbG1hc0B3YW5hZG9vLmZy X-ME-Date: Sun, 10 Aug 2014 09:46:50 +0200 X-ME-IP: 86.210.246.22 Date: Sun, 10 Aug 2014 09:46:50 +0200 (CEST) From: Gilles DALMAS To: Anil Madhavapeddy Message-ID: <1372377124.1038.1407656810318.JavaMail.www@wwinf2237> In-Reply-To: <0A33B920-A42D-4013-9BE9-9B0E4DE158CB@recoil.org> References: <1571816749.3988.1407312183021.JavaMail.www@wwinf1c15> <2126461078.4082.1407312366820.JavaMail.www@wwinf1c15> <223A1B4A-B90F-41FF-AA6E-E9EAFE89DEB9@recoil.org> <1355929158.5935.1407314691934.JavaMail.www@wwinf1c13> <692647932.3702.1407399012137.JavaMail.www@wwinf1c20> <570144226.7741.1407410020951.JavaMail.www@wwinf1c20> <0A33B920-A42D-4013-9BE9-9B0E4DE158CB@recoil.org> MIME-Version: 1.0 X-Originating-IP: [86.210.246.22] X-WUM-FROM: |~| X-WUM-TO: |~| X-WUM-CC: |~| X-WUM-REPLYTO: |~| Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] error when i create hvm guest X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Gilles DALMAS List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6906396712148052190==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6906396712148052190== Content-Type: multipart/alternative; boundary="----=_Part_1037_1751468479.1407656810315" ------=_Part_1037_1751468479.1407656810315 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'll try to take the kernel of boris BREZILLON to manage the nand. it's a v= ersion 3.16 rc6.=20 > Message du 09/08/14 15:19 > De : "Anil Madhavapeddy"=20 > A : "Gilles DALMAS"=20 > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > Objet : Re: [MirageOS-devel] error when i create hvm guest >=20 >I'm afraid not. =C2=A0HVM is specifically a set of hardware extensions to = x86 to permit it to be virtualized more easily. =C2=A0Cross-architecture bi= naries are out of scope for this feature, and Xen definitely doesn't suppor= t it. =C2=A0You could get a slow emulation by using Qemu, but it would be v= ery slow indeed. > If the image you're using is open-source, you could try building it under A= RM by using the relevant packages. I'm not familiar enough with it to know = if this is practical or not, but you could try the xen-users or the project= -specific mailing list. > -anil > On 7 Aug 2014, at 12:13, Gilles DALMAS wrote: > I thought that with this hvm allow me to emulate another architecture, bu= t if this feature did not work on arm, I do not know how. you know a progra= m, allowing me to do that? without losing too much power compared to the ho= st machine. >=20 >=20 >=20 >=20 > > Message du 07/08/14 11:58 > > De : "Anil Madhavapeddy"=20 > > A : "Gilles DALMAS"=20 > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > Objet : Re: [MirageOS-devel] error when i create hvm guest > >=20 > >Hi Gilles, > > It looks like you are trying to install an x86_64 virtual machine image ont= o an ARM Xen host. =C2=A0This will not work... > > -anil > > On 7 Aug 2014, at 09:10, Gilles DALMAS wrote: > > nobody knows where this error come from? > >=20 > >=20 > >=20 > >=20 > > > Message du 06/08/14 10:53 > > > De : "Anil Madhavapeddy"=20 > > > A : "Gilles DALMAS"=20 > > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > >=20 > > > This mode doesn't exist on ARM: it's an option to run x86 guests in hardwar= e virtualisation mode. =C2=A0Are you trying to boot an x86 guest on ARM? > > > -anil > > > On 6 Aug 2014, at 09:44, Gilles DALMAS wrote: > > >=20 > > > > > > the guest system can only be started in this mode. there is a problem= s with this mode ? > > >=20 > > >=20 > > >=20 > > >=20 > > > > Message du 06/08/14 10:21 > > > > De : "Anil Madhavapeddy"=20 > > > > A : "Gilles DALMAS"=20 > > > > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"=20 > > > > Objet : Re: [MirageOS-devel] error when i create hvm guest > > > >=20 > > > > Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should just= be using the default PV mode on ARM to launch guests. > > > > On 6 Aug 2014, at 09:06, Gilles DALMAS wrote: > > > >=20 > > > > > > > > my xl file : > > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # Example HVM guest configuration > > > > # =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > # > > > > # This is a fairly minimal example of what is required for an > > > > # HVM guest. For a more complete guide see xl.cfg(5) > > > >=20 > > > > # This configures an HVM rather than PV guest > > > > builder =3D "hvm" > > > >=20 > > > > # Guest name > > > > name =3D "Xp" > > > >=20 > > > > # 128-bit UUID for the domain as a hexadecimal number. > > > > # Use "uuidgen" to generate one if required. > > > > # The default behavior is to generate a new UUID each time the gues= t is started. > > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" > > > >=20 > > > > # Enable Microsoft Hyper-V compatibile paravirtualisation / > > > > # enlightenment interfaces. Turning this on can improve Windows gue= st > > > > # performance and is therefore recommended > > > > #viridian =3D 1 > > > >=20 > > > > # Initial memory allocation (MB) > > > > memory =3D 512 > > > >=20 > > > > # Maximum memory (MB) > > > > # If this is greater than `memory' then the slack will start balloo= ned > > > > # (this assumes guest kernel support for ballooning) > > > > #maxmem =3D 512 > > > >=20 > > > > # Number of VCPUS > > > > vcpus =3D 2 > > > >=20 > > > > # Network devices > > > > # A list of 'vifspec' entries as described in > > > > # docs/misc/xl-network-configuration.markdown > > > > vif =3D [ 'bridge=3Dbr0' ] > > > >=20 > > > > # Disk Devices > > > > # A list of `diskspec' entries as described in > > > > # docs/misc/xl-disk-configuration.txt > > > > disk =3D [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ] > > > >=20 > > > > # Guest VGA console configuration, either SDL or VNC > > > > sdl =3D 1 > > > > #vnc =3D 1 > > > >=20 > > > > > > > > =C2=A0 > Message du 06/08/14 10:03 > > > > > De : "Gilles DALMAS"=20 > > > > > A : "mirageos-devel@lists.xenproject.org"=20 > > > > > Copie =C3=A0 :=20 > > > > > Objet : [MirageOS-devel] error when i create hvm guest > > > > >=20 > > > > > > > > > > hello, > > > > > I have this error when i execute : > > > > > =C2=A0 > > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf > > > > Parsing config from /etc/xen/xl.conf > > > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: cre= ate: how=3D(nil) callback=3D(nil) poller=3D0x32578 > > > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefa= ult: qemu-xen is unavailable, use qemu-xen-traditional instead: No such fil= e or directory > > > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Di= sk vdev=3Dxvda spec.backend=3Dunknown > > > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Di= sk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: No such file or dire= ctory > > > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find dev= ice model pid in /local/domain/9/image/device-model-pid > > > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_dev= ice_model failed for 9 > > > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: co= mplete, rc=3D-3 > > > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inp= rogress: poller=3D0x32578, flags=3Dic > > > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: de= stroy > > > > xc: debug: hypercall buffer: total allocations:26 total releases:26 > > > > xc: debug: hypercall buffer: current allocations:0 maximum allocati= ons:2 > > > > xc: debug: hypercall buffer: cache current size:2 > > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2 > > > > > =C2=A0 > > > > > i have a cubietruck arm and i have installed qemu-system-arm and = qemu-system-x86 > > > > > =C2=A0 > > > >=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 > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > ------=_Part_1037_1751468479.1407656810315 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I'll try to take the kernel of boris BREZILLON to manage the nand<= /span>. it's a = version 3.16 rc6.


> Message du 09/08/14 15:19
> De : "Anil Madhava= peddy" <anil@recoil.org>
> A : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> Copie =C3=A0 : "mirageos-devel@lists.xenproject.org"= <mirageos-devel@lists.xenproject.org>
> Objet : Re: [MirageO= S-devel] error when i create hvm guest
>
>I'm afra= id not. =C2=A0HVM is specifically a set of hardware extensions to x86 to pe= rmit it to be virtualized more easily. =C2=A0Cross-architecture binaries ar= e out of scope for this feature, and Xen definitely doesn't support it. =C2= =A0You could get a slow emulation by using Qemu, but it would be very slow = indeed.

>
If the image you're using is open-source, you could try building it un= der ARM by using the relevant packages. I'm not familiar enough with it to = know if this is practical or not, but you could try the xen-users or the pr= oject-specific mailing list.

>
-anil

>
On 7 Aug 2014, at 12:13, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> I thought that with this hvm allow me to emulate another architectu= re, but if this feature did not work on arm, I do not know how. you know a = program, allowing me to do that? without losing too much power compared to = the host machine.
>
>
>
>
>

> Message du 07/08/14 11:58
> > De : "Anil Ma= dhavapeddy" <anil@recoil.org><= br />> > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > Copie =C3=A0 : "mirageos-devel@lists.xenproject.org= " <mirageos-d= evel@lists.xenproject.org>
> > Objet : Re: [MirageOS-deve= l] error when i create hvm guest
> >
> >Hi G= illes,

> >
It looks like you are trying to install an x86_64 virtual machine imag= e onto an ARM Xen host. =C2=A0This will not work...

> >
-anil

> >
On 7 Aug 2014, at 09:10, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:

> > nobody knows where this error come from?
> >
= > >
> >
> >
> >

> Message du 06/08/14 10:53
> > > De : "An= il Madhavapeddy" <anil@recoil.org= >
> > > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > > Copie =C3=A0 : "= mirageos-devel@lists= .xenproject.org" <mirageos-devel@lists.xenproject.org>
> > > Objet = : Re: [MirageOS-devel] error when i create hvm guest
> > > > > >
This mode doesn't exist on ARM: it's an option to run x86 guests in ha= rdware virtualisation mode. =C2=A0Are you trying to boot an x86 guest on AR= M?

> > >
-anil

> > > On 6 Aug 2014, at 09:44, Gilles DALMAS <gdalmas@wanadoo.fr> wrote:
>= > >
> > >

> > > the guest system can only be started in this mode. there = is a problems with this mode ?
> > >
> > > > > >
> > >
> > >

> Message du 06/08/14 10:21
> > > > De = : "Anil Madhavapeddy" <anil@recoil.or= g>
> > > > A : "Gilles DALMAS" <gdalmas@wanadoo.fr>
> > > > C= opie =C3=A0 : "mirag= eos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
> &= gt; > > Objet : Re: [MirageOS-devel] error when i create hvm guest> > > >
> > > >
Why are you trying to create an HVM guest on Xen/ARM? =C2=A0You should= just be using the default PV mode on ARM to launch guests.

> > > > On 6 Aug 2014, at 09:06, Gilles DALMAS <<= a href=3D"mailto:gdalmas@wanadoo.fr">gdalmas@wanadoo.fr> wrote:
> > > >
> > > >

> > > > my xl file :
> > > > # =3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > # Ex= ample HVM guest configuration
> > > > # =3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > > #
>= ; > > > # This is a fairly minimal example of what is required for= an
> > > > # HVM guest. For a more complete guide see xl.= cfg(5)
> > > >
> > > > # This configures= an HVM rather than PV guest
> > > > builder =3D "hvm"
> > > >
> > > > # Guest name
> >= > > name =3D "Xp"
> > > >
> > > >= # 128-bit UUID for the domain as a hexadecimal number.
> > >= > # Use "uuidgen" to generate one if required.
> > > >= # The default behavior is to generate a new UUID each time the guest is st= arted.
> > > > #uuid =3D "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX= XXXX"
> > > >
> > > > # Enable Microsoft= Hyper-V compatibile paravirtualisation /
> > > > # enligh= tenment interfaces. Turning this on can improve Windows guest
> >= ; > > # performance and is therefore recommended
> > > = > #viridian =3D 1
> > > >
> > > > # I= nitial memory allocation (MB)
> > > > memory =3D 512
= > > > >
> > > > # Maximum memory (MB)
&g= t; > > > # If this is greater than `memory' then the slack will st= art ballooned
> > > > # (this assumes guest kernel support= for ballooning)
> > > > #maxmem =3D 512
> > &g= t; >
> > > > # Number of VCPUS
> > > >= ; vcpus =3D 2
> > > >
> > > > # Network = devices
> > > > # A list of 'vifspec' entries as described= in
> > > > # docs/misc/xl-network-configuration.markdown<= br />> > > > vif =3D [ 'bridge=3Dbr0' ]
> > > >= ;
> > > > # Disk Devices
> > > > # A lis= t of `diskspec' entries as described in
> > > > # docs/mis= c/xl-disk-configuration.txt
> > > > disk =3D [ '/dev/vg0/g= uest-linux-1,raw,xvda,rw' ]
> > > >
> > > &= gt; # Guest VGA console configuration, either SDL or VNC
> > >= ; > sdl =3D 1
> > > > #vnc =3D 1
> > > &g= t;
> > > >

> > > > =C2=A0

> Message du 06/08/14 10:03
> > > > >= ; De : "Gilles DALMAS" <gdalmas@wa= nadoo.fr>
> > > > > A : "mirageos-devel@lists.xenproject.org" &l= t;mirageos-devel@lis= ts.xenproject.org>
> > > > > Copie =C3=A0 :
> > > > > Objet : [MirageOS-devel] error when i create hvm= guest
> > > > >
> > > > >

> > > > > hello,

> > > > > I have this error when i execute :

> > > > > =C2=A0

> > > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/x= en/xl.conf
> > > > Parsing config from /etc/xen/xl.conf> > > > libxl: debug: libxl_create.c:1342:do_domain_create: = ao 0x31f00: create: how=3D(nil) callback=3D(nil) poller=3D0x32578
>= > > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info= _setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No = such file or directory
> > > > libxl: debug: libxl_device.= c:251:libxl__device_disk_set_backend: Disk vdev=3Dxvda spec.backend=3Dunkno= wn
> > > > libxl: error: libxl_device.c:265:libxl__device_= disk_set_backend: Disk vdev=3Dxvda failed to stat: /dev/vg0/guest-linux-1: = No such file or directory
> > > > libxl: error: libxl_dm.c= :1467:kill_device_model: unable to find device model pid in /local/domain/9= /image/device-model-pid
> > > > libxl: error: libxl.c:1421= :libxl__destroy_domid: libxl__destroy_device_model failed for 9
> &= gt; > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f= 00: complete, rc=3D-3
> > > > libxl: debug: libxl_create.c= :1356:do_domain_create: ao 0x31f00: inprogress: poller=3D0x32578, flags=3Di= c
> > > > libxl: debug: libxl_event.c:1563:libxl__ao__dest= roy: ao 0x31f00: destroy
> > > > xc: debug: hypercall buff= er: total allocations:26 total releases:26
> > > > xc: deb= ug: hypercall buffer: current allocations:0 maximum allocations:2
>= > > > xc: debug: hypercall buffer: cache current size:2
>= > > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:= 2

> > > > > =C2=A0

> > > > > i have a cubietruck arm and i have installed qe= mu-system-arm and qemu-system-x86

> > > > > =C2=A0


> > > >
> > > >
> > > &g= t; _______________________________________________
> > > >= MirageOS-devel mailing list
> > > > MirageOS-devel@lists.xenproject.org> > > > http://lists.xenproject.org/cgi-bin/mailman/li= stinfo/mirageos-devel
> > > >
> > > >= ;
_______________________________________________
>= > > > MirageOS-devel mailing list
> > >= ; > MirageO= S-devel@lists.xenproject.org
> > > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > > >

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

>
------=_Part_1037_1751468479.1407656810315-- --===============6906396712148052190== 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 --===============6906396712148052190==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 18:20:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 18:20: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 1XGXjO-0003CP-ET; Sun, 10 Aug 2014 18:20:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGXjN-0003CK-Et for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 18:20:33 +0000 Received: from [85.158.139.211:55618] by server-2.bemta-5.messagelabs.com id AA/1B-31832-0F7B7E35; Sun, 10 Aug 2014 18:20:32 +0000 X-Env-Sender: pszmk1@nottingham.ac.uk X-Msg-Ref: server-4.tower-206.messagelabs.com!1407694831!12927585!1 X-Originating-IP: [93.159.202.52] 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 20959 invoked from network); 10 Aug 2014 18:20:31 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-4.tower-206.messagelabs.com with SMTP; 10 Aug 2014 18:20:31 -0000 Received: (qmail 25304 invoked from network); 10 Aug 2014 18:20:31 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 10 Aug 2014 18:20:31 -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 22665-08 for ; Sun, 10 Aug 2014 19:20:24 +0100 (BST) Received: (qmail 25168 invoked by uid 599); 10 Aug 2014 18:20:24 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 10 Aug 2014 19:20:24 +0100 Received: from cpc8-stap10-2-0-cust247.12-2.cable.virginm.net ([81.98.135.248] helo=[192.168.0.3]) by smtp3.nottingham.ac.uk with esmtpsa (UNKNOWN:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1XGXjD-0002wU-8E for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 19:20:23 +0100 Message-ID: <53E7B7E0.9020000@nottingham.ac.uk> Date: Sun, 10 Aug 2014 19:20:16 +0100 From: Masoud Koleini 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-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Subject: [MirageOS-devel] Network device in promiscuous mode X-BeenThere: mirageos-devel@lists.xenproject.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 want to set my network device in promiscuous mode to capture all the frames. I am looking for a function similar to Net.Manager.set_promiscuous In mirage-net, which is the older versions of tcpip library. Does tcpip library have such a function? Thanks. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 18:20:41 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 18:20: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 1XGXjO-0003CP-ET; Sun, 10 Aug 2014 18:20:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGXjN-0003CK-Et for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 18:20:33 +0000 Received: from [85.158.139.211:55618] by server-2.bemta-5.messagelabs.com id AA/1B-31832-0F7B7E35; Sun, 10 Aug 2014 18:20:32 +0000 X-Env-Sender: pszmk1@nottingham.ac.uk X-Msg-Ref: server-4.tower-206.messagelabs.com!1407694831!12927585!1 X-Originating-IP: [93.159.202.52] 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 20959 invoked from network); 10 Aug 2014 18:20:31 -0000 Received: from engine03-20433-10.icritical.com (HELO engine03-20433-10.icritical.com) (93.159.202.52) by server-4.tower-206.messagelabs.com with SMTP; 10 Aug 2014 18:20:31 -0000 Received: (qmail 25304 invoked from network); 10 Aug 2014 18:20:31 -0000 Received: from localhost (127.0.0.1) by engine03-20433-10.icritical.com with SMTP; 10 Aug 2014 18:20:31 -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 22665-08 for ; Sun, 10 Aug 2014 19:20:24 +0100 (BST) Received: (qmail 25168 invoked by uid 599); 10 Aug 2014 18:20:24 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-10.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 10 Aug 2014 19:20:24 +0100 Received: from cpc8-stap10-2-0-cust247.12-2.cable.virginm.net ([81.98.135.248] helo=[192.168.0.3]) by smtp3.nottingham.ac.uk with esmtpsa (UNKNOWN:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1XGXjD-0002wU-8E for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 19:20:23 +0100 Message-ID: <53E7B7E0.9020000@nottingham.ac.uk> Date: Sun, 10 Aug 2014 19:20:16 +0100 From: Masoud Koleini 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-Virus-Scanned: by iCritical at engine03-20433-10.icritical.com Subject: [MirageOS-devel] Network device in promiscuous mode X-BeenThere: mirageos-devel@lists.xenproject.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 want to set my network device in promiscuous mode to capture all the frames. I am looking for a function similar to Net.Manager.set_promiscuous In mirage-net, which is the older versions of tcpip library. Does tcpip library have such a function? Thanks. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 18:41:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 18:41: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 1XGY3B-0003Oa-3E; Sun, 10 Aug 2014 18:41:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGY3A-0003OV-JA for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 18:41:00 +0000 Received: from [85.158.137.68:27665] by server-3.bemta-3.messagelabs.com id 07/6B-22751-BBCB7E35; Sun, 10 Aug 2014 18:40:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1407696058!12857997!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 13783 invoked from network); 10 Aug 2014 18:40:59 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 10 Aug 2014 18:40:59 -0000 Received: (qmail 28544 invoked by uid 634); 10 Aug 2014 18:40:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 10 Aug 2014 19:40:57 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <53E7B7E0.9020000@nottingham.ac.uk> Date: Sun, 10 Aug 2014 19:40:56 +0100 Message-Id: References: <53E7B7E0.9020000@nottingham.ac.uk> To: Masoud Koleini 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] Network device in promiscuous mode X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Aug 2014, at 19:20, Masoud Koleini wrote: > Hi all, > > I want to set my network device in promiscuous mode to capture all the frames. I am looking for a function similar to Net.Manager.set_promiscuous In mirage-net, which is the older versions of tcpip library. Does tcpip library have such a function? Hi Masoud, There's no such function, but an easy way to accomplish this is by assembling a manual stack that passes all the frames into whatever library you want. See mirage/mirage-skeleton in the ethifv4/ directory for an example. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 18:41:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 18:41: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 1XGY3B-0003Oa-3E; Sun, 10 Aug 2014 18:41:01 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGY3A-0003OV-JA for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 18:41:00 +0000 Received: from [85.158.137.68:27665] by server-3.bemta-3.messagelabs.com id 07/6B-22751-BBCB7E35; Sun, 10 Aug 2014 18:40:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-31.messagelabs.com!1407696058!12857997!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 13783 invoked from network); 10 Aug 2014 18:40:59 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-31.messagelabs.com with SMTP; 10 Aug 2014 18:40:59 -0000 Received: (qmail 28544 invoked by uid 634); 10 Aug 2014 18:40:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 10 Aug 2014 19:40:57 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <53E7B7E0.9020000@nottingham.ac.uk> Date: Sun, 10 Aug 2014 19:40:56 +0100 Message-Id: References: <53E7B7E0.9020000@nottingham.ac.uk> To: Masoud Koleini 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] Network device in promiscuous mode X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Aug 2014, at 19:20, Masoud Koleini wrote: > Hi all, > > I want to set my network device in promiscuous mode to capture all the frames. I am looking for a function similar to Net.Manager.set_promiscuous In mirage-net, which is the older versions of tcpip library. Does tcpip library have such a function? Hi Masoud, There's no such function, but an easy way to accomplish this is by assembling a manual stack that passes all the frames into whatever library you want. See mirage/mirage-skeleton in the ethifv4/ directory for an example. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 19:33:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 19:33:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGYs1-00046i-5i; Sun, 10 Aug 2014 19:33:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGYs0-00046U-Br for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 19:33:32 +0000 Received: from [85.158.137.68:24263] by server-11.bemta-3.messagelabs.com id EC/48-27768-B09C7E35; Sun, 10 Aug 2014 19:33:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1407699210!12856694!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28792 invoked from network); 10 Aug 2014 19:33:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-31.messagelabs.com with SMTP; 10 Aug 2014 19:33:30 -0000 Received: (qmail 19767 invoked by uid 634); 10 Aug 2014 19:33: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 cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 10 Aug 2014 20:33:24 +0100 From: Anil Madhavapeddy Date: Sun, 10 Aug 2014 20:33:23 +0100 Message-Id: <1B51829C-343C-4F0E-90CF-C9B5F4596226@recoil.org> To: OPAM devel 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 Cc: mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org Subject: [MirageOS-devel] We have binary OPAM RPMs! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Thanks to help from Euan Harris and Jon Ludlam at the recent OCaml Compiler Hackathon at Citrix, I've managed to coax the OpenSUSE Build Service into generating binary RPMs for Fedora 19/20, CentOS 6/7 and RHEL7! WWW: https://build.opensuse.org/package/show/home:ocaml/opam# Download: http://software.opensuse.org/download.html?project=home%3Aocaml&package=opam I've only tried this on a CentOS 6 VM so far, and it's working great. Since the version of OCaml packaged there is 3.11.2, our RPMs bootstrap themselves by using a local copy of OCaml to build OPAM. The resulting yum installation is working successfully via "opam init --comp=4.01.0" on CentOS 6. Note that only OPAM 1.2.0beta3 is packaged up like this. I haven't gone back to the 1.1.x series as I don't think it's worth the maintenance burden at this stage. For the curious, here's the OpenSUSE Build Service instructions that combine what Jon/I have been doing: https://gist.github.com/avsm/09fd0f3944fecd8a8ee3 In theory, the build service should do non-x86 builds (ARM, PPC, etc), but in practise the infrastructure seems completely broken and fail in interesting ways. Has anyone ever successfully had this working? CCing xen-api as well, since this is probably of use to the xapi packaging efforts on CentOS. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 10 19:33:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 10 Aug 2014 19:33:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGYs1-00046i-5i; Sun, 10 Aug 2014 19:33:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGYs0-00046U-Br for mirageos-devel@lists.xenproject.org; Sun, 10 Aug 2014 19:33:32 +0000 Received: from [85.158.137.68:24263] by server-11.bemta-3.messagelabs.com id EC/48-27768-B09C7E35; Sun, 10 Aug 2014 19:33:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-31.messagelabs.com!1407699210!12856694!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.2 required=7.0 tests=MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28792 invoked from network); 10 Aug 2014 19:33:30 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-31.messagelabs.com with SMTP; 10 Aug 2014 19:33:30 -0000 Received: (qmail 19767 invoked by uid 634); 10 Aug 2014 19:33: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 cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 10 Aug 2014 20:33:24 +0100 From: Anil Madhavapeddy Date: Sun, 10 Aug 2014 20:33:23 +0100 Message-Id: <1B51829C-343C-4F0E-90CF-C9B5F4596226@recoil.org> To: OPAM devel 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 Cc: mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org Subject: [MirageOS-devel] We have binary OPAM RPMs! X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Thanks to help from Euan Harris and Jon Ludlam at the recent OCaml Compiler Hackathon at Citrix, I've managed to coax the OpenSUSE Build Service into generating binary RPMs for Fedora 19/20, CentOS 6/7 and RHEL7! WWW: https://build.opensuse.org/package/show/home:ocaml/opam# Download: http://software.opensuse.org/download.html?project=home%3Aocaml&package=opam I've only tried this on a CentOS 6 VM so far, and it's working great. Since the version of OCaml packaged there is 3.11.2, our RPMs bootstrap themselves by using a local copy of OCaml to build OPAM. The resulting yum installation is working successfully via "opam init --comp=4.01.0" on CentOS 6. Note that only OPAM 1.2.0beta3 is packaged up like this. I haven't gone back to the 1.1.x series as I don't think it's worth the maintenance burden at this stage. For the curious, here's the OpenSUSE Build Service instructions that combine what Jon/I have been doing: https://gist.github.com/avsm/09fd0f3944fecd8a8ee3 In theory, the build service should do non-x86 builds (ARM, PPC, etc), but in practise the infrastructure seems completely broken and fail in interesting ways. Has anyone ever successfully had this working? CCing xen-api as well, since this is probably of use to the xapi packaging efforts on CentOS. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Aug 11 10:42:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 10:42: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 1XGn37-0006BZ-BX; Mon, 11 Aug 2014 10:41:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGn36-0006BP-8I for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 10:41:56 +0000 Received: from [85.158.137.68:37724] by server-12.bemta-3.messagelabs.com id BF/3B-02460-2FD98E35; Mon, 11 Aug 2014 10:41:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1407753713!13026954!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 24241 invoked from network); 11 Aug 2014 10:41:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 11 Aug 2014 10:41:53 -0000 Received: (qmail 27671 invoked by uid 634); 11 Aug 2014 10:41:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from no-dns-yet.demon.co.uk (HELO [192.168.14.205]) (62.49.66.12) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 11 Aug 2014 11:41:52 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1407749779.2986053.151340345.7854E1DA@webmail.messagingengine.com> Date: Mon, 11 Aug 2014 11:41:50 +0100 Message-Id: <6B503910-17CB-4770-920C-ECD7D08453DB@recoil.org> References: <1407749779.2986053.151340345.7854E1DA@webmail.messagingengine.com> To: Magnus Skjegstad 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] Xen-arm-builder changes X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 Aug 2014, at 10:36, Magnus Skjegstad wrote: > I have updated xen-arm-builder to support installing driver firmware on > the disk image by adding a FIRMWARE ?= in Makefile and cloning > linux-firmware. I have also enabled support for two wireless adapters > and Cubieboard LEDs in the kernel. I have also set noatime,nodiratime in > fstab to speed up disk access. > > The firmware-change is also documented in the README.md. > > I don't know if you want to merge any of these changes back to the main > repo? > > https://github.com/MagnusS/xen-arm-builder/commits/master CCing the devel list -- all of these look useful to me. Should we also set the 'discard' option to enable TRIM on SSDs (or would this cause failures if the media doesn't support trimming?) Do send a pull request on the existing changes and I'll merge/rebuild. Incidentally, I added a Dockerfile to xen-arm-builder in order to make it quicker to fetch a working tree. The limits of containers start showing up quite fast unfortunately, since the only way to mount a loopback device is to use Docker in 'privileged mode', which none of the public build services do. Still, if anyone wants to play with it, you just: sudo docker.io pull avsm/xen-arm-builder sudo docker.io run -t avsm/xen-arm-builder bash Can't do much with it after that unless you're in a privileged local container (if anyone gets that to work, drop a note on this thread). -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 Aug 11 10:42:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 10:42: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 1XGn37-0006BZ-BX; Mon, 11 Aug 2014 10:41:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGn36-0006BP-8I for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 10:41:56 +0000 Received: from [85.158.137.68:37724] by server-12.bemta-3.messagelabs.com id BF/3B-02460-2FD98E35; Mon, 11 Aug 2014 10:41:54 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1407753713!13026954!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 24241 invoked from network); 11 Aug 2014 10:41:53 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 11 Aug 2014 10:41:53 -0000 Received: (qmail 27671 invoked by uid 634); 11 Aug 2014 10:41:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from no-dns-yet.demon.co.uk (HELO [192.168.14.205]) (62.49.66.12) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 11 Aug 2014 11:41:52 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1407749779.2986053.151340345.7854E1DA@webmail.messagingengine.com> Date: Mon, 11 Aug 2014 11:41:50 +0100 Message-Id: <6B503910-17CB-4770-920C-ECD7D08453DB@recoil.org> References: <1407749779.2986053.151340345.7854E1DA@webmail.messagingengine.com> To: Magnus Skjegstad 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] Xen-arm-builder changes X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 Aug 2014, at 10:36, Magnus Skjegstad wrote: > I have updated xen-arm-builder to support installing driver firmware on > the disk image by adding a FIRMWARE ?= in Makefile and cloning > linux-firmware. I have also enabled support for two wireless adapters > and Cubieboard LEDs in the kernel. I have also set noatime,nodiratime in > fstab to speed up disk access. > > The firmware-change is also documented in the README.md. > > I don't know if you want to merge any of these changes back to the main > repo? > > https://github.com/MagnusS/xen-arm-builder/commits/master CCing the devel list -- all of these look useful to me. Should we also set the 'discard' option to enable TRIM on SSDs (or would this cause failures if the media doesn't support trimming?) Do send a pull request on the existing changes and I'll merge/rebuild. Incidentally, I added a Dockerfile to xen-arm-builder in order to make it quicker to fetch a working tree. The limits of containers start showing up quite fast unfortunately, since the only way to mount a loopback device is to use Docker in 'privileged mode', which none of the public build services do. Still, if anyone wants to play with it, you just: sudo docker.io pull avsm/xen-arm-builder sudo docker.io run -t avsm/xen-arm-builder bash Can't do much with it after that unless you're in a privileged local container (if anyone gets that to work, drop a note on this thread). -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 Aug 11 10:48:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 10:48: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 1XGn99-0006JF-8b; Mon, 11 Aug 2014 10:48:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGn97-0006J9-CT for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 10:48:09 +0000 Received: from [85.158.139.211:51780] by server-1.bemta-5.messagelabs.com id 2E/D7-17892-86F98E35; Mon, 11 Aug 2014 10:48:08 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1407754086!13010339!1 X-Originating-IP: [209.85.219.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 25779 invoked from network); 11 Aug 2014 10:48:08 -0000 Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Aug 2014 10:48:08 -0000 Received: by mail-oa0-f53.google.com with SMTP id j17so5789991oag.26 for ; Mon, 11 Aug 2014 03:48:06 -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=Lxc0t9jeAA5VifAeH7GZ1NtQykfL8lEBeBT9c1IGPas=; b=s5W6FaPd9pTpW2CzIKcUUma/W6zJMePyCqgu+aLCsyGYRwv0lq/l+kL5hhJLVrIVjp bFqog0Ja0WxlZ4ad0IFCNs4+Khs1cXN4uDW9XOVQpCA2dewZ0UGLZR8cXS1p7GgdUMOK lLJzHM66wbgYmW7hV0mzX0+tIRElBq6qsgkObwDch1FDlFhDcsdLbTYghs5Cu7Aw9h5Z yYwjIfETE4xzg7ZqTUiUpVweQ5DcPaGXluYf3c69hJHPZFN3BZ3nD94tGqhxwn2OR901 aJ1+OM4HjOIkki+dG3Anb6h+BERxJRqT72Lq5DYWqKuL1QH/DiSMYv/gOBCU3B9AinTB St+Q== MIME-Version: 1.0 X-Received: by 10.60.220.169 with SMTP id px9mr8186712oec.67.1407754086473; Mon, 11 Aug 2014 03:48:06 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Mon, 11 Aug 2014 03:48:06 -0700 (PDT) In-Reply-To: <6B503910-17CB-4770-920C-ECD7D08453DB@recoil.org> References: <1407749779.2986053.151340345.7854E1DA@webmail.messagingengine.com> <6B503910-17CB-4770-920C-ECD7D08453DB@recoil.org> Date: Mon, 11 Aug 2014 11:48:06 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: Magnus Skjegstad , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen-arm-builder changes X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 August 2014 11:41, Anil Madhavapeddy wrote: > On 11 Aug 2014, at 10:36, Magnus Skjegstad wrote: > >> I have updated xen-arm-builder to support installing driver firmware on >> the disk image by adding a FIRMWARE ?= in Makefile and cloning >> linux-firmware. I have also enabled support for two wireless adapters >> and Cubieboard LEDs in the kernel. I have also set noatime,nodiratime in >> fstab to speed up disk access. >> >> The firmware-change is also documented in the README.md. >> >> I don't know if you want to merge any of these changes back to the main >> repo? >> >> https://github.com/MagnusS/xen-arm-builder/commits/master > > CCing the devel list -- all of these look useful to me. Should we also > set the 'discard' option to enable TRIM on SSDs (or would this cause > failures if the media doesn't support trimming?) > > Do send a pull request on the existing changes and I'll merge/rebuild. > > Incidentally, I added a Dockerfile to xen-arm-builder in order to make > it quicker to fetch a working tree. The limits of containers start > showing up quite fast unfortunately, since the only way to mount a > loopback device is to use Docker in 'privileged mode', which none of the > public build services do. Still, if anyone wants to play with it, you > just: > > sudo docker.io pull avsm/xen-arm-builder > sudo docker.io run -t avsm/xen-arm-builder bash > > Can't do much with it after that unless you're in a privileged local > container (if anyone gets that to work, drop a note on this thread). I've always been building it in a privileged docker container, since I'm not running Ubuntu. The command I use to enter my container is: docker run -e "http_proxy=http://192.168.0.11:8123/" --privileged -it -v `pwd`:/xen-arm-builder --entrypoint /bin/bash -w /xen-arm-builder xen-sdcard-builder The proxy is to save redownloading all the debs each time. To get ARM emulation support, I also have to run this inside the container (affects the host too, I think): /etc/init.d/binfmt-support start -- 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 Mon Aug 11 10:48:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 10:48: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 1XGn99-0006JF-8b; Mon, 11 Aug 2014 10:48:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGn97-0006J9-CT for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 10:48:09 +0000 Received: from [85.158.139.211:51780] by server-1.bemta-5.messagelabs.com id 2E/D7-17892-86F98E35; Mon, 11 Aug 2014 10:48:08 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1407754086!13010339!1 X-Originating-IP: [209.85.219.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 25779 invoked from network); 11 Aug 2014 10:48:08 -0000 Received: from mail-oa0-f53.google.com (HELO mail-oa0-f53.google.com) (209.85.219.53) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Aug 2014 10:48:08 -0000 Received: by mail-oa0-f53.google.com with SMTP id j17so5789991oag.26 for ; Mon, 11 Aug 2014 03:48:06 -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=Lxc0t9jeAA5VifAeH7GZ1NtQykfL8lEBeBT9c1IGPas=; b=s5W6FaPd9pTpW2CzIKcUUma/W6zJMePyCqgu+aLCsyGYRwv0lq/l+kL5hhJLVrIVjp bFqog0Ja0WxlZ4ad0IFCNs4+Khs1cXN4uDW9XOVQpCA2dewZ0UGLZR8cXS1p7GgdUMOK lLJzHM66wbgYmW7hV0mzX0+tIRElBq6qsgkObwDch1FDlFhDcsdLbTYghs5Cu7Aw9h5Z yYwjIfETE4xzg7ZqTUiUpVweQ5DcPaGXluYf3c69hJHPZFN3BZ3nD94tGqhxwn2OR901 aJ1+OM4HjOIkki+dG3Anb6h+BERxJRqT72Lq5DYWqKuL1QH/DiSMYv/gOBCU3B9AinTB St+Q== MIME-Version: 1.0 X-Received: by 10.60.220.169 with SMTP id px9mr8186712oec.67.1407754086473; Mon, 11 Aug 2014 03:48:06 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Mon, 11 Aug 2014 03:48:06 -0700 (PDT) In-Reply-To: <6B503910-17CB-4770-920C-ECD7D08453DB@recoil.org> References: <1407749779.2986053.151340345.7854E1DA@webmail.messagingengine.com> <6B503910-17CB-4770-920C-ECD7D08453DB@recoil.org> Date: Mon, 11 Aug 2014 11:48:06 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: Magnus Skjegstad , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Xen-arm-builder changes X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 August 2014 11:41, Anil Madhavapeddy wrote: > On 11 Aug 2014, at 10:36, Magnus Skjegstad wrote: > >> I have updated xen-arm-builder to support installing driver firmware on >> the disk image by adding a FIRMWARE ?= in Makefile and cloning >> linux-firmware. I have also enabled support for two wireless adapters >> and Cubieboard LEDs in the kernel. I have also set noatime,nodiratime in >> fstab to speed up disk access. >> >> The firmware-change is also documented in the README.md. >> >> I don't know if you want to merge any of these changes back to the main >> repo? >> >> https://github.com/MagnusS/xen-arm-builder/commits/master > > CCing the devel list -- all of these look useful to me. Should we also > set the 'discard' option to enable TRIM on SSDs (or would this cause > failures if the media doesn't support trimming?) > > Do send a pull request on the existing changes and I'll merge/rebuild. > > Incidentally, I added a Dockerfile to xen-arm-builder in order to make > it quicker to fetch a working tree. The limits of containers start > showing up quite fast unfortunately, since the only way to mount a > loopback device is to use Docker in 'privileged mode', which none of the > public build services do. Still, if anyone wants to play with it, you > just: > > sudo docker.io pull avsm/xen-arm-builder > sudo docker.io run -t avsm/xen-arm-builder bash > > Can't do much with it after that unless you're in a privileged local > container (if anyone gets that to work, drop a note on this thread). I've always been building it in a privileged docker container, since I'm not running Ubuntu. The command I use to enter my container is: docker run -e "http_proxy=http://192.168.0.11:8123/" --privileged -it -v `pwd`:/xen-arm-builder --entrypoint /bin/bash -w /xen-arm-builder xen-sdcard-builder The proxy is to save redownloading all the debs each time. To get ARM emulation support, I also have to run this inside the container (affects the host too, I think): /etc/init.d/binfmt-support start -- 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 Mon Aug 11 11:32:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 11:32: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 1XGnq3-0007e1-1d; Mon, 11 Aug 2014 11:32:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGnq1-0007dw-7z for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 11:32:29 +0000 Received: from [85.158.143.35:50700] by server-1.bemta-4.messagelabs.com id D0/ED-05872-CC9A8E35; Mon, 11 Aug 2014 11:32:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1407756746!12233269!1 X-Originating-IP: [209.85.219.44] 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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11715 invoked from network); 11 Aug 2014 11:32:27 -0000 Received: from mail-oa0-f44.google.com (HELO mail-oa0-f44.google.com) (209.85.219.44) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Aug 2014 11:32:27 -0000 Received: by mail-oa0-f44.google.com with SMTP id eb12so6051317oac.31 for ; Mon, 11 Aug 2014 04:32:26 -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=6/sBUc2OwOew2YUhAd9p3B/QoyAFKNPJMmAor8yAAMI=; b=ybm9s0C1D+uyacpbmbBMSWXLqWetq679cKbP4y5o92e4DrsMvbQ2zMW62DsfcpWOS5 HSgP0PPdPeE5jgIb7T9yo5VcwBbRXjWXRDx8M70h4H4B4IXzwYUDeB+Qb1TFHRTC2r2F ZRWxl75U45vL1ndYwZnSpR88/0rUyS5lZr0hl1g+r32GMHrMgZbhFCdkDc86+Z6NYVHj RZKMJBIfdzpt4Pb8UR3eOPOPINtl8K50YD5H7hJf2BmYHywRAFrB2CU4DNL9FY2XBq4D jE8DXTGcFUHb8A2osUhf2gnebtIvfnXcZ/PpdfbeuHnvbXJNffqJORlefRv92etS1JUg FTcQ== MIME-Version: 1.0 X-Received: by 10.60.121.67 with SMTP id li3mr48489299oeb.17.1407756745941; Mon, 11 Aug 2014 04:32:25 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Mon, 11 Aug 2014 04:32:25 -0700 (PDT) Date: Mon, 11 Aug 2014 12:32:25 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [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 Has anyone made any tools for profiling on Xen? I want to see why my network service on Xen/ARM only gets about 5 MB/s (while a Linux guest gets about 45 MB/s). I tried compiling with profiling on ("true: profile" in the _tags) and wrote a __gnu_mcount_nc function to dump all the results to a buffer [1], plus a script to turn the addresses back into symbols and guess the nesting (a bit unreliable, as it doesn't tell you when the function finishes). Here's an example CSV of the output (the unikernel waits for a TCP connection and then streams data to it as fast as it can): http://test.roscidus.com/static/sample-output.csv.bz2 I haven't checked it carefully to see if it's correct - this is just an example of the kind of output. It shows the call graph and the (cumulative) time spent in each function. Since it doesn't know the end times, it assumes a function runs until one of its parents calls something else. Initially, the buffer filled up almost instantly with calls to "stub_evtchn_test_and_clear". Looks like we call this once for each of the 4096 channels every time we look for work. I'm not sure whether this hurts performance much, but I reduced the number of channels to 10 to make the output readable. The call graph is missing some nodes because I didn't compile e.g. Lwt with profiling on. These functions have "?" shown for the time and no parent. Is there an easy way to get OPAM to recompile everything for profiling? Does anyone have better tools for doing this? Especially something that can link up async Lwt calls (or even track remote calls, like Causeway [2]). Anyway, I think it's quite cool to be able able to trace every kernel call - even "irq_handler" shows up in the output! [1] https://github.com/talex5/xen/commits/profiling [2] http://wiki.erights.org/wiki/Causeway -- 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 Mon Aug 11 11:32:33 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 11:32: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 1XGnq3-0007e1-1d; Mon, 11 Aug 2014 11:32:31 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGnq1-0007dw-7z for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 11:32:29 +0000 Received: from [85.158.143.35:50700] by server-1.bemta-4.messagelabs.com id D0/ED-05872-CC9A8E35; Mon, 11 Aug 2014 11:32:28 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1407756746!12233269!1 X-Originating-IP: [209.85.219.44] 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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11715 invoked from network); 11 Aug 2014 11:32:27 -0000 Received: from mail-oa0-f44.google.com (HELO mail-oa0-f44.google.com) (209.85.219.44) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Aug 2014 11:32:27 -0000 Received: by mail-oa0-f44.google.com with SMTP id eb12so6051317oac.31 for ; Mon, 11 Aug 2014 04:32:26 -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=6/sBUc2OwOew2YUhAd9p3B/QoyAFKNPJMmAor8yAAMI=; b=ybm9s0C1D+uyacpbmbBMSWXLqWetq679cKbP4y5o92e4DrsMvbQ2zMW62DsfcpWOS5 HSgP0PPdPeE5jgIb7T9yo5VcwBbRXjWXRDx8M70h4H4B4IXzwYUDeB+Qb1TFHRTC2r2F ZRWxl75U45vL1ndYwZnSpR88/0rUyS5lZr0hl1g+r32GMHrMgZbhFCdkDc86+Z6NYVHj RZKMJBIfdzpt4Pb8UR3eOPOPINtl8K50YD5H7hJf2BmYHywRAFrB2CU4DNL9FY2XBq4D jE8DXTGcFUHb8A2osUhf2gnebtIvfnXcZ/PpdfbeuHnvbXJNffqJORlefRv92etS1JUg FTcQ== MIME-Version: 1.0 X-Received: by 10.60.121.67 with SMTP id li3mr48489299oeb.17.1407756745941; Mon, 11 Aug 2014 04:32:25 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Mon, 11 Aug 2014 04:32:25 -0700 (PDT) Date: Mon, 11 Aug 2014 12:32:25 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [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 Has anyone made any tools for profiling on Xen? I want to see why my network service on Xen/ARM only gets about 5 MB/s (while a Linux guest gets about 45 MB/s). I tried compiling with profiling on ("true: profile" in the _tags) and wrote a __gnu_mcount_nc function to dump all the results to a buffer [1], plus a script to turn the addresses back into symbols and guess the nesting (a bit unreliable, as it doesn't tell you when the function finishes). Here's an example CSV of the output (the unikernel waits for a TCP connection and then streams data to it as fast as it can): http://test.roscidus.com/static/sample-output.csv.bz2 I haven't checked it carefully to see if it's correct - this is just an example of the kind of output. It shows the call graph and the (cumulative) time spent in each function. Since it doesn't know the end times, it assumes a function runs until one of its parents calls something else. Initially, the buffer filled up almost instantly with calls to "stub_evtchn_test_and_clear". Looks like we call this once for each of the 4096 channels every time we look for work. I'm not sure whether this hurts performance much, but I reduced the number of channels to 10 to make the output readable. The call graph is missing some nodes because I didn't compile e.g. Lwt with profiling on. These functions have "?" shown for the time and no parent. Is there an easy way to get OPAM to recompile everything for profiling? Does anyone have better tools for doing this? Especially something that can link up async Lwt calls (or even track remote calls, like Causeway [2]). Anyway, I think it's quite cool to be able able to trace every kernel call - even "irq_handler" shows up in the output! [1] https://github.com/talex5/xen/commits/profiling [2] http://wiki.erights.org/wiki/Causeway -- 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 Mon Aug 11 13:05:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 13:05: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 1XGpHU-0003mx-B1; Mon, 11 Aug 2014 13:04:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGpHT-0003ms-1L for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 13:04:55 +0000 Received: from [85.158.143.35:10861] by server-1.bemta-4.messagelabs.com id 1A/A7-05872-67FB8E35; Mon, 11 Aug 2014 13:04:54 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1407762291!12322255!1 X-Originating-IP: [209.85.220.41] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10821 invoked from network); 11 Aug 2014 13:04:52 -0000 Received: from mail-pa0-f41.google.com (HELO mail-pa0-f41.google.com) (209.85.220.41) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Aug 2014 13:04:52 -0000 Received: by mail-pa0-f41.google.com with SMTP id rd3so11160148pab.0 for ; Mon, 11 Aug 2014 06:04: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; bh=DfvZtVJyQN7efCxyjNKV8XDIYnh5Mc8uHd+jJvHEv8k=; b=spCjeN0TYRkwO6QVUQF5yhuz/OiG6jdaWZWbKM6bGw/UpMRIroO69MwWQw27Mmrs7c FwA6rlgUcxRgroeTN+rGL+OEk1F25lzdBa21nRVAizw3T3i3dbJ6t8XKVLAaD7lL7Pma Px6up9ZYTQyO7fw6UJmxHSN5Xws5C+Y0M8G0S5dwdjRKVEoJaHkLUluGf3BOgjOY7Cm0 REO5QSuFavyP/OSqPefMTwI1yv9e8J/WiYlw51uGH+3ckVA/yMAw9zebH1h+m85KmJjN dbtqgLsFk+BcgPhdFLRtfQq9TicQB1ammOBmchaIN5AZ6ftXyat5SxGOwS1vU3bNtnah jo3g== MIME-Version: 1.0 X-Received: by 10.66.124.226 with SMTP id ml2mr1315738pab.142.1407762290479; Mon, 11 Aug 2014 06:04:50 -0700 (PDT) Received: by 10.70.65.101 with HTTP; Mon, 11 Aug 2014 06:04:50 -0700 (PDT) In-Reply-To: References: Date: Mon, 11 Aug 2014 14:04:50 +0100 Message-ID: From: David Scott To: Thomas Leonard 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: multipart/mixed; boundary="===============3729040627462782768==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3729040627462782768== Content-Type: multipart/alternative; boundary=001a113452d440971805005a33a8 --001a113452d440971805005a33a8 Content-Type: text/plain; charset=UTF-8 On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard wrote: > Has anyone made any tools for profiling on Xen? > The closest thing I can think of is xentrace/xenalyse: http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenalyze/ This will tell you what Xen can see: eg how the vCPUs map to pCPUs and when they block on events etc. > > I want to see why my network service on Xen/ARM only gets about 5 MB/s > (while a Linux guest gets about 45 MB/s). > > I tried compiling with profiling on ("true: profile" in the _tags) and > wrote a __gnu_mcount_nc function to dump all the results to a buffer > [1], plus a script to turn the addresses back into symbols and guess > the nesting (a bit unreliable, as it doesn't tell you when the > function finishes). > > Here's an example CSV of the output (the unikernel waits for a TCP > connection and then streams data to it as fast as it can): > > http://test.roscidus.com/static/sample-output.csv.bz2 > > I haven't checked it carefully to see if it's correct - this is just > an example of the kind of output. It shows the call graph and the > (cumulative) time spent in each function. Since it doesn't know the > end times, it assumes a function runs until one of its parents calls > something else. > Cool -- it would be great to polish up a tool like this. Cheers, Dave > > Initially, the buffer filled up almost instantly with calls to > "stub_evtchn_test_and_clear". Looks like we call this once for each of > the 4096 channels every time we look for work. I'm not sure whether > this hurts performance much, but I reduced the number of channels to > 10 to make the output readable. > > The call graph is missing some nodes because I didn't compile e.g. Lwt > with profiling on. These functions have "?" shown for the time and no > parent. Is there an easy way to get OPAM to recompile everything for > profiling? > > Does anyone have better tools for doing this? Especially something > that can link up async Lwt calls (or even track remote calls, like > Causeway [2]). > > Anyway, I think it's quite cool to be able able to trace every kernel > call - even "irq_handler" shows up in the output! > > > [1] https://github.com/talex5/xen/commits/profiling > [2] http://wiki.erights.org/wiki/Causeway > > > -- > 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 > -- Dave Scott --001a113452d440971805005a33a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard <talex5@gmail.com><= /span> wrote:
Has anyone made any tools for profiling on Xen?

The closest thing I can think of is xentrace/xenalyse:<= /div>


This will tell you what Xen can see: eg how the v= CPUs map to pCPUs and when they block on events etc.

=C2=A0

I want to see why my network service on Xen/ARM only gets about 5 MB/s
(while a Linux guest gets about 45 MB/s).

I tried compiling with profiling on ("true: profile" in the _tags= ) and
wrote a __gnu_mcount_nc function to dump all the results to a buffer
[1], plus a script to turn the addresses back into symbols and guess
the nesting (a bit unreliable, as it doesn't tell you when the
function finishes).

Here's an example CSV of the output (the unikernel waits for a TCP
connection and then streams data to it as fast as it can):

=C2=A0 http://test.roscidus.com/static/sample-output.csv.bz2
I haven't checked it carefully to see if it's correct - this is jus= t
an example of the kind of output. It shows the call graph and the
(cumulative) time spent in each function. Since it doesn't know the
end times, it assumes a function runs until one of its parents calls
something else.

Cool -- it would be gre= at to polish up a tool like this.

Cheers,
Dave
=C2=A0

Initially, the buffer filled up almost instantly with calls to
"stub_evtchn_test_and_clear". Looks like we call this once for ea= ch of
the 4096 channels every time we look for work. I'm not sure whether
this hurts performance much, but I reduced the number of channels to
10 to make the output readable.

The call graph is missing some nodes because I didn't compile e.g. Lwt<= br> with profiling on. These functions have "?" shown for the time an= d no
parent. Is there an easy way to get OPAM to recompile everything for
profiling?

Does anyone have better tools for doing this? Especially something
that can link up async Lwt calls (or even track remote calls, like
Causeway [2]).

Anyway, I think it's quite cool to be able able to trace every kernel call - even "irq_handler" shows up in the output!


[1] https://github.com/talex5/xen/commits/profiling
[2] htt= p://wiki.erights.org/wiki/Causeway


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

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



-- Dave Scott
--001a113452d440971805005a33a8-- --===============3729040627462782768== 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 --===============3729040627462782768==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 11 13:05:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 11 Aug 2014 13:05: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 1XGpHU-0003mx-B1; Mon, 11 Aug 2014 13:04:56 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XGpHT-0003ms-1L for mirageos-devel@lists.xenproject.org; Mon, 11 Aug 2014 13:04:55 +0000 Received: from [85.158.143.35:10861] by server-1.bemta-4.messagelabs.com id 1A/A7-05872-67FB8E35; Mon, 11 Aug 2014 13:04:54 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1407762291!12322255!1 X-Originating-IP: [209.85.220.41] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, ML_RADAR_SPEW_LINKS_23, RCVD_BY_IP, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10821 invoked from network); 11 Aug 2014 13:04:52 -0000 Received: from mail-pa0-f41.google.com (HELO mail-pa0-f41.google.com) (209.85.220.41) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 11 Aug 2014 13:04:52 -0000 Received: by mail-pa0-f41.google.com with SMTP id rd3so11160148pab.0 for ; Mon, 11 Aug 2014 06:04: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; bh=DfvZtVJyQN7efCxyjNKV8XDIYnh5Mc8uHd+jJvHEv8k=; b=spCjeN0TYRkwO6QVUQF5yhuz/OiG6jdaWZWbKM6bGw/UpMRIroO69MwWQw27Mmrs7c FwA6rlgUcxRgroeTN+rGL+OEk1F25lzdBa21nRVAizw3T3i3dbJ6t8XKVLAaD7lL7Pma Px6up9ZYTQyO7fw6UJmxHSN5Xws5C+Y0M8G0S5dwdjRKVEoJaHkLUluGf3BOgjOY7Cm0 REO5QSuFavyP/OSqPefMTwI1yv9e8J/WiYlw51uGH+3ckVA/yMAw9zebH1h+m85KmJjN dbtqgLsFk+BcgPhdFLRtfQq9TicQB1ammOBmchaIN5AZ6ftXyat5SxGOwS1vU3bNtnah jo3g== MIME-Version: 1.0 X-Received: by 10.66.124.226 with SMTP id ml2mr1315738pab.142.1407762290479; Mon, 11 Aug 2014 06:04:50 -0700 (PDT) Received: by 10.70.65.101 with HTTP; Mon, 11 Aug 2014 06:04:50 -0700 (PDT) In-Reply-To: References: Date: Mon, 11 Aug 2014 14:04:50 +0100 Message-ID: From: David Scott To: Thomas Leonard 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: multipart/mixed; boundary="===============3729040627462782768==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3729040627462782768== Content-Type: multipart/alternative; boundary=001a113452d440971805005a33a8 --001a113452d440971805005a33a8 Content-Type: text/plain; charset=UTF-8 On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard wrote: > Has anyone made any tools for profiling on Xen? > The closest thing I can think of is xentrace/xenalyse: http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenalyze/ This will tell you what Xen can see: eg how the vCPUs map to pCPUs and when they block on events etc. > > I want to see why my network service on Xen/ARM only gets about 5 MB/s > (while a Linux guest gets about 45 MB/s). > > I tried compiling with profiling on ("true: profile" in the _tags) and > wrote a __gnu_mcount_nc function to dump all the results to a buffer > [1], plus a script to turn the addresses back into symbols and guess > the nesting (a bit unreliable, as it doesn't tell you when the > function finishes). > > Here's an example CSV of the output (the unikernel waits for a TCP > connection and then streams data to it as fast as it can): > > http://test.roscidus.com/static/sample-output.csv.bz2 > > I haven't checked it carefully to see if it's correct - this is just > an example of the kind of output. It shows the call graph and the > (cumulative) time spent in each function. Since it doesn't know the > end times, it assumes a function runs until one of its parents calls > something else. > Cool -- it would be great to polish up a tool like this. Cheers, Dave > > Initially, the buffer filled up almost instantly with calls to > "stub_evtchn_test_and_clear". Looks like we call this once for each of > the 4096 channels every time we look for work. I'm not sure whether > this hurts performance much, but I reduced the number of channels to > 10 to make the output readable. > > The call graph is missing some nodes because I didn't compile e.g. Lwt > with profiling on. These functions have "?" shown for the time and no > parent. Is there an easy way to get OPAM to recompile everything for > profiling? > > Does anyone have better tools for doing this? Especially something > that can link up async Lwt calls (or even track remote calls, like > Causeway [2]). > > Anyway, I think it's quite cool to be able able to trace every kernel > call - even "irq_handler" shows up in the output! > > > [1] https://github.com/talex5/xen/commits/profiling > [2] http://wiki.erights.org/wiki/Causeway > > > -- > 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 > -- Dave Scott --001a113452d440971805005a33a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard <talex5@gmail.com><= /span> wrote:
Has anyone made any tools for profiling on Xen?

The closest thing I can think of is xentrace/xenalyse:<= /div>


This will tell you what Xen can see: eg how the v= CPUs map to pCPUs and when they block on events etc.

=C2=A0

I want to see why my network service on Xen/ARM only gets about 5 MB/s
(while a Linux guest gets about 45 MB/s).

I tried compiling with profiling on ("true: profile" in the _tags= ) and
wrote a __gnu_mcount_nc function to dump all the results to a buffer
[1], plus a script to turn the addresses back into symbols and guess
the nesting (a bit unreliable, as it doesn't tell you when the
function finishes).

Here's an example CSV of the output (the unikernel waits for a TCP
connection and then streams data to it as fast as it can):

=C2=A0 http://test.roscidus.com/static/sample-output.csv.bz2
I haven't checked it carefully to see if it's correct - this is jus= t
an example of the kind of output. It shows the call graph and the
(cumulative) time spent in each function. Since it doesn't know the
end times, it assumes a function runs until one of its parents calls
something else.

Cool -- it would be gre= at to polish up a tool like this.

Cheers,
Dave
=C2=A0

Initially, the buffer filled up almost instantly with calls to
"stub_evtchn_test_and_clear". Looks like we call this once for ea= ch of
the 4096 channels every time we look for work. I'm not sure whether
this hurts performance much, but I reduced the number of channels to
10 to make the output readable.

The call graph is missing some nodes because I didn't compile e.g. Lwt<= br> with profiling on. These functions have "?" shown for the time an= d no
parent. Is there an easy way to get OPAM to recompile everything for
profiling?

Does anyone have better tools for doing this? Especially something
that can link up async Lwt calls (or even track remote calls, like
Causeway [2]).

Anyway, I think it's quite cool to be able able to trace every kernel call - even "irq_handler" shows up in the output!


[1] https://github.com/talex5/xen/commits/profiling
[2] htt= p://wiki.erights.org/wiki/Causeway


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

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



-- Dave Scott
--001a113452d440971805005a33a8-- --===============3729040627462782768== 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 --===============3729040627462782768==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 12 14:59:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 12 Aug 2014 14:59: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 1XHDXP-00087f-Hl; Tue, 12 Aug 2014 14:58:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHDXO-00087X-B3 for mirageos-devel@lists.xenproject.org; Tue, 12 Aug 2014 14:58:58 +0000 Received: from [85.158.143.35:29162] by server-2.bemta-4.messagelabs.com id A8/FF-04525-1BB2AE35; Tue, 12 Aug 2014 14:58:57 +0000 X-Env-Sender: hwandori@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1407855535!12594765!1 X-Originating-IP: [209.85.160.178] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23675 invoked from network); 12 Aug 2014 14:58:56 -0000 Received: from mail-yk0-f178.google.com (HELO mail-yk0-f178.google.com) (209.85.160.178) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 12 Aug 2014 14:58:56 -0000 Received: by mail-yk0-f178.google.com with SMTP id 142so7170752ykq.37 for ; Tue, 12 Aug 2014 07:58:55 -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=XCX5wjBp4Zy5VVdhiggkAIq9QzAtFHFrBlKWwnubBWc=; b=XewYHTz7cHtSqX/i6R7Y9TeqSenyHrIIxReKMnXeyfGNTG9JmgrZ/C+5wpiTr8AEEP ZhpzBEAeEDIdBeHR4z2LZ98saoyekXdtVg7e55lBWtkv1fxxFIF/qbXA1dRyX/LSyTjY BXNPuxyf5jLp1PbDu/pBId4fyZHtOaTnVNlJtGXczHY88T92sQ4kQ2fxZsX4PNFsqi4u EE36OoBzX6G9eus5IisjKKcp6iT+HLRSWOJo52MKfxAw/bV5KEqyEcDLxb/1VkW0zyFa 5LjpyGGhfkG50WnILvldcGZtZlrlnkCMmgpOWiKC+Crfdp8cCsb6mxq0YpCZjpAPMmZo fHvA== X-Received: by 10.236.47.201 with SMTP id t49mr24824652yhb.123.1407855535636; Tue, 12 Aug 2014 07:58:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.144.194 with HTTP; Tue, 12 Aug 2014 07:58:35 -0700 (PDT) From: Hwanju Kim Date: Tue, 12 Aug 2014 15:58:35 +0100 X-Google-Sender-Auth: 9xQ1zrXVk6CmCJIMDHbmav9eRFc Message-ID: To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1881949927552452010==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1881949927552452010== Content-Type: multipart/alternative; boundary=089e01681de418cd1705006fe939 --089e01681de418cd1705006fe939 Content-Type: text/plain; charset=UTF-8 Hi, I've been playing with mirage-skeleton/static_website with unix backend and tap interface. I wonder if there is a right way of assigning a specific mac address to a mirage instance. What I want right now is to run multiple instances with different mac addresses using tap interface. I saw in mirage-net-unix a mac address is assigned randomly, but with the same seed by default makes all mac addresses the same. I just tweaked it by adding, in the static_website's main.ml generated by mirage tool, Random.init before Netif.connect "tap0" to get different an address, but I am sure this is not a proper way. Is there any way to do it? (I know that manual assignment of mac address is doable with xen backend). Cheers, Hwanju --089e01681de418cd1705006fe939 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable --089e01681de418cd1705006fe939-- --===============1881949927552452010== 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 --===============1881949927552452010==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 12 14:59:05 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 12 Aug 2014 14:59: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 1XHDXP-00087f-Hl; Tue, 12 Aug 2014 14:58:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHDXO-00087X-B3 for mirageos-devel@lists.xenproject.org; Tue, 12 Aug 2014 14:58:58 +0000 Received: from [85.158.143.35:29162] by server-2.bemta-4.messagelabs.com id A8/FF-04525-1BB2AE35; Tue, 12 Aug 2014 14:58:57 +0000 X-Env-Sender: hwandori@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1407855535!12594765!1 X-Originating-IP: [209.85.160.178] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_10_20,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23675 invoked from network); 12 Aug 2014 14:58:56 -0000 Received: from mail-yk0-f178.google.com (HELO mail-yk0-f178.google.com) (209.85.160.178) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 12 Aug 2014 14:58:56 -0000 Received: by mail-yk0-f178.google.com with SMTP id 142so7170752ykq.37 for ; Tue, 12 Aug 2014 07:58:55 -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=XCX5wjBp4Zy5VVdhiggkAIq9QzAtFHFrBlKWwnubBWc=; b=XewYHTz7cHtSqX/i6R7Y9TeqSenyHrIIxReKMnXeyfGNTG9JmgrZ/C+5wpiTr8AEEP ZhpzBEAeEDIdBeHR4z2LZ98saoyekXdtVg7e55lBWtkv1fxxFIF/qbXA1dRyX/LSyTjY BXNPuxyf5jLp1PbDu/pBId4fyZHtOaTnVNlJtGXczHY88T92sQ4kQ2fxZsX4PNFsqi4u EE36OoBzX6G9eus5IisjKKcp6iT+HLRSWOJo52MKfxAw/bV5KEqyEcDLxb/1VkW0zyFa 5LjpyGGhfkG50WnILvldcGZtZlrlnkCMmgpOWiKC+Crfdp8cCsb6mxq0YpCZjpAPMmZo fHvA== X-Received: by 10.236.47.201 with SMTP id t49mr24824652yhb.123.1407855535636; Tue, 12 Aug 2014 07:58:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.144.194 with HTTP; Tue, 12 Aug 2014 07:58:35 -0700 (PDT) From: Hwanju Kim Date: Tue, 12 Aug 2014 15:58:35 +0100 X-Google-Sender-Auth: 9xQ1zrXVk6CmCJIMDHbmav9eRFc Message-ID: To: "mirageos-devel@lists.xenproject.org" Subject: [MirageOS-devel] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1881949927552452010==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1881949927552452010== Content-Type: multipart/alternative; boundary=089e01681de418cd1705006fe939 --089e01681de418cd1705006fe939 Content-Type: text/plain; charset=UTF-8 Hi, I've been playing with mirage-skeleton/static_website with unix backend and tap interface. I wonder if there is a right way of assigning a specific mac address to a mirage instance. What I want right now is to run multiple instances with different mac addresses using tap interface. I saw in mirage-net-unix a mac address is assigned randomly, but with the same seed by default makes all mac addresses the same. I just tweaked it by adding, in the static_website's main.ml generated by mirage tool, Random.init before Netif.connect "tap0" to get different an address, but I am sure this is not a proper way. Is there any way to do it? (I know that manual assignment of mac address is doable with xen backend). Cheers, Hwanju --089e01681de418cd1705006fe939 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable --089e01681de418cd1705006fe939-- --===============1881949927552452010== 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 --===============1881949927552452010==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 13 14:40:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 13 Aug 2014 14:40: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 1XHZie-0000Y3-DH; Wed, 13 Aug 2014 14:40:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHZib-0000Xu-9K for mirageos-devel@lists.xenproject.org; Wed, 13 Aug 2014 14:40:01 +0000 Received: from [85.158.137.68:43033] by server-2.bemta-3.messagelabs.com id DB/7B-09149-0C87BE35; Wed, 13 Aug 2014 14:40:00 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1407940798!13448792!1 X-Originating-IP: [209.85.214.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 23547 invoked from network); 13 Aug 2014 14:39:59 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Aug 2014 14:39:59 -0000 Received: by mail-ob0-f181.google.com with SMTP id va2so8146900obc.26 for ; Wed, 13 Aug 2014 07:39:58 -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=4FhmS1JplLNE6Q9B7un9kGZTmBtG6UtmOBnwBm0OeAA=; b=d9+71+WRAj4tVxkme5LTCTOn0P4nDzv49XrmAmCcQTmKonoRp0ag2h3j7ywFpthwVE xIVI2i4wvacF+IwlQvh7rCfhQ7Jc41WwsDHCPOpTigyl7OLREPVrj6HZ5/AXzj2co5cV 5z1nRpX3NfosgHe7FFpX7GcR3hfZpuF7mOOdVFufAYfOLQbae77elDRWvUk3O9e92aD3 ttYPDrEeNgfY+8iuInGpLlxIHD0UAFZ5EQeRsgevk1k8QYO15/cTXMzGUp3okz5Y0654 0rZOLmZdCZLi/O9RzObMtG/F9aPYVdS7KKK+i6M3bjpLNXuv5VJMrrCQ+pi2Pp1g/1vg oLFA== MIME-Version: 1.0 X-Received: by 10.182.137.195 with SMTP id qk3mr4996169obb.5.1407940798380; Wed, 13 Aug 2014 07:39:58 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Wed, 13 Aug 2014 07:39:58 -0700 (PDT) Date: Wed, 13 Aug 2014 15:39:58 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" , Jon Ludlam Subject: [MirageOS-devel] Packaging for Mirage VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm looking at ways of automating downloading and deployment of Mirage services. Back in April, I demoed a simple system using 0install and a little Python script. It worked like this: I put up a GPG-signed XML file describing versions mirage-skeleton/console here: http://test.roscidus.com/mir-console.xml On Linux, you could download and run the Unix build with: $ 0install add mir-console http://test.roscidus.com/mir-console.xml $ mir-console hello [...] On Xen, you could download and run the Xen build with: $ 0install add mir-console --os=Xen http://test.roscidus.com/mir-console.xml $ 0xm run mir-console hello [...] 0xm was just a little script that fixed up the pathname in the package's .cfg before running it, because xm didn't support relative paths (xl does support relative paths, but rather stupidly resolves them relative to the cwd rather than to the .xl file). Using 0install this way gets several useful features for free: - GPG signature checking, automatic downloading of keys, a local trust DB and a key information server to provide hints about which keys to trust. - Automatic updates, testing vs stable versions, roll-back, etc. - Tooling for hosting the repositories, mirroring, etc. The main problem with this simple scheme was that the package gets to supply the .xl file, which isn't what you want (it imples trusting the package with your dom0 for one thing). I think we should have some wrapper for 0install that lets the user specify the disk size and the service to install and creates the LVM partition and the .xl file automatically. e.g. $ 0xl add mail http://test.roscidus.com/mail-server.xml --disk=256M $ 0xl run mail $ 0xl stop mail $ 0xl destroy mail The simplest approach is to have 0xl run "lvcreate" and "xl" directly as subprocesses. However, it could also use some API (e.g. XAPI or libvirt). Do people have a preference here? These might be too heavy for e.g. deployment on a cubieboard in your home. -- 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 Aug 13 14:40:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 13 Aug 2014 14:40: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 1XHZie-0000Y3-DH; Wed, 13 Aug 2014 14:40:04 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHZib-0000Xu-9K for mirageos-devel@lists.xenproject.org; Wed, 13 Aug 2014 14:40:01 +0000 Received: from [85.158.137.68:43033] by server-2.bemta-3.messagelabs.com id DB/7B-09149-0C87BE35; Wed, 13 Aug 2014 14:40:00 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1407940798!13448792!1 X-Originating-IP: [209.85.214.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 23547 invoked from network); 13 Aug 2014 14:39:59 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-4.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Aug 2014 14:39:59 -0000 Received: by mail-ob0-f181.google.com with SMTP id va2so8146900obc.26 for ; Wed, 13 Aug 2014 07:39:58 -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=4FhmS1JplLNE6Q9B7un9kGZTmBtG6UtmOBnwBm0OeAA=; b=d9+71+WRAj4tVxkme5LTCTOn0P4nDzv49XrmAmCcQTmKonoRp0ag2h3j7ywFpthwVE xIVI2i4wvacF+IwlQvh7rCfhQ7Jc41WwsDHCPOpTigyl7OLREPVrj6HZ5/AXzj2co5cV 5z1nRpX3NfosgHe7FFpX7GcR3hfZpuF7mOOdVFufAYfOLQbae77elDRWvUk3O9e92aD3 ttYPDrEeNgfY+8iuInGpLlxIHD0UAFZ5EQeRsgevk1k8QYO15/cTXMzGUp3okz5Y0654 0rZOLmZdCZLi/O9RzObMtG/F9aPYVdS7KKK+i6M3bjpLNXuv5VJMrrCQ+pi2Pp1g/1vg oLFA== MIME-Version: 1.0 X-Received: by 10.182.137.195 with SMTP id qk3mr4996169obb.5.1407940798380; Wed, 13 Aug 2014 07:39:58 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Wed, 13 Aug 2014 07:39:58 -0700 (PDT) Date: Wed, 13 Aug 2014 15:39:58 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" , Jon Ludlam Subject: [MirageOS-devel] Packaging for Mirage VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm looking at ways of automating downloading and deployment of Mirage services. Back in April, I demoed a simple system using 0install and a little Python script. It worked like this: I put up a GPG-signed XML file describing versions mirage-skeleton/console here: http://test.roscidus.com/mir-console.xml On Linux, you could download and run the Unix build with: $ 0install add mir-console http://test.roscidus.com/mir-console.xml $ mir-console hello [...] On Xen, you could download and run the Xen build with: $ 0install add mir-console --os=Xen http://test.roscidus.com/mir-console.xml $ 0xm run mir-console hello [...] 0xm was just a little script that fixed up the pathname in the package's .cfg before running it, because xm didn't support relative paths (xl does support relative paths, but rather stupidly resolves them relative to the cwd rather than to the .xl file). Using 0install this way gets several useful features for free: - GPG signature checking, automatic downloading of keys, a local trust DB and a key information server to provide hints about which keys to trust. - Automatic updates, testing vs stable versions, roll-back, etc. - Tooling for hosting the repositories, mirroring, etc. The main problem with this simple scheme was that the package gets to supply the .xl file, which isn't what you want (it imples trusting the package with your dom0 for one thing). I think we should have some wrapper for 0install that lets the user specify the disk size and the service to install and creates the LVM partition and the .xl file automatically. e.g. $ 0xl add mail http://test.roscidus.com/mail-server.xml --disk=256M $ 0xl run mail $ 0xl stop mail $ 0xl destroy mail The simplest approach is to have 0xl run "lvcreate" and "xl" directly as subprocesses. However, it could also use some API (e.g. XAPI or libvirt). Do people have a preference here? These might be too heavy for e.g. deployment on a cubieboard in your home. -- 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 Aug 13 16:11:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 13 Aug 2014 16:11: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 1XHb8b-0002vB-8o; Wed, 13 Aug 2014 16:10:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHb8Z-0002v6-K8 for mirageos-devel@lists.xenproject.org; Wed, 13 Aug 2014 16:10:55 +0000 Received: from [85.158.143.35:18449] by server-3.bemta-4.messagelabs.com id 44/8E-06192-F0E8BE35; Wed, 13 Aug 2014 16:10:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1407946254!12800809!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6588 invoked from network); 13 Aug 2014 16:10:54 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-21.messagelabs.com with SMTP; 13 Aug 2014 16:10:54 -0000 Received: (qmail 26616 invoked by uid 634); 13 Aug 2014 16:10:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from no-dns-yet.demon.co.uk (HELO [192.168.15.57]) (62.49.66.12) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 13 Aug 2014 17:10:52 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 13 Aug 2014 17:10:50 +0100 Message-Id: References: 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] Packaging for Mirage VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 15:39, Thomas Leonard wrote: > The main problem with this simple scheme was that the package gets to > supply the .xl file, which isn't what you want (it imples trusting the > package with your dom0 for one thing). I think we should have some > wrapper for 0install that lets the user specify the disk size and the > service to install and creates the LVM partition and the .xl file > automatically. e.g. > > $ 0xl add mail http://test.roscidus.com/mail-server.xml --disk=256M > $ 0xl run mail > $ 0xl stop mail > $ 0xl destroy mail > > The simplest approach is to have 0xl run "lvcreate" and "xl" directly > as subprocesses. However, it could also use some API (e.g. XAPI or > libvirt). Do people have a preference here? These might be too heavy > for e.g. deployment on a cubieboard in your home. Could 0xl call out to some script that decides which toolchain to use? The issue is the diversity of choices on the host system: it could be libvirt, xl, or xapi (which apparently works passably well on ARM now), and also the choice of disk backend (which could be lvm, or file-backed VHD/qcow2/VMDK). Then there is the question of running this stuff on EC2 (which Jyotsna's bindings now support) -- should this be in scope for 0xl? This would require a configure phase for 0xl that supplies the EC2 API credentials, but then everything could be automated after that. -anil, lost in a maze of cloudy APIs _______________________________________________ MirageOS-devel 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 Aug 13 16:11:00 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 13 Aug 2014 16:11: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 1XHb8b-0002vB-8o; Wed, 13 Aug 2014 16:10:57 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHb8Z-0002v6-K8 for mirageos-devel@lists.xenproject.org; Wed, 13 Aug 2014 16:10:55 +0000 Received: from [85.158.143.35:18449] by server-3.bemta-4.messagelabs.com id 44/8E-06192-F0E8BE35; Wed, 13 Aug 2014 16:10:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-21.messagelabs.com!1407946254!12800809!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6588 invoked from network); 13 Aug 2014 16:10:54 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-21.messagelabs.com with SMTP; 13 Aug 2014 16:10:54 -0000 Received: (qmail 26616 invoked by uid 634); 13 Aug 2014 16:10:53 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from no-dns-yet.demon.co.uk (HELO [192.168.15.57]) (62.49.66.12) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 13 Aug 2014 17:10:52 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 13 Aug 2014 17:10:50 +0100 Message-Id: References: 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] Packaging for Mirage VMs X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 15:39, Thomas Leonard wrote: > The main problem with this simple scheme was that the package gets to > supply the .xl file, which isn't what you want (it imples trusting the > package with your dom0 for one thing). I think we should have some > wrapper for 0install that lets the user specify the disk size and the > service to install and creates the LVM partition and the .xl file > automatically. e.g. > > $ 0xl add mail http://test.roscidus.com/mail-server.xml --disk=256M > $ 0xl run mail > $ 0xl stop mail > $ 0xl destroy mail > > The simplest approach is to have 0xl run "lvcreate" and "xl" directly > as subprocesses. However, it could also use some API (e.g. XAPI or > libvirt). Do people have a preference here? These might be too heavy > for e.g. deployment on a cubieboard in your home. Could 0xl call out to some script that decides which toolchain to use? The issue is the diversity of choices on the host system: it could be libvirt, xl, or xapi (which apparently works passably well on ARM now), and also the choice of disk backend (which could be lvm, or file-backed VHD/qcow2/VMDK). Then there is the question of running this stuff on EC2 (which Jyotsna's bindings now support) -- should this be in scope for 0xl? This would require a configure phase for 0xl that supplies the EC2 API credentials, but then everything could be automated after that. -anil, lost in a maze of cloudy APIs _______________________________________________ MirageOS-devel 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 Aug 14 08:52:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 08:52: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 1XHqmB-0005Cj-Id; Thu, 14 Aug 2014 08:52:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHqm9-0005Ce-G2 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 08:52:49 +0000 Received: from [85.158.139.211:48722] by server-8.bemta-5.messagelabs.com id 74/D2-22440-0E87CE35; Thu, 14 Aug 2014 08:52:48 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1408006367!3694506!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4819 invoked from network); 14 Aug 2014 08:52:48 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 14 Aug 2014 08:52:48 -0000 Received: (qmail 27373 invoked by uid 634); 14 Aug 2014 08:52:47 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 09:52:47 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 09:52:46 +0100 Message-Id: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> References: To: Hwanju Kim 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] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 15:58, Hwanju Kim wrote: > Hi, > > I've been playing with mirage-skeleton/static_website with unix backend and tap interface. > I wonder if there is a right way of assigning a specific mac address to a mirage instance. > What I want right now is to run multiple instances with different mac addresses using tap interface. > I saw in mirage-net-unix a mac address is assigned randomly, but with the same seed by default makes all mac addresses the same. This would certainly be very useful, and we might as well make the MAC mutable at the same time. I've started the patch here; https://github.com/mirage/mirage-net-unix/pull/8 We also need to modify the type of `devname` to become a tuple of (string, string option) to become the (interface name and mac). This requires a rev of mirage-types, but that can just go into the mirage 2.0-trunk with the other ARM changes. One thing that would be helpful is exposing a set_mac interface in ocaml-tuntap -- if you look at tuntap_stubs.c, the C functions for MacOS X and Linux need to use the relevant SIOCSIFHWADDR ioctl to set it as well. Once that's exposed in the tuntap bindings, we can set the rest. > > I just tweaked it by adding, in the static_website's main.ml generated by mirage tool, Random.init before Netif.connect "tap0" to get different an address, but I am sure this is not a proper way. Is there any way to do it? (I know that manual assignment of mac address is doable with xen backend). Once the right functions are available in the tuntap/mirage-net-* libraries, we can just plumb it through directly into the mirage CLI. -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 Aug 14 08:52:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 08:52: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 1XHqmB-0005Cj-Id; Thu, 14 Aug 2014 08:52:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHqm9-0005Ce-G2 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 08:52:49 +0000 Received: from [85.158.139.211:48722] by server-8.bemta-5.messagelabs.com id 74/D2-22440-0E87CE35; Thu, 14 Aug 2014 08:52:48 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1408006367!3694506!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4819 invoked from network); 14 Aug 2014 08:52:48 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 14 Aug 2014 08:52:48 -0000 Received: (qmail 27373 invoked by uid 634); 14 Aug 2014 08:52:47 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 09:52:47 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 09:52:46 +0100 Message-Id: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> References: To: Hwanju Kim 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] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 15:58, Hwanju Kim wrote: > Hi, > > I've been playing with mirage-skeleton/static_website with unix backend and tap interface. > I wonder if there is a right way of assigning a specific mac address to a mirage instance. > What I want right now is to run multiple instances with different mac addresses using tap interface. > I saw in mirage-net-unix a mac address is assigned randomly, but with the same seed by default makes all mac addresses the same. This would certainly be very useful, and we might as well make the MAC mutable at the same time. I've started the patch here; https://github.com/mirage/mirage-net-unix/pull/8 We also need to modify the type of `devname` to become a tuple of (string, string option) to become the (interface name and mac). This requires a rev of mirage-types, but that can just go into the mirage 2.0-trunk with the other ARM changes. One thing that would be helpful is exposing a set_mac interface in ocaml-tuntap -- if you look at tuntap_stubs.c, the C functions for MacOS X and Linux need to use the relevant SIOCSIFHWADDR ioctl to set it as well. Once that's exposed in the tuntap bindings, we can set the rest. > > I just tweaked it by adding, in the static_website's main.ml generated by mirage tool, Random.init before Netif.connect "tap0" to get different an address, but I am sure this is not a proper way. Is there any way to do it? (I know that manual assignment of mac address is doable with xen backend). Once the right functions are available in the tuntap/mirage-net-* libraries, we can just plumb it through directly into the mirage CLI. -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 Aug 14 13:45:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 13:45: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 1XHvLD-0000GD-IM; Thu, 14 Aug 2014 13:45:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHvLC-0000G8-Ew for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 13:45:18 +0000 Received: from [85.158.139.211:6879] by server-15.bemta-5.messagelabs.com id 18/0D-12002-C6DBCE35; Thu, 14 Aug 2014 13:45:16 +0000 X-Env-Sender: hwandori@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1408023914!8004923!1 X-Originating-IP: [209.85.160.179] 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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16893 invoked from network); 14 Aug 2014 13:45:15 -0000 Received: from mail-yk0-f179.google.com (HELO mail-yk0-f179.google.com) (209.85.160.179) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 13:45:15 -0000 Received: by mail-yk0-f179.google.com with SMTP id 142so958856ykq.38 for ; Thu, 14 Aug 2014 06:45:13 -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:from:date:message-id :subject:to:cc:content-type; bh=ahiWUxjqlZq8J5UlkNXqrvQ7B0BcSU5xRo7A1spqJDw=; b=bSOvbF6wuaEA6NkYF/tNZgHPwG9ko/IvNMOs5AAZinLkvO41RzE+QqbqD76XSavDP+ Q+AESIFKD4+TdvgJ25sITqcHwpoFeyrrdv4Hwoe9DdfF4oEk/zC0Bqhd/4/jAAEDyHIM aMdroMz6q7JQue34ja39BfUX1P5ig/fI01btGIOKuTzo42kGpfuAnCcawuqAfAZl9C4K wj8XEN0LYY8oFItdgxpRd98l6jbD3j4hJ+rZ4vXI+IILpjJxZ9bJDiAwr+QX/ZucF2YK j6168IBzOlRvpoiANdNaPiXXQXfQzbGB15Bnf3siCdNECCj9D49jlQteml1Nd5BeRShr HBNw== X-Received: by 10.236.47.201 with SMTP id t49mr16795379yhb.123.1408023913451; Thu, 14 Aug 2014 06:45:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.144.194 with HTTP; Thu, 14 Aug 2014 06:44:53 -0700 (PDT) In-Reply-To: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> References: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> From: Hwanju Kim Date: Thu, 14 Aug 2014 14:44:53 +0100 X-Google-Sender-Auth: tj5yXgakxdsqPNzQiy9qgCRbmKY Message-ID: To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8528218205117305465==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8528218205117305465== Content-Type: multipart/alternative; boundary=089e01681de43259260500971d38 --089e01681de43259260500971d38 Content-Type: text/plain; charset=UTF-8 2014-08-14 9:52 GMT+01:00 Anil Madhavapeddy : > On 12 Aug 2014, at 15:58, Hwanju Kim wrote: > > > Hi, > > > > I've been playing with mirage-skeleton/static_website with unix backend > and tap interface. > > I wonder if there is a right way of assigning a specific mac address to > a mirage instance. > > What I want right now is to run multiple instances with different mac > addresses using tap interface. > > I saw in mirage-net-unix a mac address is assigned randomly, but with > the same seed by default makes all mac addresses the same. > > This would certainly be very useful, and we might as well make the MAC > mutable at the same time. > > I've started the patch here; > https://github.com/mirage/mirage-net-unix/pull/8 > > We also need to modify the type of `devname` to become a tuple of (string, > string option) to become the (interface name and mac). This requires a rev > of mirage-types, but that can just go into the mirage 2.0-trunk with the > other ARM changes. > Cool! I will keep my eyes on it. > > One thing that would be helpful is exposing a set_mac interface in > ocaml-tuntap -- if you look at tuntap_stubs.c, the C functions for MacOS X > and Linux need to use the relevant SIOCSIFHWADDR ioctl to set it as well. > Once that's exposed in the tuntap bindings, we can set the rest. > The set interface of Netif is straightforward. Regarding tuntap, however, I wonder what situation makes a tap device also need a specific mac address. I thought they act as a link to each mirage guest and the Netif of a guest is the one that reacts ARP requests. (in addition, multiple taps have different mac addresses already). Cheers, Hwanju > > > > > I just tweaked it by adding, in the static_website's main.ml generated > by mirage tool, Random.init before Netif.connect "tap0" > to get different an address, but I am sure this is not a proper way. Is > there any way to do it? (I know that manual assignment of mac address is > doable with xen backend). > > Once the right functions are available in the tuntap/mirage-net-* > libraries, we can just plumb it through directly into the mirage CLI. > > -anil --089e01681de43259260500971d38 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



2014-08-14 9:52 GMT+01:00 Anil Madhavapeddy <<= a href=3D"mailto:anil@recoil.org" target=3D"_blank">anil@recoil.org>= :
On 12 Aug 2014, at 15:58, Hw= anju Kim <Hwanju.Kim@cl.cam.a= c.uk> wrote:

> Hi,
>
> I've been playing with mirage-skeleton/static_website with unix ba= ckend and tap interface.
> I wonder if there is a right way of assigning a specific mac address t= o a mirage instance.
> What I want right now is to run multiple instances with different mac = addresses using tap interface.
> I saw in mirage-net-unix a mac address is assigned randomly, but with = the same seed by default makes all mac addresses the same.

This would certainly be very useful, and we might as well make the MA= C mutable at the same time.

I've started the patch here; https://github.com/mirage/mirage-net-u= nix/pull/8

We also need to modify the type of `devname` to become a tuple of (string, = string option) to become the (interface name and mac).=C2=A0 This requires = a rev of mirage-types, but that can just go into the mirage 2.0-trunk with = the other ARM changes.

Cool! I will keep my eyes on it.
=C2=A0

One thing that would be helpful is exposing a set_mac interface in ocaml-tu= ntap -- if you look at tuntap_stubs.c, the C functions for MacOS X and Linu= x need to use the relevant SIOCSIFHWADDR ioctl to set it as well.=C2=A0 Onc= e that's exposed in the tuntap bindings, we can set the rest.

The set interface of Netif is straightforw= ard. Regarding tuntap, however, I wonder what situation makes a tap device = also need a specific mac address. I thought they act as a link to each mira= ge guest and the Netif of a guest is the one that reacts ARP requests. (in = addition, multiple taps have different mac addresses already).

Cheers,
Hwanju
=C2=A0

>
> I just tweaked it by adding, in the static_website's main.ml generated by mirage tool, Rando= m.init <a different seed> before Netif.connect "tap0" to ge= t different an address, but I am sure this is not a proper way. Is there an= y way to do it? (I know that manual assignment of mac address is doable wit= h xen backend).

Once the right functions are available in the tuntap/mirage-net-* lib= raries, we can just plumb it through directly into the mirage CLI.

-anil

--089e01681de43259260500971d38-- --===============8528218205117305465== 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 --===============8528218205117305465==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 13:45:24 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 13:45: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 1XHvLD-0000GD-IM; Thu, 14 Aug 2014 13:45:19 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHvLC-0000G8-Ew for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 13:45:18 +0000 Received: from [85.158.139.211:6879] by server-15.bemta-5.messagelabs.com id 18/0D-12002-C6DBCE35; Thu, 14 Aug 2014 13:45:16 +0000 X-Env-Sender: hwandori@gmail.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1408023914!8004923!1 X-Originating-IP: [209.85.160.179] 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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16893 invoked from network); 14 Aug 2014 13:45:15 -0000 Received: from mail-yk0-f179.google.com (HELO mail-yk0-f179.google.com) (209.85.160.179) by server-15.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 13:45:15 -0000 Received: by mail-yk0-f179.google.com with SMTP id 142so958856ykq.38 for ; Thu, 14 Aug 2014 06:45:13 -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:from:date:message-id :subject:to:cc:content-type; bh=ahiWUxjqlZq8J5UlkNXqrvQ7B0BcSU5xRo7A1spqJDw=; b=bSOvbF6wuaEA6NkYF/tNZgHPwG9ko/IvNMOs5AAZinLkvO41RzE+QqbqD76XSavDP+ Q+AESIFKD4+TdvgJ25sITqcHwpoFeyrrdv4Hwoe9DdfF4oEk/zC0Bqhd/4/jAAEDyHIM aMdroMz6q7JQue34ja39BfUX1P5ig/fI01btGIOKuTzo42kGpfuAnCcawuqAfAZl9C4K wj8XEN0LYY8oFItdgxpRd98l6jbD3j4hJ+rZ4vXI+IILpjJxZ9bJDiAwr+QX/ZucF2YK j6168IBzOlRvpoiANdNaPiXXQXfQzbGB15Bnf3siCdNECCj9D49jlQteml1Nd5BeRShr HBNw== X-Received: by 10.236.47.201 with SMTP id t49mr16795379yhb.123.1408023913451; Thu, 14 Aug 2014 06:45:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.144.194 with HTTP; Thu, 14 Aug 2014 06:44:53 -0700 (PDT) In-Reply-To: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> References: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> From: Hwanju Kim Date: Thu, 14 Aug 2014 14:44:53 +0100 X-Google-Sender-Auth: tj5yXgakxdsqPNzQiy9qgCRbmKY Message-ID: To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8528218205117305465==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8528218205117305465== Content-Type: multipart/alternative; boundary=089e01681de43259260500971d38 --089e01681de43259260500971d38 Content-Type: text/plain; charset=UTF-8 2014-08-14 9:52 GMT+01:00 Anil Madhavapeddy : > On 12 Aug 2014, at 15:58, Hwanju Kim wrote: > > > Hi, > > > > I've been playing with mirage-skeleton/static_website with unix backend > and tap interface. > > I wonder if there is a right way of assigning a specific mac address to > a mirage instance. > > What I want right now is to run multiple instances with different mac > addresses using tap interface. > > I saw in mirage-net-unix a mac address is assigned randomly, but with > the same seed by default makes all mac addresses the same. > > This would certainly be very useful, and we might as well make the MAC > mutable at the same time. > > I've started the patch here; > https://github.com/mirage/mirage-net-unix/pull/8 > > We also need to modify the type of `devname` to become a tuple of (string, > string option) to become the (interface name and mac). This requires a rev > of mirage-types, but that can just go into the mirage 2.0-trunk with the > other ARM changes. > Cool! I will keep my eyes on it. > > One thing that would be helpful is exposing a set_mac interface in > ocaml-tuntap -- if you look at tuntap_stubs.c, the C functions for MacOS X > and Linux need to use the relevant SIOCSIFHWADDR ioctl to set it as well. > Once that's exposed in the tuntap bindings, we can set the rest. > The set interface of Netif is straightforward. Regarding tuntap, however, I wonder what situation makes a tap device also need a specific mac address. I thought they act as a link to each mirage guest and the Netif of a guest is the one that reacts ARP requests. (in addition, multiple taps have different mac addresses already). Cheers, Hwanju > > > > > I just tweaked it by adding, in the static_website's main.ml generated > by mirage tool, Random.init before Netif.connect "tap0" > to get different an address, but I am sure this is not a proper way. Is > there any way to do it? (I know that manual assignment of mac address is > doable with xen backend). > > Once the right functions are available in the tuntap/mirage-net-* > libraries, we can just plumb it through directly into the mirage CLI. > > -anil --089e01681de43259260500971d38 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



2014-08-14 9:52 GMT+01:00 Anil Madhavapeddy <<= a href=3D"mailto:anil@recoil.org" target=3D"_blank">anil@recoil.org>= :
On 12 Aug 2014, at 15:58, Hw= anju Kim <Hwanju.Kim@cl.cam.a= c.uk> wrote:

> Hi,
>
> I've been playing with mirage-skeleton/static_website with unix ba= ckend and tap interface.
> I wonder if there is a right way of assigning a specific mac address t= o a mirage instance.
> What I want right now is to run multiple instances with different mac = addresses using tap interface.
> I saw in mirage-net-unix a mac address is assigned randomly, but with = the same seed by default makes all mac addresses the same.

This would certainly be very useful, and we might as well make the MA= C mutable at the same time.

I've started the patch here; https://github.com/mirage/mirage-net-u= nix/pull/8

We also need to modify the type of `devname` to become a tuple of (string, = string option) to become the (interface name and mac).=C2=A0 This requires = a rev of mirage-types, but that can just go into the mirage 2.0-trunk with = the other ARM changes.

Cool! I will keep my eyes on it.
=C2=A0

One thing that would be helpful is exposing a set_mac interface in ocaml-tu= ntap -- if you look at tuntap_stubs.c, the C functions for MacOS X and Linu= x need to use the relevant SIOCSIFHWADDR ioctl to set it as well.=C2=A0 Onc= e that's exposed in the tuntap bindings, we can set the rest.

The set interface of Netif is straightforw= ard. Regarding tuntap, however, I wonder what situation makes a tap device = also need a specific mac address. I thought they act as a link to each mira= ge guest and the Netif of a guest is the one that reacts ARP requests. (in = addition, multiple taps have different mac addresses already).

Cheers,
Hwanju
=C2=A0

>
> I just tweaked it by adding, in the static_website's main.ml generated by mirage tool, Rando= m.init <a different seed> before Netif.connect "tap0" to ge= t different an address, but I am sure this is not a proper way. Is there an= y way to do it? (I know that manual assignment of mac address is doable wit= h xen backend).

Once the right functions are available in the tuntap/mirage-net-* lib= raries, we can just plumb it through directly into the mirage CLI.

-anil

--089e01681de43259260500971d38-- --===============8528218205117305465== 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 --===============8528218205117305465==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 13:48:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 13:48: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 1XHvNy-0000IO-Ur; Thu, 14 Aug 2014 13:48:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHvNx-0000IJ-A0 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 13:48:09 +0000 Received: from [85.158.139.211:54826] by server-13.bemta-5.messagelabs.com id 6D/0D-20082-81EBCE35; Thu, 14 Aug 2014 13:48:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1408024087!6071661!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10489 invoked from network); 14 Aug 2014 13:48:08 -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; 14 Aug 2014 13:48:08 -0000 Received: (qmail 21482 invoked by uid 634); 14 Aug 2014 13:48:07 -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.110]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 14:48:07 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 14:48:05 +0100 Message-Id: References: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> To: Hwanju Kim 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] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7703296289045157284==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7703296289045157284== Content-Type: multipart/alternative; boundary="Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7" --Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 14 Aug 2014, at 14:44, Hwanju Kim wrote: > The set interface of Netif is straightforward. Regarding tuntap, = however, I wonder what situation makes a tap device also need a specific = mac address. I thought they act as a link to each mirage guest and the = Netif of a guest is the one that reacts ARP requests. (in addition, = multiple taps have different mac addresses already). Manual control is useful for setting up development networks (as Massoud = is doing for example). But most importantly, it gives us a homogenous = interface between Xen and Unix environments. It would also help with = deterministic test cases (if things like Mac, IP and ARP entries are all = settable from the mirage frontend). -anil --Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 14 = Aug 2014, at 14:44, Hwanju Kim <Hwanju.Kim@cl.cam.ac.uk> = wrote:

The = set interface of Netif is straightforward. Regarding tuntap, however, I = wonder what situation makes a tap device also need a specific mac = address. I thought they act as a link to each mirage guest and the Netif = of a guest is the one that reacts ARP requests. (in addition, multiple = taps have different mac addresses = already).

Manual control is useful for = setting up development networks (as Massoud is doing for example). =  But most importantly, it gives us a homogenous interface between = Xen and Unix environments.  It would also help with deterministic = test cases (if things like Mac, IP and ARP entries are all settable from = the mirage = frontend).

-anil

= --Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7-- --===============7703296289045157284== 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 --===============7703296289045157284==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 13:48:10 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 13:48: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 1XHvNy-0000IO-Ur; Thu, 14 Aug 2014 13:48:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHvNx-0000IJ-A0 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 13:48:09 +0000 Received: from [85.158.139.211:54826] by server-13.bemta-5.messagelabs.com id 6D/0D-20082-81EBCE35; Thu, 14 Aug 2014 13:48:08 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1408024087!6071661!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10489 invoked from network); 14 Aug 2014 13:48:08 -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; 14 Aug 2014 13:48:08 -0000 Received: (qmail 21482 invoked by uid 634); 14 Aug 2014 13:48:07 -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.110]) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 14:48:07 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 14:48:05 +0100 Message-Id: References: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> To: Hwanju Kim 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] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7703296289045157284==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7703296289045157284== Content-Type: multipart/alternative; boundary="Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7" --Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 14 Aug 2014, at 14:44, Hwanju Kim wrote: > The set interface of Netif is straightforward. Regarding tuntap, = however, I wonder what situation makes a tap device also need a specific = mac address. I thought they act as a link to each mirage guest and the = Netif of a guest is the one that reacts ARP requests. (in addition, = multiple taps have different mac addresses already). Manual control is useful for setting up development networks (as Massoud = is doing for example). But most importantly, it gives us a homogenous = interface between Xen and Unix environments. It would also help with = deterministic test cases (if things like Mac, IP and ARP entries are all = settable from the mirage frontend). -anil --Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 14 = Aug 2014, at 14:44, Hwanju Kim <Hwanju.Kim@cl.cam.ac.uk> = wrote:

The = set interface of Netif is straightforward. Regarding tuntap, however, I = wonder what situation makes a tap device also need a specific mac = address. I thought they act as a link to each mirage guest and the Netif = of a guest is the one that reacts ARP requests. (in addition, multiple = taps have different mac addresses = already).

Manual control is useful for = setting up development networks (as Massoud is doing for example). =  But most importantly, it gives us a homogenous interface between = Xen and Unix environments.  It would also help with deterministic = test cases (if things like Mac, IP and ARP entries are all settable from = the mirage = frontend).

-anil

= --Apple-Mail=_16A06181-42C1-4792-998E-898544DAFCC7-- --===============7703296289045157284== 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 --===============7703296289045157284==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 13:50:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 13:50: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 1XHvPy-0000ML-6Y; Thu, 14 Aug 2014 13:50:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHvPw-0000MG-E4 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 13:50:12 +0000 Received: from [85.158.137.68:23287] by server-16.bemta-3.messagelabs.com id 39/D3-08587-19EBCE35; Thu, 14 Aug 2014 13:50:09 +0000 X-Env-Sender: hwandori@gmail.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1408024207!13716345!1 X-Originating-IP: [209.85.213.42] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17113 invoked from network); 14 Aug 2014 13:50:08 -0000 Received: from mail-yh0-f42.google.com (HELO mail-yh0-f42.google.com) (209.85.213.42) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 13:50:08 -0000 Received: by mail-yh0-f42.google.com with SMTP id a41so1031605yho.29 for ; Thu, 14 Aug 2014 06:50:07 -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:from:date:message-id :subject:to:cc:content-type; bh=SDP5g6pt7o5/F3pYignOArov6AxBMN3dtOgrRrCH+E4=; b=nikLQOYMhfOI3Cc7rF27l9Frlq8BBbzsLhhVMS70Qkle+x394r76iULffyOx5q+ZAh UuJHRwWKZ2Zs8IsjfxmobuYNNrvtfZ9g83GcxuMRv6WF4KlxMd2ojeIUwDOuDAsXsCOB UeYyglCXSPhb4LlE0fS6WbcHCEXwCqIHV8PUlYZHPco18/ZXvOaLZrUEQLjilZKJ5Qbs n/i8onaMyahfrEZIWWGHdkbbOM4LwAAx+30nS8oSZkVgIffwqgmD1uh2sGq9lXE8vtK8 4MoJQHZXpawoqYw9ByC4LXk9ZrF3n4kUCLuja+3wIHURsA0SsVNKquI6P7ZNiF1ZQBdp vorg== X-Received: by 10.236.112.167 with SMTP id y27mr16694303yhg.60.1408024207400; Thu, 14 Aug 2014 06:50:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.144.194 with HTTP; Thu, 14 Aug 2014 06:49:46 -0700 (PDT) In-Reply-To: References: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> From: Hwanju Kim Date: Thu, 14 Aug 2014 14:49:46 +0100 X-Google-Sender-Auth: QtlVmDCiJ4cMG9kaNbap-xqcNh8 Message-ID: To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5923350463000043691==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5923350463000043691== Content-Type: multipart/alternative; boundary=20cf3011df67b7a6250500972e16 --20cf3011df67b7a6250500972e16 Content-Type: text/plain; charset=UTF-8 2014-08-14 14:48 GMT+01:00 Anil Madhavapeddy : > On 14 Aug 2014, at 14:44, Hwanju Kim wrote: > > The set interface of Netif is straightforward. Regarding tuntap, however, > I wonder what situation makes a tap device also need a specific mac > address. I thought they act as a link to each mirage guest and the Netif of > a guest is the one that reacts ARP requests. (in addition, multiple taps > have different mac addresses already). > > > Manual control is useful for setting up development networks (as Massoud > is doing for example). But most importantly, it gives us a homogenous > interface between Xen and Unix environments. It would also help with > deterministic test cases (if things like Mac, IP and ARP entries are all > settable from the mirage frontend). > Got it. That makes sense. Thank you! Cheers, Hwanju > > -anil > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --20cf3011df67b7a6250500972e16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



2014-08-14 14:48 GMT+01:00 Anil Madhavapeddy <= anil@recoil.org>= ;:
On 14 Aug 2014, at 14:44, Hwanju Kim <Hwanju.Kim@cl.cam.ac.uk> wrote:

The set interface of Netif is straightforward. Regarding tuntap, however, I= wonder what situation makes a tap device also need a specific mac address.= I thought they act as a link to each mirage guest and the Netif of a guest= is the one that reacts ARP requests. (in addition, multiple taps have diff= erent mac addresses already).

Manual control is useful for setting up d= evelopment networks (as Massoud is doing for example). =C2=A0But most impor= tantly, it gives us a homogenous interface between Xen and Unix environment= s. =C2=A0It would also help with deterministic test cases (if things like M= ac, IP and ARP entries are all settable from the mirage frontend).

Got it. That makes sense. Thank you!= =C2=A0

Cheers,
Hwanju

-anil


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


--20cf3011df67b7a6250500972e16-- --===============5923350463000043691== 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 --===============5923350463000043691==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 13:50:14 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 13:50: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 1XHvPy-0000ML-6Y; Thu, 14 Aug 2014 13:50:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHvPw-0000MG-E4 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 13:50:12 +0000 Received: from [85.158.137.68:23287] by server-16.bemta-3.messagelabs.com id 39/D3-08587-19EBCE35; Thu, 14 Aug 2014 13:50:09 +0000 X-Env-Sender: hwandori@gmail.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1408024207!13716345!1 X-Originating-IP: [209.85.213.42] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17113 invoked from network); 14 Aug 2014 13:50:08 -0000 Received: from mail-yh0-f42.google.com (HELO mail-yh0-f42.google.com) (209.85.213.42) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 13:50:08 -0000 Received: by mail-yh0-f42.google.com with SMTP id a41so1031605yho.29 for ; Thu, 14 Aug 2014 06:50:07 -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:from:date:message-id :subject:to:cc:content-type; bh=SDP5g6pt7o5/F3pYignOArov6AxBMN3dtOgrRrCH+E4=; b=nikLQOYMhfOI3Cc7rF27l9Frlq8BBbzsLhhVMS70Qkle+x394r76iULffyOx5q+ZAh UuJHRwWKZ2Zs8IsjfxmobuYNNrvtfZ9g83GcxuMRv6WF4KlxMd2ojeIUwDOuDAsXsCOB UeYyglCXSPhb4LlE0fS6WbcHCEXwCqIHV8PUlYZHPco18/ZXvOaLZrUEQLjilZKJ5Qbs n/i8onaMyahfrEZIWWGHdkbbOM4LwAAx+30nS8oSZkVgIffwqgmD1uh2sGq9lXE8vtK8 4MoJQHZXpawoqYw9ByC4LXk9ZrF3n4kUCLuja+3wIHURsA0SsVNKquI6P7ZNiF1ZQBdp vorg== X-Received: by 10.236.112.167 with SMTP id y27mr16694303yhg.60.1408024207400; Thu, 14 Aug 2014 06:50:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.144.194 with HTTP; Thu, 14 Aug 2014 06:49:46 -0700 (PDT) In-Reply-To: References: <443CCA2D-D640-4963-9529-5B2FCC318F08@recoil.org> From: Hwanju Kim Date: Thu, 14 Aug 2014 14:49:46 +0100 X-Google-Sender-Auth: QtlVmDCiJ4cMG9kaNbap-xqcNh8 Message-ID: To: Anil Madhavapeddy Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Manual assignment of mac address for tap interface X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5923350463000043691==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5923350463000043691== Content-Type: multipart/alternative; boundary=20cf3011df67b7a6250500972e16 --20cf3011df67b7a6250500972e16 Content-Type: text/plain; charset=UTF-8 2014-08-14 14:48 GMT+01:00 Anil Madhavapeddy : > On 14 Aug 2014, at 14:44, Hwanju Kim wrote: > > The set interface of Netif is straightforward. Regarding tuntap, however, > I wonder what situation makes a tap device also need a specific mac > address. I thought they act as a link to each mirage guest and the Netif of > a guest is the one that reacts ARP requests. (in addition, multiple taps > have different mac addresses already). > > > Manual control is useful for setting up development networks (as Massoud > is doing for example). But most importantly, it gives us a homogenous > interface between Xen and Unix environments. It would also help with > deterministic test cases (if things like Mac, IP and ARP entries are all > settable from the mirage frontend). > Got it. That makes sense. Thank you! Cheers, Hwanju > > -anil > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > --20cf3011df67b7a6250500972e16 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



2014-08-14 14:48 GMT+01:00 Anil Madhavapeddy <= anil@recoil.org>= ;:
On 14 Aug 2014, at 14:44, Hwanju Kim <Hwanju.Kim@cl.cam.ac.uk> wrote:

The set interface of Netif is straightforward. Regarding tuntap, however, I= wonder what situation makes a tap device also need a specific mac address.= I thought they act as a link to each mirage guest and the Netif of a guest= is the one that reacts ARP requests. (in addition, multiple taps have diff= erent mac addresses already).

Manual control is useful for setting up d= evelopment networks (as Massoud is doing for example). =C2=A0But most impor= tantly, it gives us a homogenous interface between Xen and Unix environment= s. =C2=A0It would also help with deterministic test cases (if things like M= ac, IP and ARP entries are all settable from the mirage frontend).

Got it. That makes sense. Thank you!= =C2=A0

Cheers,
Hwanju

-anil


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


--20cf3011df67b7a6250500972e16-- --===============5923350463000043691== 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 --===============5923350463000043691==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 15:12:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 15:12: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 1XHwh6-000221-Ud; Thu, 14 Aug 2014 15:12:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHwh6-00021w-3X for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 15:12:00 +0000 Received: from [85.158.139.211:35701] by server-17.bemta-5.messagelabs.com id 26/54-08943-FB1DCE35; Thu, 14 Aug 2014 15:11:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1408029118!3794874!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16358 invoked from network); 14 Aug 2014 15:11:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 14 Aug 2014 15:11:58 -0000 Received: (qmail 15808 invoked by uid 634); 14 Aug 2014 15:11:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 16:11:56 +0100 From: Anil Madhavapeddy Message-Id: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> Date: Thu, 14 Aug 2014 16:11:55 +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) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [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 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. The old VM uses CentOS 6, which is a little old to get all the cross-tools needed. -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 Aug 14 15:12:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 15:12: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 1XHwh6-000221-Ud; Thu, 14 Aug 2014 15:12:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHwh6-00021w-3X for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 15:12:00 +0000 Received: from [85.158.139.211:35701] by server-17.bemta-5.messagelabs.com id 26/54-08943-FB1DCE35; Thu, 14 Aug 2014 15:11:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1408029118!3794874!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16358 invoked from network); 14 Aug 2014 15:11:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 14 Aug 2014 15:11:58 -0000 Received: (qmail 15808 invoked by uid 634); 14 Aug 2014 15:11:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 16:11:56 +0100 From: Anil Madhavapeddy Message-Id: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> Date: Thu, 14 Aug 2014 16:11:55 +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) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [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 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. The old VM uses CentOS 6, which is a little old to get all the cross-tools needed. -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 Aug 14 15:25:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 15:25: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 1XHwtq-00027D-0p; Thu, 14 Aug 2014 15:25:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHwtp-000278-AT for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 15:25:09 +0000 Received: from [85.158.139.211:16430] by server-2.bemta-5.messagelabs.com id FE/CC-31832-4D4DCE35; Thu, 14 Aug 2014 15:25:08 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1408029906!8501250!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11309 invoked from network); 14 Aug 2014 15:25:08 -0000 Received: from mail-oi0-f53.google.com (HELO mail-oi0-f53.google.com) (209.85.218.53) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 15:25:08 -0000 Received: by mail-oi0-f53.google.com with SMTP id e131so831076oig.40 for ; Thu, 14 Aug 2014 08:25:06 -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=B6Zi6HaMvqcrvCX6RWLapHEea8Zhnq5FE7KvzG0+vlw=; b=BjhwcCnJYt+OX/ix+L20ZulARhRvRA4yCVHbu3/+AIyNEeU70caS+6vDNluuiYCe7M iixNvG+8TN/9GlfqiLQvEpBAa8ScaRAaU594vBRRf2qZJRwY7QXpoTZYlr4p800dzLas 86cWA75nHYmp2tyQglOvcYPNDyufRcmTJNGdOJiNqKxlESwv4oI5NnMClRp9rOhhSZNt V3rElOpsE38OmQDLk6ImMWmHsKvetqYGsjo9JM+/wVH4CFedU55W3FWDLiBkmJmVvIA5 brij8SGdbX3GzHhOiS0/tNQSAjhvsIKYvokcl/NZbQuT0vL9AVHaoQ3WcKF2GZVWcZ6U VySw== MIME-Version: 1.0 X-Received: by 10.182.104.104 with SMTP id gd8mr13481359obb.17.1408029906307; Thu, 14 Aug 2014 08:25:06 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Thu, 14 Aug 2014 08:25:06 -0700 (PDT) In-Reply-To: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> References: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> Date: Thu, 14 Aug 2014 16:25:06 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy 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 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)! -- 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 Thu Aug 14 15:25:11 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 15:25: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 1XHwtq-00027D-0p; Thu, 14 Aug 2014 15:25:10 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHwtp-000278-AT for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 15:25:09 +0000 Received: from [85.158.139.211:16430] by server-2.bemta-5.messagelabs.com id FE/CC-31832-4D4DCE35; Thu, 14 Aug 2014 15:25:08 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1408029906!8501250!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11309 invoked from network); 14 Aug 2014 15:25:08 -0000 Received: from mail-oi0-f53.google.com (HELO mail-oi0-f53.google.com) (209.85.218.53) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 15:25:08 -0000 Received: by mail-oi0-f53.google.com with SMTP id e131so831076oig.40 for ; Thu, 14 Aug 2014 08:25:06 -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=B6Zi6HaMvqcrvCX6RWLapHEea8Zhnq5FE7KvzG0+vlw=; b=BjhwcCnJYt+OX/ix+L20ZulARhRvRA4yCVHbu3/+AIyNEeU70caS+6vDNluuiYCe7M iixNvG+8TN/9GlfqiLQvEpBAa8ScaRAaU594vBRRf2qZJRwY7QXpoTZYlr4p800dzLas 86cWA75nHYmp2tyQglOvcYPNDyufRcmTJNGdOJiNqKxlESwv4oI5NnMClRp9rOhhSZNt V3rElOpsE38OmQDLk6ImMWmHsKvetqYGsjo9JM+/wVH4CFedU55W3FWDLiBkmJmVvIA5 brij8SGdbX3GzHhOiS0/tNQSAjhvsIKYvokcl/NZbQuT0vL9AVHaoQ3WcKF2GZVWcZ6U VySw== MIME-Version: 1.0 X-Received: by 10.182.104.104 with SMTP id gd8mr13481359obb.17.1408029906307; Thu, 14 Aug 2014 08:25:06 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Thu, 14 Aug 2014 08:25:06 -0700 (PDT) In-Reply-To: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> References: <1F1C3527-1762-4E9B-91B2-5006F102DC1A@recoil.org> Date: Thu, 14 Aug 2014 16:25:06 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy 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 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)! -- 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 Thu Aug 14 15:58:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 15:58: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 1XHxQA-0002bY-FP; Thu, 14 Aug 2014 15:58:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxQ8-0002bT-F8 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 15:58:32 +0000 Received: from [85.158.139.211:5248] by server-2.bemta-5.messagelabs.com id A9/06-31832-7ACDCE35; Thu, 14 Aug 2014 15:58:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1408031911!11388023!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14495 invoked from network); 14 Aug 2014 15:58:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-206.messagelabs.com with SMTP; 14 Aug 2014 15:58:31 -0000 Received: (qmail 31289 invoked by uid 634); 14 Aug 2014 15:58:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 16:58:30 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 16:58:28 +0100 Message-Id: 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: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! -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 Aug 14 15:58:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 15:58: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 1XHxQA-0002bY-FP; Thu, 14 Aug 2014 15:58:34 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxQ8-0002bT-F8 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 15:58:32 +0000 Received: from [85.158.139.211:5248] by server-2.bemta-5.messagelabs.com id A9/06-31832-7ACDCE35; Thu, 14 Aug 2014 15:58:31 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1408031911!11388023!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14495 invoked from network); 14 Aug 2014 15:58:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-206.messagelabs.com with SMTP; 14 Aug 2014 15:58:31 -0000 Received: (qmail 31289 invoked by uid 634); 14 Aug 2014 15:58:30 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 16:58:30 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 16:58:28 +0100 Message-Id: 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: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! -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 Aug 14 16:04:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:04: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 1XHxVy-00038q-C7; Thu, 14 Aug 2014 16:04:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxVx-00038h-3u for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:04:33 +0000 Received: from [85.158.137.68:59005] by server-12.bemta-3.messagelabs.com id 51/9A-02460-01EDCE35; Thu, 14 Aug 2014 16:04:32 +0000 X-Env-Sender: philtomson@gmail.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1408032270!13746956!1 X-Originating-IP: [209.85.213.175] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_20_30,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29837 invoked from network); 14 Aug 2014 16:04:31 -0000 Received: from mail-ig0-f175.google.com (HELO mail-ig0-f175.google.com) (209.85.213.175) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 16:04:31 -0000 Received: by mail-ig0-f175.google.com with SMTP id uq10so14038461igb.8 for ; Thu, 14 Aug 2014 09:04:30 -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=9JpDi6VPmhChgfyOd8ImxaqLgBvbpjNaGtwy3g3p9Yg=; b=DrTGabfNFE5IUU1lDUe1aTbIxmDkhLhaRYt61kr7GjF87JLbDmacb2gSJZVeydtiNk +VOBgjeCBEapPBK/LR9STjir051aA3BoKAMa6gTDYWlX+7HBkdicQNh621XE+E8lM8us /scL9HJTEeL327JnopKuQDf95ykw8r9JsuqACR8hiRxUo4UtudKcLil6cetxABAnSx5f C2+w9+dTwrJ7/lzlRcO45/HzSlBg4lkpKk+G/WE9/sf4RuJ736IMLm2bIw+Rzf99lO6P Shfwd3zh5kX5AZiqaDJl3zW2vSdLKDNJ7KPPdhq2nkVKwg947058mAWGIMAww18G1PdD KK4g== MIME-Version: 1.0 X-Received: by 10.50.122.99 with SMTP id lr3mr59103629igb.10.1408032270277; Thu, 14 Aug 2014 09:04:30 -0700 (PDT) Received: by 10.43.111.136 with HTTP; Thu, 14 Aug 2014 09:04:30 -0700 (PDT) Date: Thu, 14 Aug 2014 09:04:30 -0700 Message-ID: From: Phil Tomson To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Is Mirage 2.0 released? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1900891951890646074==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1900891951890646074== Content-Type: multipart/alternative; boundary=089e0153835a4d87fd0500990ff5 --089e0153835a4d87fd0500990ff5 Content-Type: text/plain; charset=UTF-8 I only see 1.2.0 in opam packages. Also looking at the github page 1.2.0 is the current release. Phil --089e0153835a4d87fd0500990ff5 Content-Type: text/html; charset=UTF-8
I only see 1.2.0 in opam packages. Also looking at the github page 1.2.0 is the current release.

Phil
--089e0153835a4d87fd0500990ff5-- --===============1900891951890646074== 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 --===============1900891951890646074==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 16:04:35 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:04: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 1XHxVy-00038q-C7; Thu, 14 Aug 2014 16:04:34 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxVx-00038h-3u for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:04:33 +0000 Received: from [85.158.137.68:59005] by server-12.bemta-3.messagelabs.com id 51/9A-02460-01EDCE35; Thu, 14 Aug 2014 16:04:32 +0000 X-Env-Sender: philtomson@gmail.com X-Msg-Ref: server-16.tower-31.messagelabs.com!1408032270!13746956!1 X-Originating-IP: [209.85.213.175] X-SpamReason: No, hits=2.8 required=7.0 tests=HTML_20_30,HTML_MESSAGE, HTML_SHORT_LENGTH,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29837 invoked from network); 14 Aug 2014 16:04:31 -0000 Received: from mail-ig0-f175.google.com (HELO mail-ig0-f175.google.com) (209.85.213.175) by server-16.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 14 Aug 2014 16:04:31 -0000 Received: by mail-ig0-f175.google.com with SMTP id uq10so14038461igb.8 for ; Thu, 14 Aug 2014 09:04:30 -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=9JpDi6VPmhChgfyOd8ImxaqLgBvbpjNaGtwy3g3p9Yg=; b=DrTGabfNFE5IUU1lDUe1aTbIxmDkhLhaRYt61kr7GjF87JLbDmacb2gSJZVeydtiNk +VOBgjeCBEapPBK/LR9STjir051aA3BoKAMa6gTDYWlX+7HBkdicQNh621XE+E8lM8us /scL9HJTEeL327JnopKuQDf95ykw8r9JsuqACR8hiRxUo4UtudKcLil6cetxABAnSx5f C2+w9+dTwrJ7/lzlRcO45/HzSlBg4lkpKk+G/WE9/sf4RuJ736IMLm2bIw+Rzf99lO6P Shfwd3zh5kX5AZiqaDJl3zW2vSdLKDNJ7KPPdhq2nkVKwg947058mAWGIMAww18G1PdD KK4g== MIME-Version: 1.0 X-Received: by 10.50.122.99 with SMTP id lr3mr59103629igb.10.1408032270277; Thu, 14 Aug 2014 09:04:30 -0700 (PDT) Received: by 10.43.111.136 with HTTP; Thu, 14 Aug 2014 09:04:30 -0700 (PDT) Date: Thu, 14 Aug 2014 09:04:30 -0700 Message-ID: From: Phil Tomson To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Is Mirage 2.0 released? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1900891951890646074==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1900891951890646074== Content-Type: multipart/alternative; boundary=089e0153835a4d87fd0500990ff5 --089e0153835a4d87fd0500990ff5 Content-Type: text/plain; charset=UTF-8 I only see 1.2.0 in opam packages. Also looking at the github page 1.2.0 is the current release. Phil --089e0153835a4d87fd0500990ff5 Content-Type: text/html; charset=UTF-8
I only see 1.2.0 in opam packages. Also looking at the github page 1.2.0 is the current release.

Phil
--089e0153835a4d87fd0500990ff5-- --===============1900891951890646074== 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 --===============1900891951890646074==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 16:17:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:17: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 1XHxiG-0003K1-BV; Thu, 14 Aug 2014 16:17:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxiF-0003Jw-F9 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:17:15 +0000 Received: from [193.109.254.147:60408] by server-4.bemta-14.messagelabs.com id 62/E3-23592-A01ECE35; Thu, 14 Aug 2014 16:17:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1408033033!9226823!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19921 invoked from network); 14 Aug 2014 16:17:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-27.messagelabs.com with SMTP; 14 Aug 2014 16:17:13 -0000 Received: (qmail 4016 invoked by uid 634); 14 Aug 2014 16:17: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 cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 17:17:12 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 17:17:11 +0100 Message-Id: <9B0C3254-E19D-4A72-8D79-7E69F41835AC@recoil.org> References: To: Phil Tomson 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] Is Mirage 2.0 released? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 14 Aug 2014, at 17:04, Phil Tomson wrote: > I only see 1.2.0 in opam packages. Also looking at the github page 1.2.0 is the current release. The release is *almost* in OPAM, but got blocked due to a Cohttp issue (I'm almost done fixing it!). In practise, this only matters if you're using the Xen/ARM backend, and it's easily fixed by doing some pins. See http://openmirage.org/blog/introducing-xen-minios-arm for more, or just do: opam install mirage-xen-minios opam pin mirage https://github.com/mirage/mirage.git opam pin mirage-xen https://github.com/mirage/mirage-platform opam pin tcpip https://github.com/mirage/mirage-tcpip opam pin cohttp https://github.com/mirage/ocaml-cohttp opam pin mirage-http https://github.com/mirage/mirage-http This gets you all the right libraries for the ARM linking to work (for example with mirage-skeleton's static_website). -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 Aug 14 16:17:19 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:17: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 1XHxiG-0003K1-BV; Thu, 14 Aug 2014 16:17:16 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxiF-0003Jw-F9 for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:17:15 +0000 Received: from [193.109.254.147:60408] by server-4.bemta-14.messagelabs.com id 62/E3-23592-A01ECE35; Thu, 14 Aug 2014 16:17:14 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1408033033!9226823!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19921 invoked from network); 14 Aug 2014 16:17:13 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-27.messagelabs.com with SMTP; 14 Aug 2014 16:17:13 -0000 Received: (qmail 4016 invoked by uid 634); 14 Aug 2014 16:17: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 cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 17:17:12 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 14 Aug 2014 17:17:11 +0100 Message-Id: <9B0C3254-E19D-4A72-8D79-7E69F41835AC@recoil.org> References: To: Phil Tomson 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] Is Mirage 2.0 released? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 14 Aug 2014, at 17:04, Phil Tomson wrote: > I only see 1.2.0 in opam packages. Also looking at the github page 1.2.0 is the current release. The release is *almost* in OPAM, but got blocked due to a Cohttp issue (I'm almost done fixing it!). In practise, this only matters if you're using the Xen/ARM backend, and it's easily fixed by doing some pins. See http://openmirage.org/blog/introducing-xen-minios-arm for more, or just do: opam install mirage-xen-minios opam pin mirage https://github.com/mirage/mirage.git opam pin mirage-xen https://github.com/mirage/mirage-platform opam pin tcpip https://github.com/mirage/mirage-tcpip opam pin cohttp https://github.com/mirage/ocaml-cohttp opam pin mirage-http https://github.com/mirage/mirage-http This gets you all the right libraries for the ARM linking to work (for example with mirage-skeleton's static_website). -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 Aug 14 16:24:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:24: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 1XHxpi-0003Or-12; Thu, 14 Aug 2014 16:24:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxph-0003Om-1v for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:24:57 +0000 Received: from [85.158.143.35:54140] by server-2.bemta-4.messagelabs.com id 75/9F-04525-8D2ECE35; Thu, 14 Aug 2014 16:24:56 +0000 X-Env-Sender: tom.jrbrown@yahoo.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1408033494!13047593!1 X-Originating-IP: [98.138.229.31] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28793 invoked from network); 14 Aug 2014 16:24:55 -0000 Received: from nm38.bullet.mail.ne1.yahoo.com (HELO nm38.bullet.mail.ne1.yahoo.com) (98.138.229.31) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Aug 2014 16:24:55 -0000 Received: from [127.0.0.1] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 16:24:53 -0000 Received: from [98.138.100.116] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 16:22:05 -0000 Received: from [212.82.98.60] by tm107.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 16:22:05 -0000 Received: from [212.82.98.64] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 16:22:04 -0000 Received: from [127.0.0.1] by omp1001.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 16:22:04 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 820435.34823.bm@omp1001.mail.ir2.yahoo.com Received: (qmail 51362 invoked by uid 60001); 14 Aug 2014 16:22:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1408033324; bh=JaxwSIvrVn7TB/gO1xLR7ajMFWyo1lkAlmV4zCO8ApQ=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=n9FPzmfrYIqnUznPSRuXCnyF62lyhxTOFkVZHxRwajBR038UoNr+dOQ4rZcxnSVtDVRlGxjO2+PzeDsyImpHNbUdMT04cnRK6cCUCfzQFEyZ8SoJM96ZZZGLV+vctxw9T82z704ss2626NBMuW2EKf8lqgsXTfWQDwRRS6CTZVk= X-YMail-OSG: zRQcRGUVM1mk_r2wjSX6CXAwqoIPpKVpZTYZpWpiqXrubge bwkQQtMUiVw4YGt8.m754Hmsf8Ok2I1w_0KJaJbD4lMyLp2WhhPcsPNxooTI fd2ioKjTgVB0aJ9hYJTXO_LCO25Oy8wsc9KYgm0aAT0wV0.h7061aKDioCMv DirnoJJF5qptqMw2VJteAcQ6e9hyud5GIk8Jwg0BGMSwWIUUotRRJoNWMPUv emWOrf5fw_0zVnP1Gd3IPidTeSICj8EfbKNGZYSuXMBzkPNpXTccTq3uCFc2 SUAj_89SDevx64pHzvfMxthaddXRGV831AWY1wnqlFB5PDdRSuMseddnDTPu 73qSShCkr8ok6fcpRzcsRKCctT_ysrAY4gWztHBBKuo7A3b3M5Ih_1sAGiHT qSsRl5NBoQZNHrWatTAXJUWhqrw41IhriAVvKj8DNxpVM8pOLSQzwfVe2ALS 1ly_XjD1OS7KZGB5HTBL4ZVym4RlqM1WXJQQGpT8bSCGs5O6vvAftuzzQ8gF MexdZFIxgQBrXJanJxhM- Received: from [185.17.184.206] by web172001.mail.ir2.yahoo.com via HTTP; Thu, 14 Aug 2014 17:22:04 BST X-Rocket-MIMEInfo: 002.001, SXQgbG9va3MgdGhhdCBmdW5jdGlvbiBzdHJpbmdfb2ZfaWQgaW4gbmV0aWYsIHdoaWNoIHJldHVybnMgbmV0d29yayBpbnRlcmZhY2UgaWQgYXMgYSBzdHJpbmcsIGRvZXNuJ3QgZXhpc3RzIGFueSBtb3JlICh0aGUgc2FtZSBhcyBpZF9vZl9zdHJpbmcpLiBhbnkgc3VnZ2VzdGlvbiBwbGVhc2U_CgoKVGhhbmtzLgoBMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 Message-ID: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> Date: Thu, 14 Aug 2014 17:22:04 +0100 From: Tom Brown To: "mirageos-devel@lists.xenproject.org" MIME-Version: 1.0 Subject: [MirageOS-devel] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Tom Brown List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6864149114899693813==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6864149114899693813== Content-Type: multipart/alternative; boundary="1242719849-496694234-1408033324=:49238" --1242719849-496694234-1408033324=:49238 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It looks that function string_of_id in netif, which returns network interfa= ce id as a string, doesn't exists any more (the same as id_of_string). any = suggestion please?=0A=0A=0AThanks.=0A --1242719849-496694234-1408033324=:49238 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
It looks tha= t function string_of_id in netif, which returns network interface id as a s= tring, doesn't exists any more (the same as id_of_string). any suggestion p= lease?

Thanks= .
--1242719849-496694234-1408033324=:49238-- --===============6864149114899693813== 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 --===============6864149114899693813==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 16:24:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:24: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 1XHxpi-0003Or-12; Thu, 14 Aug 2014 16:24:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxph-0003Om-1v for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:24:57 +0000 Received: from [85.158.143.35:54140] by server-2.bemta-4.messagelabs.com id 75/9F-04525-8D2ECE35; Thu, 14 Aug 2014 16:24:56 +0000 X-Env-Sender: tom.jrbrown@yahoo.com X-Msg-Ref: server-11.tower-21.messagelabs.com!1408033494!13047593!1 X-Originating-IP: [98.138.229.31] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE, ML_RADAR_SPEW_LINKS_12,ML_RADAR_SPEW_LINKS_14,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28793 invoked from network); 14 Aug 2014 16:24:55 -0000 Received: from nm38.bullet.mail.ne1.yahoo.com (HELO nm38.bullet.mail.ne1.yahoo.com) (98.138.229.31) by server-11.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Aug 2014 16:24:55 -0000 Received: from [127.0.0.1] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 16:24:53 -0000 Received: from [98.138.100.116] by nm38.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 16:22:05 -0000 Received: from [212.82.98.60] by tm107.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 16:22:05 -0000 Received: from [212.82.98.64] by tm13.bullet.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 16:22:04 -0000 Received: from [127.0.0.1] by omp1001.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 16:22:04 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 820435.34823.bm@omp1001.mail.ir2.yahoo.com Received: (qmail 51362 invoked by uid 60001); 14 Aug 2014 16:22:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1408033324; bh=JaxwSIvrVn7TB/gO1xLR7ajMFWyo1lkAlmV4zCO8ApQ=; h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=n9FPzmfrYIqnUznPSRuXCnyF62lyhxTOFkVZHxRwajBR038UoNr+dOQ4rZcxnSVtDVRlGxjO2+PzeDsyImpHNbUdMT04cnRK6cCUCfzQFEyZ8SoJM96ZZZGLV+vctxw9T82z704ss2626NBMuW2EKf8lqgsXTfWQDwRRS6CTZVk= X-YMail-OSG: zRQcRGUVM1mk_r2wjSX6CXAwqoIPpKVpZTYZpWpiqXrubge bwkQQtMUiVw4YGt8.m754Hmsf8Ok2I1w_0KJaJbD4lMyLp2WhhPcsPNxooTI fd2ioKjTgVB0aJ9hYJTXO_LCO25Oy8wsc9KYgm0aAT0wV0.h7061aKDioCMv DirnoJJF5qptqMw2VJteAcQ6e9hyud5GIk8Jwg0BGMSwWIUUotRRJoNWMPUv emWOrf5fw_0zVnP1Gd3IPidTeSICj8EfbKNGZYSuXMBzkPNpXTccTq3uCFc2 SUAj_89SDevx64pHzvfMxthaddXRGV831AWY1wnqlFB5PDdRSuMseddnDTPu 73qSShCkr8ok6fcpRzcsRKCctT_ysrAY4gWztHBBKuo7A3b3M5Ih_1sAGiHT qSsRl5NBoQZNHrWatTAXJUWhqrw41IhriAVvKj8DNxpVM8pOLSQzwfVe2ALS 1ly_XjD1OS7KZGB5HTBL4ZVym4RlqM1WXJQQGpT8bSCGs5O6vvAftuzzQ8gF MexdZFIxgQBrXJanJxhM- Received: from [185.17.184.206] by web172001.mail.ir2.yahoo.com via HTTP; Thu, 14 Aug 2014 17:22:04 BST X-Rocket-MIMEInfo: 002.001, SXQgbG9va3MgdGhhdCBmdW5jdGlvbiBzdHJpbmdfb2ZfaWQgaW4gbmV0aWYsIHdoaWNoIHJldHVybnMgbmV0d29yayBpbnRlcmZhY2UgaWQgYXMgYSBzdHJpbmcsIGRvZXNuJ3QgZXhpc3RzIGFueSBtb3JlICh0aGUgc2FtZSBhcyBpZF9vZl9zdHJpbmcpLiBhbnkgc3VnZ2VzdGlvbiBwbGVhc2U_CgoKVGhhbmtzLgoBMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 Message-ID: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> Date: Thu, 14 Aug 2014 17:22:04 +0100 From: Tom Brown To: "mirageos-devel@lists.xenproject.org" MIME-Version: 1.0 Subject: [MirageOS-devel] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Tom Brown List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6864149114899693813==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6864149114899693813== Content-Type: multipart/alternative; boundary="1242719849-496694234-1408033324=:49238" --1242719849-496694234-1408033324=:49238 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable It looks that function string_of_id in netif, which returns network interfa= ce id as a string, doesn't exists any more (the same as id_of_string). any = suggestion please?=0A=0A=0AThanks.=0A --1242719849-496694234-1408033324=:49238 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
It looks tha= t function string_of_id in netif, which returns network interface id as a s= tring, doesn't exists any more (the same as id_of_string). any suggestion p= lease?

Thanks= .
--1242719849-496694234-1408033324=:49238-- --===============6864149114899693813== 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 --===============6864149114899693813==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 16:32:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:32: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 1XHxwk-0003So-Kv; Thu, 14 Aug 2014 16:32:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxwj-0003Sj-1e for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:32:13 +0000 Received: from [85.158.139.211:62266] by server-12.bemta-5.messagelabs.com id 5C/B4-22251-C84ECE35; Thu, 14 Aug 2014 16:32:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1408033931!11381958!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11275 invoked from network); 14 Aug 2014 16:32:11 -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; 14 Aug 2014 16:32:11 -0000 Received: (qmail 25281 invoked by uid 634); 14 Aug 2014 16:32:11 -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.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 17:32:11 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> Date: Thu, 14 Aug 2014 17:32:09 +0100 Message-Id: <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> References: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> To: Tom Brown 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] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 17:22, Tom Brown wrote: > It looks that function string_of_id in netif, which returns network interface id as a string, doesn't exists any more (the same as id_of_string). any suggestion please? What context are you trying to use this in? mirage-net-unix/xen just expose the type id=string; include V1.NETWORK with type 'a io = 'a Lwt.t and type page_aligned_buffer = Io_page.t and type buffer = Cstruct.t and type id = string and type macaddr = Macaddr.t Are you trying to use it within a JOB functor, where it's still abstract? I'm plumbing through sexpr conversion functions for that usecase -- or do you specifically need string for something? -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 Aug 14 16:32:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 16:32: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 1XHxwk-0003So-Kv; Thu, 14 Aug 2014 16:32:14 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHxwj-0003Sj-1e for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 16:32:13 +0000 Received: from [85.158.139.211:62266] by server-12.bemta-5.messagelabs.com id 5C/B4-22251-C84ECE35; Thu, 14 Aug 2014 16:32:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1408033931!11381958!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11275 invoked from network); 14 Aug 2014 16:32:11 -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; 14 Aug 2014 16:32:11 -0000 Received: (qmail 25281 invoked by uid 634); 14 Aug 2014 16:32:11 -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.98]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 14 Aug 2014 17:32:11 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> Date: Thu, 14 Aug 2014 17:32:09 +0100 Message-Id: <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> References: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> To: Tom Brown 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] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 17:22, Tom Brown wrote: > It looks that function string_of_id in netif, which returns network interface id as a string, doesn't exists any more (the same as id_of_string). any suggestion please? What context are you trying to use this in? mirage-net-unix/xen just expose the type id=string; include V1.NETWORK with type 'a io = 'a Lwt.t and type page_aligned_buffer = Io_page.t and type buffer = Cstruct.t and type id = string and type macaddr = Macaddr.t Are you trying to use it within a JOB functor, where it's still abstract? I'm plumbing through sexpr conversion functions for that usecase -- or do you specifically need string for something? -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 Aug 14 17:51:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 17:51:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHzBB-0004vX-TN; Thu, 14 Aug 2014 17:51:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHzBA-0004vN-Du for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 17:51:12 +0000 Received: from [85.158.137.68:55779] by server-3.bemta-3.messagelabs.com id 12/5C-22751-F07FCE35; Thu, 14 Aug 2014 17:51:11 +0000 X-Env-Sender: tom.jrbrown@yahoo.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1408038668!10018708!1 X-Originating-IP: [98.138.229.24] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, 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 14949 invoked from network); 14 Aug 2014 17:51:10 -0000 Received: from nm31.bullet.mail.ne1.yahoo.com (HELO nm31.bullet.mail.ne1.yahoo.com) (98.138.229.24) by server-9.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Aug 2014 17:51:10 -0000 Received: from [127.0.0.1] by nm31.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 17:51:08 -0000 Received: from [98.138.100.111] by nm31.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 Received: from [212.82.98.48] by tm100.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 Received: from [212.82.98.67] by tm1.bullet.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 Received: from [127.0.0.1] by omp1004.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 402263.43115.bm@omp1004.mail.ir2.yahoo.com Received: (qmail 12762 invoked by uid 60001); 14 Aug 2014 17:48:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1408038499; bh=BN55fcnQlbVNmIsGk++3Vv1xb/gWlYQH7i2EQ5fxo+Y=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=H6QjYbu3JHRHad6DshoQcXU87t/Gva+f9j8FBUdIq28Tu2etAD898tzreyRFgc6TYrCmx+XZtQkvED6jkGi0VoYWjjN0AjtzpsHwJSBn+UsDkq6xJbRk4vsZRVNUQ0ogfH7IerdnV16g61EuLvATMu8J3kNcU7BbzWhvngQa/+k= X-YMail-OSG: 4OcCuGoVM1kLYLwvvZc7mxy8k9SeRXwrpqOOpJS_CBIkQlu uSygzJhWho0bJNSw5uwPb7PBnQlGlQnc8KXgVZPnK9SISEr5MnTVE268mRWD 6n.ep.SvTUmtP3.vG27t7nsREVLkB5l4FUt0hZl8t6Do0Vx0tCRBn2I5EAgc eQEj3X5kLf0wqcjDxgl03AzTZM_7M8BbYdHQuUV3LsOs4VKl6A7vKPRV5v3W S.7Y893F.v8qJ80mIuhO7DDWc3lX9dX3uJeHtUYFgBZFjZslno4d63rYHDfx Yb1tsVX7UCQsttiXxWeZzonNOjyiSpegmMDXNWcHaUTh8kdmXQRH7NWz2XbK gUFMp839_M5VtxEWiBl29m.I4n.WGuWhfkZ4nWuaxeQeYL_4xRfclamS6XrP HmNo2_dcEi87aROAkhfiEoL0T5W.s248KxIsXcOFY4OHZjsM6r2ktDdJYveO LM1WayqQPVAWvOKULKnK7Lhp5mOf8nkA_8H3QBLqoZpERnip6rSX.DyuXEGG tkG..DGkTuQUnbFf5N_IX8eVyxvLXybgjx9cM3ebb_suj7ZKkKFJTew-- Received: from [95.130.9.190] by web172003.mail.ir2.yahoo.com via HTTP; Thu, 14 Aug 2014 18:48:19 BST X-Rocket-MIMEInfo: 002.001, SSBhbSB1c2luZyB0aGF0IHdpdGhpbiB0aGUgbWFpbiBtb2R1bGUsIGFuZCB0byBwcmludCBvdXQgZGV2aWNlIGlkLiBQcmludGluZyBvdXQgKE4uaWQgZGV2KSByZXN1bHRzIGluIGVycm9yICJFcnJvcjogVGhpcyBleHByZXNzaW9uIGhhcyB0eXBlIE4uaWQgYnV0IGFuIGV4cHJlc3Npb24gd2FzIGV4cGVjdGVkIG9mIHR5cGUgc3RyaW5nIi4KCkFzIHlvdSBhbHNvIG1lbnRpb25lZCwgdGhlIHByb2JsZW0gaXMgdGhhdCB0eXBlIGlkIGlzIGFic3RyYWN0LgoKCgpPbiBUaHVyc2RheSwgMTQgQXVndXN0IDIwMTQBMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 References: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> Message-ID: <1408038499.24611.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Thu, 14 Aug 2014 18:48:19 +0100 From: Tom Brown To: Anil Madhavapeddy In-Reply-To: <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Tom Brown List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1489849568310758407==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1489849568310758407== Content-Type: multipart/alternative; boundary="-661429482-1190436011-1408038499=:24611" ---661429482-1190436011-1408038499=:24611 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I am using that within the main module, and to print out device id. Printin= g out (N.id dev) results in error "Error: This expression has type N.id but= an expression was expected of type string".=0A=0AAs you also mentioned, th= e problem is that type id is abstract.=0A=0A=0A=0AOn Thursday, 14 August 20= 14, 16:32, Anil Madhavapeddy wrote:=0A =0A=0A=0AOn 14 Aug= 2014, at 17:22, Tom Brown wrote:=0A=0A=0A> It look= s that function string_of_id in netif, which returns network interface id a= s a string, doesn't exists any more (the same as id_of_string). any suggest= ion please?=0A=0AWhat context are you trying to use this in?=A0 mirage-net-= unix/xen just expose the type id=3Dstring;=0A=0A=A0 =A0 include V1.NETWORK= =0A=A0 =A0 with type 'a io =3D 'a Lwt.t=0A=A0 =A0 and type=A0 =A0 page_ali= gned_buffer =3D Io_page.t=0A=A0 =A0 and type=A0 =A0 buffer =3D Cstruct.t= =0A=A0 =A0 and type=A0 =A0 id =3D string=0A=A0 =A0 and type=A0 =A0 macadd= r =3D Macaddr.t=0A=0AAre you trying to use it within a JOB functor, where i= t's still abstract?=A0 I'm plumbing through sexpr conversion functions for = that usecase -- or do you specifically need string for something?=0A=0A-ani= l ---661429482-1190436011-1408038499=:24611 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I am u= sing that within the main module, and to print out device id. Printing out = (N.id dev) results in error "Error: This expression has type N.id but an ex= pression was expected of type string".
As you = also mentioned, the problem is that type id is abstract.


On Thursday, 14 August 2014, 16:32, Anil Madhavapeddy <anil@recoil.o= rg> wrote:


On 14 Aug 2014= , at 17:22, Tom Brown <tom= .jrbrown@yahoo.com> wrote:


> It looks that function string_of_id in netif, which returns = network interface id as a string, doesn't exists any more (the same as id_o= f_string). any suggestion please?


What context are you trying to use this in?  mirage-net-unix/xen just expose the type id= =3Dstring;

    include V1.NETWORK
    with type 'a io =3D 'a Lwt.t
    and type    page_aligned_bu= ffer =3D Io_page.t
    an= d type    buffer =3D Cstruct.t
    and type    id =3D string
    and type    macaddr =3D Mac= addr.t

Are you trying to use it within a JOB functor, where it's stil= l abstract?  I'm plumbing through sexpr conversion functions for that = usecase -- or do you specifically need string for something?

-anil

---661429482-1190436011-1408038499=:24611-- --===============1489849568310758407== 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 --===============1489849568310758407==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 14 17:51:16 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 14 Aug 2014 17:51:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHzBB-0004vX-TN; Thu, 14 Aug 2014 17:51:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XHzBA-0004vN-Du for mirageos-devel@lists.xenproject.org; Thu, 14 Aug 2014 17:51:12 +0000 Received: from [85.158.137.68:55779] by server-3.bemta-3.messagelabs.com id 12/5C-22751-F07FCE35; Thu, 14 Aug 2014 17:51:11 +0000 X-Env-Sender: tom.jrbrown@yahoo.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1408038668!10018708!1 X-Originating-IP: [98.138.229.24] X-SpamReason: No, hits=0.8 required=7.0 tests=BODY_RANDOM_LONG, 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 14949 invoked from network); 14 Aug 2014 17:51:10 -0000 Received: from nm31.bullet.mail.ne1.yahoo.com (HELO nm31.bullet.mail.ne1.yahoo.com) (98.138.229.24) by server-9.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Aug 2014 17:51:10 -0000 Received: from [127.0.0.1] by nm31.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 17:51:08 -0000 Received: from [98.138.100.111] by nm31.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 Received: from [212.82.98.48] by tm100.bullet.mail.ne1.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 Received: from [212.82.98.67] by tm1.bullet.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 Received: from [127.0.0.1] by omp1004.mail.ir2.yahoo.com with NNFMP; 14 Aug 2014 17:48:19 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 402263.43115.bm@omp1004.mail.ir2.yahoo.com Received: (qmail 12762 invoked by uid 60001); 14 Aug 2014 17:48:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1408038499; bh=BN55fcnQlbVNmIsGk++3Vv1xb/gWlYQH7i2EQ5fxo+Y=; h=References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=H6QjYbu3JHRHad6DshoQcXU87t/Gva+f9j8FBUdIq28Tu2etAD898tzreyRFgc6TYrCmx+XZtQkvED6jkGi0VoYWjjN0AjtzpsHwJSBn+UsDkq6xJbRk4vsZRVNUQ0ogfH7IerdnV16g61EuLvATMu8J3kNcU7BbzWhvngQa/+k= X-YMail-OSG: 4OcCuGoVM1kLYLwvvZc7mxy8k9SeRXwrpqOOpJS_CBIkQlu uSygzJhWho0bJNSw5uwPb7PBnQlGlQnc8KXgVZPnK9SISEr5MnTVE268mRWD 6n.ep.SvTUmtP3.vG27t7nsREVLkB5l4FUt0hZl8t6Do0Vx0tCRBn2I5EAgc eQEj3X5kLf0wqcjDxgl03AzTZM_7M8BbYdHQuUV3LsOs4VKl6A7vKPRV5v3W S.7Y893F.v8qJ80mIuhO7DDWc3lX9dX3uJeHtUYFgBZFjZslno4d63rYHDfx Yb1tsVX7UCQsttiXxWeZzonNOjyiSpegmMDXNWcHaUTh8kdmXQRH7NWz2XbK gUFMp839_M5VtxEWiBl29m.I4n.WGuWhfkZ4nWuaxeQeYL_4xRfclamS6XrP HmNo2_dcEi87aROAkhfiEoL0T5W.s248KxIsXcOFY4OHZjsM6r2ktDdJYveO LM1WayqQPVAWvOKULKnK7Lhp5mOf8nkA_8H3QBLqoZpERnip6rSX.DyuXEGG tkG..DGkTuQUnbFf5N_IX8eVyxvLXybgjx9cM3ebb_suj7ZKkKFJTew-- Received: from [95.130.9.190] by web172003.mail.ir2.yahoo.com via HTTP; Thu, 14 Aug 2014 18:48:19 BST X-Rocket-MIMEInfo: 002.001, SSBhbSB1c2luZyB0aGF0IHdpdGhpbiB0aGUgbWFpbiBtb2R1bGUsIGFuZCB0byBwcmludCBvdXQgZGV2aWNlIGlkLiBQcmludGluZyBvdXQgKE4uaWQgZGV2KSByZXN1bHRzIGluIGVycm9yICJFcnJvcjogVGhpcyBleHByZXNzaW9uIGhhcyB0eXBlIE4uaWQgYnV0IGFuIGV4cHJlc3Npb24gd2FzIGV4cGVjdGVkIG9mIHR5cGUgc3RyaW5nIi4KCkFzIHlvdSBhbHNvIG1lbnRpb25lZCwgdGhlIHByb2JsZW0gaXMgdGhhdCB0eXBlIGlkIGlzIGFic3RyYWN0LgoKCgpPbiBUaHVyc2RheSwgMTQgQXVndXN0IDIwMTQBMAEBAQE- X-Mailer: YahooMailWebService/0.8.201.700 References: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> Message-ID: <1408038499.24611.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Thu, 14 Aug 2014 18:48:19 +0100 From: Tom Brown To: Anil Madhavapeddy In-Reply-To: <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> MIME-Version: 1.0 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Tom Brown List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1489849568310758407==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1489849568310758407== Content-Type: multipart/alternative; boundary="-661429482-1190436011-1408038499=:24611" ---661429482-1190436011-1408038499=:24611 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable I am using that within the main module, and to print out device id. Printin= g out (N.id dev) results in error "Error: This expression has type N.id but= an expression was expected of type string".=0A=0AAs you also mentioned, th= e problem is that type id is abstract.=0A=0A=0A=0AOn Thursday, 14 August 20= 14, 16:32, Anil Madhavapeddy wrote:=0A =0A=0A=0AOn 14 Aug= 2014, at 17:22, Tom Brown wrote:=0A=0A=0A> It look= s that function string_of_id in netif, which returns network interface id a= s a string, doesn't exists any more (the same as id_of_string). any suggest= ion please?=0A=0AWhat context are you trying to use this in?=A0 mirage-net-= unix/xen just expose the type id=3Dstring;=0A=0A=A0 =A0 include V1.NETWORK= =0A=A0 =A0 with type 'a io =3D 'a Lwt.t=0A=A0 =A0 and type=A0 =A0 page_ali= gned_buffer =3D Io_page.t=0A=A0 =A0 and type=A0 =A0 buffer =3D Cstruct.t= =0A=A0 =A0 and type=A0 =A0 id =3D string=0A=A0 =A0 and type=A0 =A0 macadd= r =3D Macaddr.t=0A=0AAre you trying to use it within a JOB functor, where i= t's still abstract?=A0 I'm plumbing through sexpr conversion functions for = that usecase -- or do you specifically need string for something?=0A=0A-ani= l ---661429482-1190436011-1408038499=:24611 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
I am u= sing that within the main module, and to print out device id. Printing out = (N.id dev) results in error "Error: This expression has type N.id but an ex= pression was expected of type string".
As you = also mentioned, the problem is that type id is abstract.


On Thursday, 14 August 2014, 16:32, Anil Madhavapeddy <anil@recoil.o= rg> wrote:


On 14 Aug 2014= , at 17:22, Tom Brown <tom= .jrbrown@yahoo.com> wrote:


> It looks that function string_of_id in netif, which returns = network interface id as a string, doesn't exists any more (the same as id_o= f_string). any suggestion please?


What context are you trying to use this in?  mirage-net-unix/xen just expose the type id= =3Dstring;

    include V1.NETWORK
    with type 'a io =3D 'a Lwt.t
    and type    page_aligned_bu= ffer =3D Io_page.t
    an= d type    buffer =3D Cstruct.t
    and type    id =3D string
    and type    macaddr =3D Mac= addr.t

Are you trying to use it within a JOB functor, where it's stil= l abstract?  I'm plumbing through sexpr conversion functions for that = usecase -- or do you specifically need string for something?

-anil

---661429482-1190436011-1408038499=:24611-- --===============1489849568310758407== 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 --===============1489849568310758407==-- From mirageos-devel-bounces@lists.xenproject.org Sat Aug 16 14:50:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 16 Aug 2014 14:50: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 1XIfJP-0006i7-94; Sat, 16 Aug 2014 14:50:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIfJO-0006i2-6E for mirageos-devel@lists.xenproject.org; Sat, 16 Aug 2014 14:50:30 +0000 Received: from [193.109.254.147:49551] by server-9.bemta-14.messagelabs.com id EB/6F-31535-5BF6FE35; Sat, 16 Aug 2014 14:50:29 +0000 X-Env-Sender: nick@internetmachines.co.uk X-Msg-Ref: server-6.tower-27.messagelabs.com!1408200628!12832741!1 X-Originating-IP: [213.138.108.180] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22189 invoked from network); 16 Aug 2014 14:50:28 -0000 Received: from adm02.default.planetlarg.uk0.bigv.io (HELO mail.localhost) (213.138.108.180) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Aug 2014 14:50:28 -0000 Received: by mail.localhost (Postfix, from userid 2001) id 67DC64C162; Sat, 16 Aug 2014 14:50:26 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on adm02.default.planetlarg.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.2 Received: from [10.0.1.42] (unknown [62.254.230.80]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localhost (Postfix) with ESMTPSA id 86B974C160 for ; Sat, 16 Aug 2014 14:50:25 +0000 (UTC) From: Nick Hardiman Message-Id: Date: Sat, 16 Aug 2014 15:50: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] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8061756372207889173==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8061756372207889173== Content-Type: multipart/signed; boundary="Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A"; protocol="application/pgp-signature"; micalg=pgp-sha1 --Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A Content-Type: multipart/alternative; boundary="Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204" --Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial application. I think an OpenMirage unikernel might work well as a workload container = (container as in 'a package of stuff', not as in 'Docker'). However, = before I burn evenings and weekends going off in the wrong direction = (done that plenty), I'd like to get some expert criticism first.=20 How would I present the high level idea, and how would I get advice on = how to use work done so far on OpenMirage? Many thanks,=20 Nick --Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick




= --Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204-- --Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A 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 - http://gpgtools.org iQEcBAEBAgAGBQJT72+vAAoJEEpTXxTuqGWVx28IAIiN2vny2W2Gq9ygMCuTbTBQ zITZzXIC5T7JHpYwkvYXaYa4W67T/V0li81b4VcvFrdqrlfM3sMnG4cK0vUIckRL vYgaRNbpYT+cMMWektIoO8AukYTWzCBYsFlm6A556UJQH5klXHcay/j+xrMimJ4X UKCNgyWpjrahfVIsNr64r2EZfZ0bR2L6+Ifk7uAcpOlNbSVn6a3A0KSrhs6EF15r xKo6VU6aJRb82p+zDULR90A7/qX5iwnvWsY/pYpwfIIrWzQYVOhDm2BhyLUPvcUn r6XZ4/tJiNKpjHlR4TvOw/1X2ozRmKEwYbmfUkAGPYV4polJ+CDVh5kT1qvnOTM= =SUwm -----END PGP SIGNATURE----- --Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A-- --===============8061756372207889173== 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 --===============8061756372207889173==-- From mirageos-devel-bounces@lists.xenproject.org Sat Aug 16 14:50:38 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 16 Aug 2014 14:50: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 1XIfJP-0006i7-94; Sat, 16 Aug 2014 14:50:31 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIfJO-0006i2-6E for mirageos-devel@lists.xenproject.org; Sat, 16 Aug 2014 14:50:30 +0000 Received: from [193.109.254.147:49551] by server-9.bemta-14.messagelabs.com id EB/6F-31535-5BF6FE35; Sat, 16 Aug 2014 14:50:29 +0000 X-Env-Sender: nick@internetmachines.co.uk X-Msg-Ref: server-6.tower-27.messagelabs.com!1408200628!12832741!1 X-Originating-IP: [213.138.108.180] X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22189 invoked from network); 16 Aug 2014 14:50:28 -0000 Received: from adm02.default.planetlarg.uk0.bigv.io (HELO mail.localhost) (213.138.108.180) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Aug 2014 14:50:28 -0000 Received: by mail.localhost (Postfix, from userid 2001) id 67DC64C162; Sat, 16 Aug 2014 14:50:26 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on adm02.default.planetlarg.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.2 Received: from [10.0.1.42] (unknown [62.254.230.80]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localhost (Postfix) with ESMTPSA id 86B974C160 for ; Sat, 16 Aug 2014 14:50:25 +0000 (UTC) From: Nick Hardiman Message-Id: Date: Sat, 16 Aug 2014 15:50: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] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============8061756372207889173==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8061756372207889173== Content-Type: multipart/signed; boundary="Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A"; protocol="application/pgp-signature"; micalg=pgp-sha1 --Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A Content-Type: multipart/alternative; boundary="Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204" --Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial application. I think an OpenMirage unikernel might work well as a workload container = (container as in 'a package of stuff', not as in 'Docker'). However, = before I burn evenings and weekends going off in the wrong direction = (done that plenty), I'd like to get some expert criticism first.=20 How would I present the high level idea, and how would I get advice on = how to use work done so far on OpenMirage? Many thanks,=20 Nick --Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick




= --Apple-Mail=_97EE4151-93C5-4D7D-BBAA-254545888204-- --Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A 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 - http://gpgtools.org iQEcBAEBAgAGBQJT72+vAAoJEEpTXxTuqGWVx28IAIiN2vny2W2Gq9ygMCuTbTBQ zITZzXIC5T7JHpYwkvYXaYa4W67T/V0li81b4VcvFrdqrlfM3sMnG4cK0vUIckRL vYgaRNbpYT+cMMWektIoO8AukYTWzCBYsFlm6A556UJQH5klXHcay/j+xrMimJ4X UKCNgyWpjrahfVIsNr64r2EZfZ0bR2L6+Ifk7uAcpOlNbSVn6a3A0KSrhs6EF15r xKo6VU6aJRb82p+zDULR90A7/qX5iwnvWsY/pYpwfIIrWzQYVOhDm2BhyLUPvcUn r6XZ4/tJiNKpjHlR4TvOw/1X2ozRmKEwYbmfUkAGPYV4polJ+CDVh5kT1qvnOTM= =SUwm -----END PGP SIGNATURE----- --Apple-Mail=_6E3F8F9F-B573-4C59-B7D2-2DE161D5568A-- --===============8061756372207889173== 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 --===============8061756372207889173==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 10:27:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 10:27: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 1XIxge-0004mC-IX; Sun, 17 Aug 2014 10:27:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIxgd-0004m5-6k for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 10:27:43 +0000 Received: from [193.109.254.147:37152] by server-14.bemta-14.messagelabs.com id 52/03-02763-E9380F35; Sun, 17 Aug 2014 10:27:42 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1408271261!9610223!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17450 invoked from network); 17 Aug 2014 10:27:41 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 10:27:41 -0000 Received: by mail-wg0-f48.google.com with SMTP id x13so3820507wgg.31 for ; Sun, 17 Aug 2014 03:27:41 -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=0ZJXzvF71obKENawZmm6m+MhD52xQsb89y/kaxp+RbI=; b=H3l2sI6aOgMKunjfevVEXOMFwgTRB/5BHfDbKJN+UFTRmzl+NPO5rl4R+7aml9gdFI NgNU+jwzwdwWb8aWoCPSq10iUW0KBwx/Va5bpabIgSmlp8kIFsV/f+I8Ct1yzYDyfr9i /6cABMXQrDpU0iRA2EQGmoUrsZdlY3wtoM/eHSZaUa2Dmz4P3DOPMHu1ywOrapLUvHdY nO6iMKHFpa/fsoAhXc6aP2aTTBtN5tpgvYZ4vTM+2io4lEfZ2ZRgXEks43kUFzm4d2zY DmeE9tiqRqHu5cfrtUc5iZARZW2iueGsI8HGlOvnqJ1cmUiU0WyMTiFLyjtiqtvPpLon WZpw== X-Received: by 10.180.96.33 with SMTP id dp1mr32871088wib.20.1408271261055; Sun, 17 Aug 2014 03:27:41 -0700 (PDT) Received: from [192.168.1.65] (192.Red-83-35-72.dynamicIP.rima-tde.net. [83.35.72.192]) by mx.google.com with ESMTPSA id mw4sm25944954wic.20.2014.08.17.03.27.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Aug 2014 03:27:40 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 17 Aug 2014 12:27:37 +0200 Message-Id: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> References: To: Nick Hardiman X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2890090237068383894==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2890090237068383894== Content-Type: multipart/alternative; boundary="Apple-Mail=_C65D4475-7166-473C-BD3F-9CBE60A7462D" --Apple-Mail=_C65D4475-7166-473C-BD3F-9CBE60A7462D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Which kind of workload are you trying to run? If it's an OCaml program, = yes sure, MirageOS might be a good option.=20 If not, there are other unikernels: HalVM in Haskell, Erlang-on-Xen, OSv = for the JVM, etc... They are basically all tied to a specific language = runtime environment and they can interoperate between each other and = with legacy OS at the API level. Thomas On 16 Aug 2014, at 16:50, Nick Hardiman = wrote: > I have been trying to come up with an easy way to move workloads = around. This is for a home lab POC, not for a commercial application. >=20 > I think an OpenMirage unikernel might work well as a workload = container (container as in 'a package of stuff', not as in 'Docker'). = However, before I burn evenings and weekends going off in the wrong = direction (done that plenty), I'd like to get some expert criticism = first.=20 >=20 > How would I present the high level idea, and how would I get advice on = how to use work done so far on OpenMirage? >=20 > Many thanks,=20 > Nick >=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=_C65D4475-7166-473C-BD3F-9CBE60A7462D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

Which kind of workload are = you trying to run? If it's an OCaml program, yes sure, MirageOS might be = a good option. 

If not, there are other = unikernels: HalVM in Haskell, Erlang-on-Xen, OSv for the JVM, etc... = They are basically all tied to a specific language runtime environment = and they can interoperate between each other and with legacy OS at the = API = level.

Thomas


<= br>

On 16 Aug 2014, at 16:50, Nick Hardiman = <nick@internetmachines.co.uk> wrote:

I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick



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

= --Apple-Mail=_C65D4475-7166-473C-BD3F-9CBE60A7462D-- --===============2890090237068383894== 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 --===============2890090237068383894==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 10:27:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 10:27: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 1XIxge-0004mC-IX; Sun, 17 Aug 2014 10:27:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIxgd-0004m5-6k for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 10:27:43 +0000 Received: from [193.109.254.147:37152] by server-14.bemta-14.messagelabs.com id 52/03-02763-E9380F35; Sun, 17 Aug 2014 10:27:42 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-27.messagelabs.com!1408271261!9610223!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_60_70,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17450 invoked from network); 17 Aug 2014 10:27:41 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-11.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 10:27:41 -0000 Received: by mail-wg0-f48.google.com with SMTP id x13so3820507wgg.31 for ; Sun, 17 Aug 2014 03:27:41 -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=0ZJXzvF71obKENawZmm6m+MhD52xQsb89y/kaxp+RbI=; b=H3l2sI6aOgMKunjfevVEXOMFwgTRB/5BHfDbKJN+UFTRmzl+NPO5rl4R+7aml9gdFI NgNU+jwzwdwWb8aWoCPSq10iUW0KBwx/Va5bpabIgSmlp8kIFsV/f+I8Ct1yzYDyfr9i /6cABMXQrDpU0iRA2EQGmoUrsZdlY3wtoM/eHSZaUa2Dmz4P3DOPMHu1ywOrapLUvHdY nO6iMKHFpa/fsoAhXc6aP2aTTBtN5tpgvYZ4vTM+2io4lEfZ2ZRgXEks43kUFzm4d2zY DmeE9tiqRqHu5cfrtUc5iZARZW2iueGsI8HGlOvnqJ1cmUiU0WyMTiFLyjtiqtvPpLon WZpw== X-Received: by 10.180.96.33 with SMTP id dp1mr32871088wib.20.1408271261055; Sun, 17 Aug 2014 03:27:41 -0700 (PDT) Received: from [192.168.1.65] (192.Red-83-35-72.dynamicIP.rima-tde.net. [83.35.72.192]) by mx.google.com with ESMTPSA id mw4sm25944954wic.20.2014.08.17.03.27.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 17 Aug 2014 03:27:40 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Sun, 17 Aug 2014 12:27:37 +0200 Message-Id: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> References: To: Nick Hardiman X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2890090237068383894==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2890090237068383894== Content-Type: multipart/alternative; boundary="Apple-Mail=_C65D4475-7166-473C-BD3F-9CBE60A7462D" --Apple-Mail=_C65D4475-7166-473C-BD3F-9CBE60A7462D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Which kind of workload are you trying to run? If it's an OCaml program, = yes sure, MirageOS might be a good option.=20 If not, there are other unikernels: HalVM in Haskell, Erlang-on-Xen, OSv = for the JVM, etc... They are basically all tied to a specific language = runtime environment and they can interoperate between each other and = with legacy OS at the API level. Thomas On 16 Aug 2014, at 16:50, Nick Hardiman = wrote: > I have been trying to come up with an easy way to move workloads = around. This is for a home lab POC, not for a commercial application. >=20 > I think an OpenMirage unikernel might work well as a workload = container (container as in 'a package of stuff', not as in 'Docker'). = However, before I burn evenings and weekends going off in the wrong = direction (done that plenty), I'd like to get some expert criticism = first.=20 >=20 > How would I present the high level idea, and how would I get advice on = how to use work done so far on OpenMirage? >=20 > Many thanks,=20 > Nick >=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=_C65D4475-7166-473C-BD3F-9CBE60A7462D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi,

Which kind of workload are = you trying to run? If it's an OCaml program, yes sure, MirageOS might be = a good option. 

If not, there are other = unikernels: HalVM in Haskell, Erlang-on-Xen, OSv for the JVM, etc... = They are basically all tied to a specific language runtime environment = and they can interoperate between each other and with legacy OS at the = API = level.

Thomas


<= br>

On 16 Aug 2014, at 16:50, Nick Hardiman = <nick@internetmachines.co.uk> wrote:

I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick



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

= --Apple-Mail=_C65D4475-7166-473C-BD3F-9CBE60A7462D-- --===============2890090237068383894== 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 --===============2890090237068383894==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 11:24:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 11:24: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 1XIyZN-00057u-UR; Sun, 17 Aug 2014 11:24:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIyZM-00057p-Lm for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 11:24:16 +0000 Received: from [85.158.143.35:28795] by server-1.bemta-4.messagelabs.com id 54/B6-05872-FD090F35; Sun, 17 Aug 2014 11:24:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1408274654!13467439!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6516 invoked from network); 17 Aug 2014 11:24:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-21.messagelabs.com with SMTP; 17 Aug 2014 11:24:14 -0000 Received: (qmail 17138 invoked by uid 634); 17 Aug 2014 11:24:14 -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 50-203-222-2-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.2) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 12:24:13 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> Date: Sun, 17 Aug 2014 06:24:11 -0500 Message-Id: References: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> To: Thomas Gazagnaire 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] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3325074322244094116==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3325074322244094116== Content-Type: multipart/alternative; boundary="Apple-Mail=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4" --Apple-Mail=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Yeah, if the workloads are fairly self-contained, unikernels are great. = It gets more interesting when they form a distributed system, since a = group of unikernels may need to be migrated as a group. I'd suggest starting by outlining the scenario you want to build, and = then we can help you work through the unikernel components to build. = Are you looking at ARM or x86 for your POC? For instance, beginning with just a static website workload, and = building the HTTP proxies to do workload balancing would be a small but = significant start (since it would require building out the proxy and = migration infrastructure). -anil On 17 Aug 2014, at 05:27, Thomas Gazagnaire = wrote: > Hi, >=20 > Which kind of workload are you trying to run? If it's an OCaml = program, yes sure, MirageOS might be a good option.=20 >=20 > If not, there are other unikernels: HalVM in Haskell, Erlang-on-Xen, = OSv for the JVM, etc... They are basically all tied to a specific = language runtime environment and they can interoperate between each = other and with legacy OS at the API level. >=20 > Thomas >=20 >=20 >=20 >=20 > On 16 Aug 2014, at 16:50, Nick Hardiman = wrote: >=20 >> I have been trying to come up with an easy way to move workloads = around. This is for a home lab POC, not for a commercial application. >>=20 >> I think an OpenMirage unikernel might work well as a workload = container (container as in 'a package of stuff', not as in 'Docker'). = However, before I burn evenings and weekends going off in the wrong = direction (done that plenty), I'd like to get some expert criticism = first.=20 >>=20 >> How would I present the high level idea, and how would I get advice = on how to use work done so far on OpenMirage? >>=20 >> Many thanks,=20 >> Nick >>=20 >>=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=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Yeah, = if the workloads are fairly self-contained, unikernels are great. =  It gets more interesting when they form a distributed system, = since a group of unikernels may need to be migrated as a = group.

I'd suggest starting by outlining the scenario = you want to build, and then we can help you work through the unikernel = components to build.  Are you looking at ARM or x86 for your = POC?

For instance, beginning with just a static = website workload, and building the HTTP proxies to do workload balancing = would be a small but significant start (since it would require building = out the proxy and migration = infrastructure).

-anil

<= div>
On 17 Aug 2014, at 05:27, Thomas Gazagnaire <thomas@gazagnaire.org> = wrote:

Hi,

Which kind of workload are = you trying to run? If it's an OCaml program, yes sure, MirageOS might be = a good option. 

If not, there are other = unikernels: HalVM in Haskell, Erlang-on-Xen, OSv for the JVM, etc... = They are basically all tied to a specific language runtime environment = and they can interoperate between each other and with legacy OS at the = API = level.

Thomas


<= br>

On 16 Aug 2014, at 16:50, Nick Hardiman = <nick@internetmachines.co.uk> wrote:

I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick



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

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

= --Apple-Mail=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4-- --===============3325074322244094116== 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 --===============3325074322244094116==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 11:24:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 11:24: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 1XIyZN-00057u-UR; Sun, 17 Aug 2014 11:24:17 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIyZM-00057p-Lm for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 11:24:16 +0000 Received: from [85.158.143.35:28795] by server-1.bemta-4.messagelabs.com id 54/B6-05872-FD090F35; Sun, 17 Aug 2014 11:24:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1408274654!13467439!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6516 invoked from network); 17 Aug 2014 11:24:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-4.tower-21.messagelabs.com with SMTP; 17 Aug 2014 11:24:14 -0000 Received: (qmail 17138 invoked by uid 634); 17 Aug 2014 11:24:14 -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 50-203-222-2-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.2) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 12:24:13 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> Date: Sun, 17 Aug 2014 06:24:11 -0500 Message-Id: References: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> To: Thomas Gazagnaire 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] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============3325074322244094116==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3325074322244094116== Content-Type: multipart/alternative; boundary="Apple-Mail=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4" --Apple-Mail=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Yeah, if the workloads are fairly self-contained, unikernels are great. = It gets more interesting when they form a distributed system, since a = group of unikernels may need to be migrated as a group. I'd suggest starting by outlining the scenario you want to build, and = then we can help you work through the unikernel components to build. = Are you looking at ARM or x86 for your POC? For instance, beginning with just a static website workload, and = building the HTTP proxies to do workload balancing would be a small but = significant start (since it would require building out the proxy and = migration infrastructure). -anil On 17 Aug 2014, at 05:27, Thomas Gazagnaire = wrote: > Hi, >=20 > Which kind of workload are you trying to run? If it's an OCaml = program, yes sure, MirageOS might be a good option.=20 >=20 > If not, there are other unikernels: HalVM in Haskell, Erlang-on-Xen, = OSv for the JVM, etc... They are basically all tied to a specific = language runtime environment and they can interoperate between each = other and with legacy OS at the API level. >=20 > Thomas >=20 >=20 >=20 >=20 > On 16 Aug 2014, at 16:50, Nick Hardiman = wrote: >=20 >> I have been trying to come up with an easy way to move workloads = around. This is for a home lab POC, not for a commercial application. >>=20 >> I think an OpenMirage unikernel might work well as a workload = container (container as in 'a package of stuff', not as in 'Docker'). = However, before I burn evenings and weekends going off in the wrong = direction (done that plenty), I'd like to get some expert criticism = first.=20 >>=20 >> How would I present the high level idea, and how would I get advice = on how to use work done so far on OpenMirage? >>=20 >> Many thanks,=20 >> Nick >>=20 >>=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=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Yeah, = if the workloads are fairly self-contained, unikernels are great. =  It gets more interesting when they form a distributed system, = since a group of unikernels may need to be migrated as a = group.

I'd suggest starting by outlining the scenario = you want to build, and then we can help you work through the unikernel = components to build.  Are you looking at ARM or x86 for your = POC?

For instance, beginning with just a static = website workload, and building the HTTP proxies to do workload balancing = would be a small but significant start (since it would require building = out the proxy and migration = infrastructure).

-anil

<= div>
On 17 Aug 2014, at 05:27, Thomas Gazagnaire <thomas@gazagnaire.org> = wrote:

Hi,

Which kind of workload are = you trying to run? If it's an OCaml program, yes sure, MirageOS might be = a good option. 

If not, there are other = unikernels: HalVM in Haskell, Erlang-on-Xen, OSv for the JVM, etc... = They are basically all tied to a specific language runtime environment = and they can interoperate between each other and with legacy OS at the = API = level.

Thomas


<= br>

On 16 Aug 2014, at 16:50, Nick Hardiman = <nick@internetmachines.co.uk> wrote:

I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick



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

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

= --Apple-Mail=_DAD04E0C-DC62-4ECA-8084-1BF3403AF7B4-- --===============3325074322244094116== 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 --===============3325074322244094116==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 11:56:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 11:56: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 1XIz4c-0005Jr-Dp; Sun, 17 Aug 2014 11:56:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIz4b-0005Jm-EG for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 11:56:33 +0000 Received: from [193.109.254.147:10281] by server-5.bemta-14.messagelabs.com id F1/9C-28255-07890F35; Sun, 17 Aug 2014 11:56:32 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1408276591!12862677!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19356 invoked from network); 17 Aug 2014 11:56:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-27.messagelabs.com with SMTP; 17 Aug 2014 11:56:31 -0000 Received: (qmail 24116 invoked by uid 634); 17 Aug 2014 11:56:31 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-2-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.2) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 12:56:30 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1408038499.24611.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Sun, 17 Aug 2014 06:56:29 -0500 Message-Id: <0D226750-A585-4F86-88CE-1BCC69A22693@recoil.org> References: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> <1408038499.24611.YahooMailNeo@web172003.mail.ir2.yahoo.com> To: Tom Brown 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] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org That's still be abstract, annoyingly. The best solution to this is definitely to add 'with sexp' annotations to all the type definitions in mirage-types for v2. I've got a changeset to do that, and it's a better solution than 'string_of' since it permits more complex id types (such as records or config tuples) to be represented in a more structured form than just a flat string. -anil On 14 Aug 2014, at 12:48, Tom Brown wrote: > I am using that within the main module, and to print out device id. Printing out (N.id dev) results in error "Error: This expression has type N.id but an expression was expected of type string". > As you also mentioned, the problem is that type id is abstract. > > > On Thursday, 14 August 2014, 16:32, Anil Madhavapeddy wrote: > > > On 14 Aug 2014, at 17:22, Tom Brown wrote: > > > > It looks that function string_of_id in netif, which returns network interface id as a string, doesn't exists any more (the same as id_of_string). any suggestion please? > > > What context are you trying to use this in? mirage-net-unix/xen just expose the type id=string; > > include V1.NETWORK > with type 'a io = 'a Lwt.t > and type page_aligned_buffer = Io_page.t > and type buffer = Cstruct.t > and type id = string > and type macaddr = Macaddr.t > > Are you trying to use it within a JOB functor, where it's still abstract? I'm plumbing through sexpr conversion functions for that usecase -- or do you specifically need string for something? > > -anil > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 11:56:39 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 11:56: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 1XIz4c-0005Jr-Dp; Sun, 17 Aug 2014 11:56:34 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XIz4b-0005Jm-EG for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 11:56:33 +0000 Received: from [193.109.254.147:10281] by server-5.bemta-14.messagelabs.com id F1/9C-28255-07890F35; Sun, 17 Aug 2014 11:56:32 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-27.messagelabs.com!1408276591!12862677!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19356 invoked from network); 17 Aug 2014 11:56:31 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-27.messagelabs.com with SMTP; 17 Aug 2014 11:56:31 -0000 Received: (qmail 24116 invoked by uid 634); 17 Aug 2014 11:56:31 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-2-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.2) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 12:56:30 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1408038499.24611.YahooMailNeo@web172003.mail.ir2.yahoo.com> Date: Sun, 17 Aug 2014 06:56:29 -0500 Message-Id: <0D226750-A585-4F86-88CE-1BCC69A22693@recoil.org> References: <1408033324.49238.YahooMailNeo@web172001.mail.ir2.yahoo.com> <091D0189-1CF5-4B7F-9C07-060C316B3C82@recoil.org> <1408038499.24611.YahooMailNeo@web172003.mail.ir2.yahoo.com> To: Tom Brown 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] string_of_id for netif X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org That's still be abstract, annoyingly. The best solution to this is definitely to add 'with sexp' annotations to all the type definitions in mirage-types for v2. I've got a changeset to do that, and it's a better solution than 'string_of' since it permits more complex id types (such as records or config tuples) to be represented in a more structured form than just a flat string. -anil On 14 Aug 2014, at 12:48, Tom Brown wrote: > I am using that within the main module, and to print out device id. Printing out (N.id dev) results in error "Error: This expression has type N.id but an expression was expected of type string". > As you also mentioned, the problem is that type id is abstract. > > > On Thursday, 14 August 2014, 16:32, Anil Madhavapeddy wrote: > > > On 14 Aug 2014, at 17:22, Tom Brown wrote: > > > > It looks that function string_of_id in netif, which returns network interface id as a string, doesn't exists any more (the same as id_of_string). any suggestion please? > > > What context are you trying to use this in? mirage-net-unix/xen just expose the type id=string; > > include V1.NETWORK > with type 'a io = 'a Lwt.t > and type page_aligned_buffer = Io_page.t > and type buffer = Cstruct.t > and type id = string > and type macaddr = Macaddr.t > > Are you trying to use it within a JOB functor, where it's still abstract? I'm plumbing through sexpr conversion functions for that usecase -- or do you specifically need string for something? > > -anil > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:01:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:01: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 1XJ2tx-0007Bt-1N; Sun, 17 Aug 2014 16:01:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ2tv-0007Bo-AU for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:01:47 +0000 Received: from [193.109.254.147:53116] by server-12.bemta-14.messagelabs.com id BB/3D-23840-AE1D0F35; Sun, 17 Aug 2014 16:01:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1408291305!12931357!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6341 invoked from network); 17 Aug 2014 16:01:45 -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; 17 Aug 2014 16:01:45 -0000 Received: (qmail 10638 invoked by uid 634); 17 Aug 2014 16:01: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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 17:01:44 +0100 From: Anil Madhavapeddy Message-Id: Date: Sun, 17 Aug 2014 11:01:44 -0500 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) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. Slides here: http://decks.openmirage.org/xendevsummit14#/ Repo: https://github.com/mirage/mirage-decks as usual Feedback most welcome before tomorrow, or else I'll spend the rest of the day wandering Chicago's museums^H^H^Hfinishing the Conduit patches! cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:01:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:01: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 1XJ2tx-0007Bt-1N; Sun, 17 Aug 2014 16:01:49 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ2tv-0007Bo-AU for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:01:47 +0000 Received: from [193.109.254.147:53116] by server-12.bemta-14.messagelabs.com id BB/3D-23840-AE1D0F35; Sun, 17 Aug 2014 16:01:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-27.messagelabs.com!1408291305!12931357!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6341 invoked from network); 17 Aug 2014 16:01:45 -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; 17 Aug 2014 16:01:45 -0000 Received: (qmail 10638 invoked by uid 634); 17 Aug 2014 16:01: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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 17:01:44 +0100 From: Anil Madhavapeddy Message-Id: Date: Sun, 17 Aug 2014 11:01:44 -0500 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) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. Slides here: http://decks.openmirage.org/xendevsummit14#/ Repo: https://github.com/mirage/mirage-decks as usual Feedback most welcome before tomorrow, or else I'll spend the rest of the day wandering Chicago's museums^H^H^Hfinishing the Conduit patches! cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:28:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:28: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 1XJ3Jm-0007Jz-Ck; Sun, 17 Aug 2014 16:28:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Jl-0007Ju-4I for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:28:29 +0000 Received: from [85.158.137.68:10169] by server-2.bemta-3.messagelabs.com id 84/03-09149-C28D0F35; Sun, 17 Aug 2014 16:28:28 +0000 X-Env-Sender: nick@internetmachines.co.uk X-Msg-Ref: server-13.tower-31.messagelabs.com!1408292906!14159447!1 X-Originating-IP: [213.138.108.180] 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 27198 invoked from network); 17 Aug 2014 16:28:26 -0000 Received: from adm02.default.planetlarg.uk0.bigv.io (HELO mail.localhost) (213.138.108.180) by server-13.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Aug 2014 16:28:26 -0000 Received: by mail.localhost (Postfix, from userid 2001) id DE63A4C168; Sun, 17 Aug 2014 16:28:25 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on adm02.default.planetlarg.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.2 Received: from [10.0.1.42] (unknown [62.254.230.80]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localhost (Postfix) with ESMTPSA id 538F34C150 for ; Sun, 17 Aug 2014 16:28:23 +0000 (UTC) From: Nick Hardiman Message-Id: <01175592-5E4A-43B3-8DAA-ED5C221A200D@internetmachines.co.uk> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Date: Sun, 17 Aug 2014 17:28:21 +0100 References: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> To: mirageos-devel@lists.xenproject.org In-Reply-To: X-Mailer: Apple Mail (2.1878.6) Subject: Re: [MirageOS-devel] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2343807304685069695==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2343807304685069695== Content-Type: multipart/signed; boundary="Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413"; protocol="application/pgp-signature"; micalg=pgp-sha1 --Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413 Content-Type: multipart/alternative; boundary="Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB" --Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii What I want to do first is basically a portability experiment. I've done = nothing hands-on yet so my apologies for sounding like an idiot. Can = this be done?=20 1 - Create a workload.=20 A web service is good, but anything that I can test both locally and in = the cloud will do. Is something ready-rolled on OPAM? 2 - Move the workload from a personal device to the cloud.=20 I don't want to use configuration management tools. I want to move the = local software stack to a remote provider.=20 * local architecture - cubiboard=20 * remote architecture - AWS I see work has been done here, but I'm not sure how much Xen homogenizes = the platforms.=20 3 - Automate the process.=20 Build an orchestrator into the workload (so the workload transfers = itself) or into a privileged space that can see the workload. If this is OK, I can move onto next steps. A while ago I experimented with a Dreamplug and a LAMP stack. The = journey was littered with device driver issues. The end result was slow = and not portable. Many thanks, Nick On 17 Aug 2014, at 12:24, Anil Madhavapeddy wrote: > Yeah, if the workloads are fairly self-contained, unikernels are = great. It gets more interesting when they form a distributed system, = since a group of unikernels may need to be migrated as a group. >=20 > I'd suggest starting by outlining the scenario you want to build, and = then we can help you work through the unikernel components to build. = Are you looking at ARM or x86 for your POC? >=20 > For instance, beginning with just a static website workload, and = building the HTTP proxies to do workload balancing would be a small but = significant start (since it would require building out the proxy and = migration infrastructure). >=20 > -anil >=20 > On 17 Aug 2014, at 05:27, Thomas Gazagnaire = wrote: >=20 >> Hi, >>=20 >> Which kind of workload are you trying to run? If it's an OCaml = program, yes sure, MirageOS might be a good option.=20 >>=20 >> If not, there are other unikernels: HalVM in Haskell, Erlang-on-Xen, = OSv for the JVM, etc... They are basically all tied to a specific = language runtime environment and they can interoperate between each = other and with legacy OS at the API level. >>=20 >> Thomas >>=20 >>=20 >>=20 >>=20 >> On 16 Aug 2014, at 16:50, Nick Hardiman = wrote: >>=20 >>> I have been trying to come up with an easy way to move workloads = around. This is for a home lab POC, not for a commercial application. >>>=20 >>> I think an OpenMirage unikernel might work well as a workload = container (container as in 'a package of stuff', not as in 'Docker'). = However, before I burn evenings and weekends going off in the wrong = direction (done that plenty), I'd like to get some expert criticism = first.=20 >>>=20 >>> How would I present the high level idea, and how would I get advice = on how to use work done so far on OpenMirage? >>>=20 >>> Many thanks,=20 >>> Nick >>>=20 >>>=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 >=20 --Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
What I want to do first is basically a = portability experiment. I've done nothing hands-on yet so my apologies = for sounding like an idiot. Can this be done? 

1 - Create a workload. 
A web service is good, but anything that I = can test both locally and in the cloud will do. Is something = ready-rolled on OPAM?
2 - Move = the workload from a personal device to the cloud. 
I don't want to use configuration = management tools. I want to move the local software stack to a remote = provider. 
* local = architecture - cubiboard 
* = remote architecture - AWS
I see = work has been done here, but I'm not sure how much Xen homogenizes the = platforms. 
3 - Automate = the process. 
Build an = orchestrator into the workload (so the workload transfers itself) or = into a privileged space that can see the workload.

If this is OK, I can move onto next = steps.

A while ago I experimented with a = Dreamplug and a LAMP stack. The journey was littered with device driver = issues. The end result was slow and not portable.


Many thanks,
Nick




On 17 Aug 2014, at 12:24, Anil Madhavapeddy <anil@recoil.org> wrote:

Yeah, if the workloads are = fairly self-contained, unikernels are great.  It gets more = interesting when they form a distributed system, since a group of = unikernels may need to be migrated as a group.

I'd = suggest starting by outlining the scenario you want to build, and then = we can help you work through the unikernel components to build. =  Are you looking at ARM or x86 for your = POC?

For instance, beginning with just a static = website workload, and building the HTTP proxies to do workload balancing = would be a small but significant start (since it would require building = out the proxy and migration = infrastructure).

-anil

<= div>
On 17 Aug 2014, at 05:27, Thomas Gazagnaire <thomas@gazagnaire.org> = wrote:

Hi,

Which kind of workload are = you trying to run? If it's an OCaml program, yes sure, MirageOS might be = a good option. 

If not, there are other = unikernels: HalVM in Haskell, Erlang-on-Xen, OSv for the JVM, etc... = They are basically all tied to a specific language runtime environment = and they can interoperate between each other and with legacy OS at the = API = level.

Thomas


<= br>

On 16 Aug 2014, at 16:50, Nick Hardiman = <nick@internetmachines.co.uk> wrote:

I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick



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

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


= --Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB-- --Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413 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 - http://gpgtools.org iQEcBAEBAgAGBQJT8NglAAoJEEpTXxTuqGWVRZsH/1R4ZTUJlzB2aTYaVzesXbwb dz54/WLAUpnaHpVkTlHWKOfOvHpE70iRr2CbUAlqPzWAp4+Hrljut6KfOvz9Drgm Sk7hqMpYm+21Wc8ZRymEUXjpZsEFYyjjXdy7zhsiTr23wAYfhh3mucK7OZATN4HF 4dEoJrSRFcqgvWxz+J+TZPbfnqyCRxS1Y7uBKBoMZKOZCZQ6V8JA7l0bYNo18/Ti WAEtH4+8QPhyOSIaPIXXqAjDHJShFIDrFX2x2b8uFXev0/LIvo6hRYs326T2dJkW c74NZSALOEAAqI0Q2VGj80gMTFy5oVUR2FEhxwnYaE4j4LAzSIsrXnPKRDykFww= =J2RU -----END PGP SIGNATURE----- --Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413-- --===============2343807304685069695== 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 --===============2343807304685069695==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:28:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:28: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 1XJ3Jm-0007Jz-Ck; Sun, 17 Aug 2014 16:28:30 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Jl-0007Ju-4I for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:28:29 +0000 Received: from [85.158.137.68:10169] by server-2.bemta-3.messagelabs.com id 84/03-09149-C28D0F35; Sun, 17 Aug 2014 16:28:28 +0000 X-Env-Sender: nick@internetmachines.co.uk X-Msg-Ref: server-13.tower-31.messagelabs.com!1408292906!14159447!1 X-Originating-IP: [213.138.108.180] 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 27198 invoked from network); 17 Aug 2014 16:28:26 -0000 Received: from adm02.default.planetlarg.uk0.bigv.io (HELO mail.localhost) (213.138.108.180) by server-13.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Aug 2014 16:28:26 -0000 Received: by mail.localhost (Postfix, from userid 2001) id DE63A4C168; Sun, 17 Aug 2014 16:28:25 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on adm02.default.planetlarg.uk0.bigv.io X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham version=3.3.2 Received: from [10.0.1.42] (unknown [62.254.230.80]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localhost (Postfix) with ESMTPSA id 538F34C150 for ; Sun, 17 Aug 2014 16:28:23 +0000 (UTC) From: Nick Hardiman Message-Id: <01175592-5E4A-43B3-8DAA-ED5C221A200D@internetmachines.co.uk> Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Date: Sun, 17 Aug 2014 17:28:21 +0100 References: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> To: mirageos-devel@lists.xenproject.org In-Reply-To: X-Mailer: Apple Mail (2.1878.6) Subject: Re: [MirageOS-devel] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2343807304685069695==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2343807304685069695== Content-Type: multipart/signed; boundary="Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413"; protocol="application/pgp-signature"; micalg=pgp-sha1 --Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413 Content-Type: multipart/alternative; boundary="Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB" --Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii What I want to do first is basically a portability experiment. I've done = nothing hands-on yet so my apologies for sounding like an idiot. Can = this be done?=20 1 - Create a workload.=20 A web service is good, but anything that I can test both locally and in = the cloud will do. Is something ready-rolled on OPAM? 2 - Move the workload from a personal device to the cloud.=20 I don't want to use configuration management tools. I want to move the = local software stack to a remote provider.=20 * local architecture - cubiboard=20 * remote architecture - AWS I see work has been done here, but I'm not sure how much Xen homogenizes = the platforms.=20 3 - Automate the process.=20 Build an orchestrator into the workload (so the workload transfers = itself) or into a privileged space that can see the workload. If this is OK, I can move onto next steps. A while ago I experimented with a Dreamplug and a LAMP stack. The = journey was littered with device driver issues. The end result was slow = and not portable. Many thanks, Nick On 17 Aug 2014, at 12:24, Anil Madhavapeddy wrote: > Yeah, if the workloads are fairly self-contained, unikernels are = great. It gets more interesting when they form a distributed system, = since a group of unikernels may need to be migrated as a group. >=20 > I'd suggest starting by outlining the scenario you want to build, and = then we can help you work through the unikernel components to build. = Are you looking at ARM or x86 for your POC? >=20 > For instance, beginning with just a static website workload, and = building the HTTP proxies to do workload balancing would be a small but = significant start (since it would require building out the proxy and = migration infrastructure). >=20 > -anil >=20 > On 17 Aug 2014, at 05:27, Thomas Gazagnaire = wrote: >=20 >> Hi, >>=20 >> Which kind of workload are you trying to run? If it's an OCaml = program, yes sure, MirageOS might be a good option.=20 >>=20 >> If not, there are other unikernels: HalVM in Haskell, Erlang-on-Xen, = OSv for the JVM, etc... They are basically all tied to a specific = language runtime environment and they can interoperate between each = other and with legacy OS at the API level. >>=20 >> Thomas >>=20 >>=20 >>=20 >>=20 >> On 16 Aug 2014, at 16:50, Nick Hardiman = wrote: >>=20 >>> I have been trying to come up with an easy way to move workloads = around. This is for a home lab POC, not for a commercial application. >>>=20 >>> I think an OpenMirage unikernel might work well as a workload = container (container as in 'a package of stuff', not as in 'Docker'). = However, before I burn evenings and weekends going off in the wrong = direction (done that plenty), I'd like to get some expert criticism = first.=20 >>>=20 >>> How would I present the high level idea, and how would I get advice = on how to use work done so far on OpenMirage? >>>=20 >>> Many thanks,=20 >>> Nick >>>=20 >>>=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 >=20 --Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
What I want to do first is basically a = portability experiment. I've done nothing hands-on yet so my apologies = for sounding like an idiot. Can this be done? 

1 - Create a workload. 
A web service is good, but anything that I = can test both locally and in the cloud will do. Is something = ready-rolled on OPAM?
2 - Move = the workload from a personal device to the cloud. 
I don't want to use configuration = management tools. I want to move the local software stack to a remote = provider. 
* local = architecture - cubiboard 
* = remote architecture - AWS
I see = work has been done here, but I'm not sure how much Xen homogenizes the = platforms. 
3 - Automate = the process. 
Build an = orchestrator into the workload (so the workload transfers itself) or = into a privileged space that can see the workload.

If this is OK, I can move onto next = steps.

A while ago I experimented with a = Dreamplug and a LAMP stack. The journey was littered with device driver = issues. The end result was slow and not portable.


Many thanks,
Nick




On 17 Aug 2014, at 12:24, Anil Madhavapeddy <anil@recoil.org> wrote:

Yeah, if the workloads are = fairly self-contained, unikernels are great.  It gets more = interesting when they form a distributed system, since a group of = unikernels may need to be migrated as a group.

I'd = suggest starting by outlining the scenario you want to build, and then = we can help you work through the unikernel components to build. =  Are you looking at ARM or x86 for your = POC?

For instance, beginning with just a static = website workload, and building the HTTP proxies to do workload balancing = would be a small but significant start (since it would require building = out the proxy and migration = infrastructure).

-anil

<= div>
On 17 Aug 2014, at 05:27, Thomas Gazagnaire <thomas@gazagnaire.org> = wrote:

Hi,

Which kind of workload are = you trying to run? If it's an OCaml program, yes sure, MirageOS might be = a good option. 

If not, there are other = unikernels: HalVM in Haskell, Erlang-on-Xen, OSv for the JVM, etc... = They are basically all tied to a specific language runtime environment = and they can interoperate between each other and with legacy OS at the = API = level.

Thomas


<= br>

On 16 Aug 2014, at 16:50, Nick Hardiman = <nick@internetmachines.co.uk> wrote:

I = have been trying to come up with an easy way to move workloads around. = This is for a home lab POC, not for a commercial = application.

I think an OpenMirage unikernel = might work well as a workload container (container as in 'a package of = stuff', not as in 'Docker'). However, before I burn evenings and = weekends going off in the wrong direction (done that plenty), I'd like = to get some expert criticism first. 

How = would I present the high level idea, and how would I get advice on how = to use work done so far on OpenMirage?

Many thanks, 
Nick



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

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


= --Apple-Mail=_792ADF8E-0769-4CD6-B632-0917C4404FEB-- --Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413 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 - http://gpgtools.org iQEcBAEBAgAGBQJT8NglAAoJEEpTXxTuqGWVRZsH/1R4ZTUJlzB2aTYaVzesXbwb dz54/WLAUpnaHpVkTlHWKOfOvHpE70iRr2CbUAlqPzWAp4+Hrljut6KfOvz9Drgm Sk7hqMpYm+21Wc8ZRymEUXjpZsEFYyjjXdy7zhsiTr23wAYfhh3mucK7OZATN4HF 4dEoJrSRFcqgvWxz+J+TZPbfnqyCRxS1Y7uBKBoMZKOZCZQ6V8JA7l0bYNo18/Ti WAEtH4+8QPhyOSIaPIXXqAjDHJShFIDrFX2x2b8uFXev0/LIvo6hRYs326T2dJkW c74NZSALOEAAqI0Q2VGj80gMTFy5oVUR2FEhxwnYaE4j4LAzSIsrXnPKRDykFww= =J2RU -----END PGP SIGNATURE----- --Apple-Mail=_D3FD6E6E-91FC-494E-9A67-6934E6337413-- --===============2343807304685069695== 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 --===============2343807304685069695==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:36:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:36:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Rd-0007P7-12; Sun, 17 Aug 2014 16:36:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Rb-0007P2-G0 for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:36:35 +0000 Received: from [193.109.254.147:61822] by server-14.bemta-14.messagelabs.com id 88/1E-02763-21AD0F35; Sun, 17 Aug 2014 16:36:34 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-9.tower-27.messagelabs.com!1408293393!12950748!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.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14391 invoked from network); 17 Aug 2014 16:36:33 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Aug 2014 16:36:33 -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]:59441 helo=[192.168.99.66]) 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 1XJ3RZ-0004sJ-k9 (Exim 4.82_3-c0e5623) (return-path ); Sun, 17 Aug 2014 17:36:33 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Sun, 17 Aug 2014 17:36:36 +0100 Message-Id: References: To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Quick comments. Is there supposed to be more on Slide 2.3? http://decks.openmirage.org/xendevsummit14#/2/3 On slide 4.1, you should make the "Irmin to the rescue!" bold (and/or larger). I nearly missed it http://decks.openmirage.org/xendevsummit14#/4/1 Slide 4.2 made me laugh :) Slide 5.1 - as for 4.1 above AC On 17 Aug 2014, at 17:01, Anil Madhavapeddy wrote: > I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. > > Slides here: http://decks.openmirage.org/xendevsummit14#/ > Repo: https://github.com/mirage/mirage-decks as usual > > Feedback most welcome before tomorrow, or else I'll spend the rest of the day wandering Chicago's museums^H^H^Hfinishing the Conduit patches! > > cheers, > Anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:36:37 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:36:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Rd-0007P7-12; Sun, 17 Aug 2014 16:36:37 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Rb-0007P2-G0 for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:36:35 +0000 Received: from [193.109.254.147:61822] by server-14.bemta-14.messagelabs.com id 88/1E-02763-21AD0F35; Sun, 17 Aug 2014 16:36:34 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-9.tower-27.messagelabs.com!1408293393!12950748!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.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14391 invoked from network); 17 Aug 2014 16:36:33 -0000 Received: from ppsw-40.csi.cam.ac.uk (HELO ppsw-40.csi.cam.ac.uk) (131.111.8.140) by server-9.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Aug 2014 16:36:33 -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]:59441 helo=[192.168.99.66]) 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 1XJ3RZ-0004sJ-k9 (Exim 4.82_3-c0e5623) (return-path ); Sun, 17 Aug 2014 17:36:33 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Sun, 17 Aug 2014 17:36:36 +0100 Message-Id: References: To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Quick comments. Is there supposed to be more on Slide 2.3? http://decks.openmirage.org/xendevsummit14#/2/3 On slide 4.1, you should make the "Irmin to the rescue!" bold (and/or larger). I nearly missed it http://decks.openmirage.org/xendevsummit14#/4/1 Slide 4.2 made me laugh :) Slide 5.1 - as for 4.1 above AC On 17 Aug 2014, at 17:01, Anil Madhavapeddy wrote: > I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. > > Slides here: http://decks.openmirage.org/xendevsummit14#/ > Repo: https://github.com/mirage/mirage-decks as usual > > Feedback most welcome before tomorrow, or else I'll spend the rest of the day wandering Chicago's museums^H^H^Hfinishing the Conduit patches! > > cheers, > Anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:39:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:39:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Ui-0007S8-AB; Sun, 17 Aug 2014 16:39:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Ug-0007S3-Fi for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:39:46 +0000 Received: from [193.109.254.147:8299] by server-13.bemta-14.messagelabs.com id 9C/28-19311-1DAD0F35; Sun, 17 Aug 2014 16:39:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1408293583!12977745!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32123 invoked from network); 17 Aug 2014 16:39:43 -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; 17 Aug 2014 16:39:43 -0000 Received: (qmail 5445 invoked by uid 634); 17 Aug 2014 16:39:43 -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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 17:39:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <01175592-5E4A-43B3-8DAA-ED5C221A200D@internetmachines.co.uk> Date: Sun, 17 Aug 2014 11:39:41 -0500 Message-Id: <9A8230AC-A55A-449F-B377-47E2D8D1C4F1@recoil.org> References: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> <01175592-5E4A-43B3-8DAA-ED5C221A200D@internetmachines.co.uk> To: Nick Hardiman X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Magnus Skjegstad , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1753828331715128519==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1753828331715128519== Content-Type: multipart/alternative; boundary="Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA" --Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 17 Aug 2014, at 11:28, Nick Hardiman = wrote: > What I want to do first is basically a portability experiment. I've = done nothing hands-on yet so my apologies for sounding like an idiot. = Can this be done?=20 This is all good exploration -- no question is too basic when it comes = to unikernel deployment (where features you might expect be available = simply aren't because the appropriate library hasn't been constructed = yet -- but can be done so increasingly easily). >=20 > 1 - Create a workload.=20 > A web service is good, but anything that I can test both locally and = in the cloud will do. Is something ready-rolled on OPAM? Two things to check in one are: - the self-hosting websites: `opam install mirage-www` and then checkout = https://github.com/mirage/mirage-www and build it in DHCP/Xen mode (cd = src && DHCP=3D1 mirage configure --xen && make). - read Thomas Leonard's post on gluing a unikernel REST service = together: http://roscidus.com/blog/blog/2014/07/28/my-first-unikernel/ > 2 - Move the workload from a personal device to the cloud.=20 > I don't want to use configuration management tools. I want to move the = local software stack to a remote provider.=20 > * local architecture - cubiboard=20 > * remote architecture - AWS > I see work has been done here, but I'm not sure how much Xen = homogenizes the platforms.=20 There is an interesting thing to do here. There is an automated GitHub = workflow for building x86 unikernels right now; see : - http://openmirage.org/wiki/deploying-via-ci - http://amirchaudhry.com/from-jekyll-to-unikernel-in-fifty-lines/ What these do is to turn the source code repositories into deployment = repositories like: - https://github.com/mirage/mirage-www-deployment (the main website) - https://github.com/mirage/mirage-decks-deployment (the slide decks) You *could* make it such that an ARM Cubie builds an ARM equivalent and = uploads both unikernels to the same deployment repo. Then you just need = some way to spin up both the ARM kernels (locally) and the x86 kernels = (on the cloud) and use a DNS server to redirect you appropriately. Magnus Skjegstad and I are working on the DNS bits for local->remote = redirection. I'll drop a mail here when that's done, but you can just = do it manually through DNS assignment for now. > 3 - Automate the process.=20 > Build an orchestrator into the workload (so the workload transfers = itself) or into a privileged space that can see the workload. >=20 > If this is OK, I can move onto next steps. >=20 > A while ago I experimented with a Dreamplug and a LAMP stack. The = journey was littered with device driver issues. The end result was slow = and not portable. Yeah, here the problem shifts to one of orchestration, which is much = more tractable I think. -anil= --Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
- the self-hosting websites: `opam = install mirage-www` and then checkout https://github.com/mirage/mi= rage-www and build it in DHCP/Xen mode (cd src && DHCP=3D1 = mirage configure --xen && make).
- read Thomas = Leonard's post on gluing a unikernel REST service together: http= ://roscidus.com/blog/blog/2014/07/28/my-first-unikernel/
2 - Move the workload from a personal = device to the cloud. 
I = don't want to use configuration management tools. I want to move the = local software stack to a remote provider. 
* local architecture - = cubiboard 
* remote = architecture - AWS
I see work = has been done here, but I'm not sure how much Xen homogenizes the = platforms. 

There is an = interesting thing to do here.  There is an automated GitHub = workflow for building x86 unikernels right now; see = :
=

What these do is to turn the source code = repositories into deployment repositories like:

You *could* make it such that an ARM = Cubie builds an ARM equivalent and uploads both unikernels to the same = deployment repo.  Then you just need some way to spin up both the = ARM kernels (locally) and the x86 kernels (on the cloud) and use a DNS = server to redirect you appropriately.

Magnus = Skjegstad and I are working on the DNS bits for local->remote = redirection.  I'll drop a mail here when that's done, but you can = just do it manually through DNS assignment for = now.

3 - Automate the process. 
Build an orchestrator into the workload = (so the workload transfers itself) or into a privileged space that can = see the workload.

If this is OK, I can move onto next = steps.

A while ago I experimented with a = Dreamplug and a LAMP stack. The journey was littered with device driver = issues. The end result was slow and not = portable.

Yeah, here the problem = shifts to one of orchestration, which is much more tractable I = think.

-anil
= --Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA-- --===============1753828331715128519== 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 --===============1753828331715128519==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:39:49 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:39:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Ui-0007S8-AB; Sun, 17 Aug 2014 16:39:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Ug-0007S3-Fi for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:39:46 +0000 Received: from [193.109.254.147:8299] by server-13.bemta-14.messagelabs.com id 9C/28-19311-1DAD0F35; Sun, 17 Aug 2014 16:39:45 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1408293583!12977745!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32123 invoked from network); 17 Aug 2014 16:39:43 -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; 17 Aug 2014 16:39:43 -0000 Received: (qmail 5445 invoked by uid 634); 17 Aug 2014 16:39:43 -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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 17:39:42 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <01175592-5E4A-43B3-8DAA-ED5C221A200D@internetmachines.co.uk> Date: Sun, 17 Aug 2014 11:39:41 -0500 Message-Id: <9A8230AC-A55A-449F-B377-47E2D8D1C4F1@recoil.org> References: <9BC37CE4-8A55-4908-9720-F17FF7774365@gazagnaire.org> <01175592-5E4A-43B3-8DAA-ED5C221A200D@internetmachines.co.uk> To: Nick Hardiman X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Magnus Skjegstad , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] getting criticism for a workload idea X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1753828331715128519==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1753828331715128519== Content-Type: multipart/alternative; boundary="Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA" --Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 17 Aug 2014, at 11:28, Nick Hardiman = wrote: > What I want to do first is basically a portability experiment. I've = done nothing hands-on yet so my apologies for sounding like an idiot. = Can this be done?=20 This is all good exploration -- no question is too basic when it comes = to unikernel deployment (where features you might expect be available = simply aren't because the appropriate library hasn't been constructed = yet -- but can be done so increasingly easily). >=20 > 1 - Create a workload.=20 > A web service is good, but anything that I can test both locally and = in the cloud will do. Is something ready-rolled on OPAM? Two things to check in one are: - the self-hosting websites: `opam install mirage-www` and then checkout = https://github.com/mirage/mirage-www and build it in DHCP/Xen mode (cd = src && DHCP=3D1 mirage configure --xen && make). - read Thomas Leonard's post on gluing a unikernel REST service = together: http://roscidus.com/blog/blog/2014/07/28/my-first-unikernel/ > 2 - Move the workload from a personal device to the cloud.=20 > I don't want to use configuration management tools. I want to move the = local software stack to a remote provider.=20 > * local architecture - cubiboard=20 > * remote architecture - AWS > I see work has been done here, but I'm not sure how much Xen = homogenizes the platforms.=20 There is an interesting thing to do here. There is an automated GitHub = workflow for building x86 unikernels right now; see : - http://openmirage.org/wiki/deploying-via-ci - http://amirchaudhry.com/from-jekyll-to-unikernel-in-fifty-lines/ What these do is to turn the source code repositories into deployment = repositories like: - https://github.com/mirage/mirage-www-deployment (the main website) - https://github.com/mirage/mirage-decks-deployment (the slide decks) You *could* make it such that an ARM Cubie builds an ARM equivalent and = uploads both unikernels to the same deployment repo. Then you just need = some way to spin up both the ARM kernels (locally) and the x86 kernels = (on the cloud) and use a DNS server to redirect you appropriately. Magnus Skjegstad and I are working on the DNS bits for local->remote = redirection. I'll drop a mail here when that's done, but you can just = do it manually through DNS assignment for now. > 3 - Automate the process.=20 > Build an orchestrator into the workload (so the workload transfers = itself) or into a privileged space that can see the workload. >=20 > If this is OK, I can move onto next steps. >=20 > A while ago I experimented with a Dreamplug and a LAMP stack. The = journey was littered with device driver issues. The end result was slow = and not portable. Yeah, here the problem shifts to one of orchestration, which is much = more tractable I think. -anil= --Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
- the self-hosting websites: `opam = install mirage-www` and then checkout https://github.com/mirage/mi= rage-www and build it in DHCP/Xen mode (cd src && DHCP=3D1 = mirage configure --xen && make).
- read Thomas = Leonard's post on gluing a unikernel REST service together: http= ://roscidus.com/blog/blog/2014/07/28/my-first-unikernel/
2 - Move the workload from a personal = device to the cloud. 
I = don't want to use configuration management tools. I want to move the = local software stack to a remote provider. 
* local architecture - = cubiboard 
* remote = architecture - AWS
I see work = has been done here, but I'm not sure how much Xen homogenizes the = platforms. 

There is an = interesting thing to do here.  There is an automated GitHub = workflow for building x86 unikernels right now; see = :
=

What these do is to turn the source code = repositories into deployment repositories like:

You *could* make it such that an ARM = Cubie builds an ARM equivalent and uploads both unikernels to the same = deployment repo.  Then you just need some way to spin up both the = ARM kernels (locally) and the x86 kernels (on the cloud) and use a DNS = server to redirect you appropriately.

Magnus = Skjegstad and I are working on the DNS bits for local->remote = redirection.  I'll drop a mail here when that's done, but you can = just do it manually through DNS assignment for = now.

3 - Automate the process. 
Build an orchestrator into the workload = (so the workload transfers itself) or into a privileged space that can = see the workload.

If this is OK, I can move onto next = steps.

A while ago I experimented with a = Dreamplug and a LAMP stack. The journey was littered with device driver = issues. The end result was slow and not = portable.

Yeah, here the problem = shifts to one of orchestration, which is much more tractable I = think.

-anil
= --Apple-Mail=_631EAC9A-D05F-4876-A522-329CAF046BBA-- --===============1753828331715128519== 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 --===============1753828331715128519==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:41:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:41: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 1XJ3Vt-0007Tu-GM; Sun, 17 Aug 2014 16:41:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Vs-0007Tp-1X for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:41:00 +0000 Received: from [193.109.254.147:34585] by server-12.bemta-14.messagelabs.com id D9/85-23840-B1BD0F35; Sun, 17 Aug 2014 16:40:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1408293658!12989219!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16725 invoked from network); 17 Aug 2014 16:40:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 17 Aug 2014 16:40:58 -0000 Received: (qmail 3986 invoked by uid 634); 17 Aug 2014 16:40:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 17:40:58 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 17 Aug 2014 11:40:57 -0500 Message-Id: References: To: Amir M Chaudhry 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] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 11:36, Amir Chaudhry wrote: > Quick comments. > > Is there supposed to be more on Slide 2.3? > http://decks.openmirage.org/xendevsummit14#/2/3 Well there was, but I can't figure out the HTML runes to do two-column in reveal.js, so I just left it there as a summary of the previous points... > On slide 4.1, you should make the "Irmin to the rescue!" bold (and/or larger). I nearly missed it > http://decks.openmirage.org/xendevsummit14#/4/1 > > Slide 4.2 made me laugh :) > > Slide 5.1 - as for 4.1 above thanks -- updated in my local copy; will push later! -a _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 16:41:01 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 16:41: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 1XJ3Vt-0007Tu-GM; Sun, 17 Aug 2014 16:41:01 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ3Vs-0007Tp-1X for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 16:41:00 +0000 Received: from [193.109.254.147:34585] by server-12.bemta-14.messagelabs.com id D9/85-23840-B1BD0F35; Sun, 17 Aug 2014 16:40:59 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1408293658!12989219!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16725 invoked from network); 17 Aug 2014 16:40:58 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 17 Aug 2014 16:40:58 -0000 Received: (qmail 3986 invoked by uid 634); 17 Aug 2014 16:40:58 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 17:40:58 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 17 Aug 2014 11:40:57 -0500 Message-Id: References: To: Amir M Chaudhry 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] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 11:36, Amir Chaudhry wrote: > Quick comments. > > Is there supposed to be more on Slide 2.3? > http://decks.openmirage.org/xendevsummit14#/2/3 Well there was, but I can't figure out the HTML runes to do two-column in reveal.js, so I just left it there as a summary of the previous points... > On slide 4.1, you should make the "Irmin to the rescue!" bold (and/or larger). I nearly missed it > http://decks.openmirage.org/xendevsummit14#/4/1 > > Slide 4.2 made me laugh :) > > Slide 5.1 - as for 4.1 above thanks -- updated in my local copy; will push later! -a _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 17:15:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 17: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 1XJ42q-0007h3-4S; Sun, 17 Aug 2014 17:15:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ42o-0007gy-Jc for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 17:15:02 +0000 Received: from [85.158.143.35:39944] by server-1.bemta-4.messagelabs.com id 4C/32-05872-513E0F35; Sun, 17 Aug 2014 17:15:01 +0000 X-Env-Sender: philtomson@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1408295699!13492761!1 X-Originating-IP: [209.85.213.172] 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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1167 invoked from network); 17 Aug 2014 17:15:00 -0000 Received: from mail-ig0-f172.google.com (HELO mail-ig0-f172.google.com) (209.85.213.172) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 17:15:00 -0000 Received: by mail-ig0-f172.google.com with SMTP id h15so6083380igd.11 for ; Sun, 17 Aug 2014 10:14: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=DXnavL2PQ+9UP9YCnkVtjG4cj0Bt5aTCvVL6fmlquP8=; b=fGLsXyMgbkyLG/WBFnmP+46ilAJqJf27wR/ilIhwqj/8Y55Q4wJrm4zNy6Ub27EwrC jAin4lselwOxVuL6XJHWO6Ab2USub2WXUMng3GcS6wS/3kH7VbNxeCYmtpDCylF8hpTO 3vw8n633f+F0IVgjok2CY5TlArSdzdv7D27MyBne8wo8d18PYwNSUYvM9mp7QdHUw/EU lNCHvH8ZuRTja5ZJvRLcJnGzP+rCl6f1/TrY2EGSngNpzjo/ifNge8CPjsqOhV9v6tVU kV5vhVCbRtFKDCeRnCOw/y4Ry1NBs77TRxCZf68nX4CJxbDtVVDXaImJDTol/ji4JiRM /JMA== MIME-Version: 1.0 X-Received: by 10.50.110.103 with SMTP id hz7mr37037259igb.10.1408295699342; Sun, 17 Aug 2014 10:14:59 -0700 (PDT) Received: by 10.43.111.136 with HTTP; Sun, 17 Aug 2014 10:14:59 -0700 (PDT) Date: Sun, 17 Aug 2014 10:14:59 -0700 Message-ID: From: Phil Tomson To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1374659791347107119==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1374659791347107119== Content-Type: multipart/alternative; boundary=089e01183756e5ee540500d664f3 --089e01183756e5ee540500d664f3 Content-Type: text/plain; charset=UTF-8 I'm interested in Mirage for some embedded applications that interact with the Internet of Things either by http or other protocols (like MQTT or COAP). So for example, let's say I've got a Cubieboard2 and I connect up an A/D board to collect data (temperature, weather data, etc.) and I want to setup an http server using Mirage that would serve up this data. The http part is straightforward. However, how does one interact with the GPIO pins on the Cubieboard? - that seems to be on the "other side of" Xen. So would one need to write some kind of device driver for Xen that interfaces to the Cubieboard's GPIO in order to do this? And if so, how would it be accessed by Mirage? 1. Is it possible? 2. If so, can you point me in the right direction? Phil --089e01183756e5ee540500d664f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm interested in Mirage for some embedded a= pplications that interact with the Internet of Things either by http or oth= er protocols (like MQTT or COAP).

So for example, let's sa= y I've got a Cubieboard2 and I connect up an A/D board to collect data = (temperature, weather data, etc.) and I want to setup an http server using = Mirage that would serve up this data. The http part is straightforward. How= ever, how does one interact with the GPIO pins on the Cubieboard? - that se= ems to be on the "other side of" Xen. So would one need to write = some kind of device driver for Xen that interfaces to the Cubieboard's = GPIO in order to do this? And if so, how would it be accessed by Mirage?
1. Is it possible?
2. If so, can you point me = in the right direction?

Phil
--089e01183756e5ee540500d664f3-- --===============1374659791347107119== 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 --===============1374659791347107119==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 17:15:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 17: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 1XJ42q-0007h3-4S; Sun, 17 Aug 2014 17:15:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ42o-0007gy-Jc for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 17:15:02 +0000 Received: from [85.158.143.35:39944] by server-1.bemta-4.messagelabs.com id 4C/32-05872-513E0F35; Sun, 17 Aug 2014 17:15:01 +0000 X-Env-Sender: philtomson@gmail.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1408295699!13492761!1 X-Originating-IP: [209.85.213.172] 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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1167 invoked from network); 17 Aug 2014 17:15:00 -0000 Received: from mail-ig0-f172.google.com (HELO mail-ig0-f172.google.com) (209.85.213.172) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 17:15:00 -0000 Received: by mail-ig0-f172.google.com with SMTP id h15so6083380igd.11 for ; Sun, 17 Aug 2014 10:14: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=DXnavL2PQ+9UP9YCnkVtjG4cj0Bt5aTCvVL6fmlquP8=; b=fGLsXyMgbkyLG/WBFnmP+46ilAJqJf27wR/ilIhwqj/8Y55Q4wJrm4zNy6Ub27EwrC jAin4lselwOxVuL6XJHWO6Ab2USub2WXUMng3GcS6wS/3kH7VbNxeCYmtpDCylF8hpTO 3vw8n633f+F0IVgjok2CY5TlArSdzdv7D27MyBne8wo8d18PYwNSUYvM9mp7QdHUw/EU lNCHvH8ZuRTja5ZJvRLcJnGzP+rCl6f1/TrY2EGSngNpzjo/ifNge8CPjsqOhV9v6tVU kV5vhVCbRtFKDCeRnCOw/y4Ry1NBs77TRxCZf68nX4CJxbDtVVDXaImJDTol/ji4JiRM /JMA== MIME-Version: 1.0 X-Received: by 10.50.110.103 with SMTP id hz7mr37037259igb.10.1408295699342; Sun, 17 Aug 2014 10:14:59 -0700 (PDT) Received: by 10.43.111.136 with HTTP; Sun, 17 Aug 2014 10:14:59 -0700 (PDT) Date: Sun, 17 Aug 2014 10:14:59 -0700 Message-ID: From: Phil Tomson To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============1374659791347107119==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1374659791347107119== Content-Type: multipart/alternative; boundary=089e01183756e5ee540500d664f3 --089e01183756e5ee540500d664f3 Content-Type: text/plain; charset=UTF-8 I'm interested in Mirage for some embedded applications that interact with the Internet of Things either by http or other protocols (like MQTT or COAP). So for example, let's say I've got a Cubieboard2 and I connect up an A/D board to collect data (temperature, weather data, etc.) and I want to setup an http server using Mirage that would serve up this data. The http part is straightforward. However, how does one interact with the GPIO pins on the Cubieboard? - that seems to be on the "other side of" Xen. So would one need to write some kind of device driver for Xen that interfaces to the Cubieboard's GPIO in order to do this? And if so, how would it be accessed by Mirage? 1. Is it possible? 2. If so, can you point me in the right direction? Phil --089e01183756e5ee540500d664f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm interested in Mirage for some embedded a= pplications that interact with the Internet of Things either by http or oth= er protocols (like MQTT or COAP).

So for example, let's sa= y I've got a Cubieboard2 and I connect up an A/D board to collect data = (temperature, weather data, etc.) and I want to setup an http server using = Mirage that would serve up this data. The http part is straightforward. How= ever, how does one interact with the GPIO pins on the Cubieboard? - that se= ems to be on the "other side of" Xen. So would one need to write = some kind of device driver for Xen that interfaces to the Cubieboard's = GPIO in order to do this? And if so, how would it be accessed by Mirage?
1. Is it possible?
2. If so, can you point me = in the right direction?

Phil
--089e01183756e5ee540500d664f3-- --===============1374659791347107119== 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 --===============1374659791347107119==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 17:18:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 17:18: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 1XJ465-0007jZ-Ji; Sun, 17 Aug 2014 17:18:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ464-0007jU-Ib for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 17:18:24 +0000 Received: from [85.158.139.211:4328] by server-8.bemta-5.messagelabs.com id 7A/42-22440-FD3E0F35; Sun, 17 Aug 2014 17:18:23 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1408295902!11780449!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16054 invoked from network); 17 Aug 2014 17:18:22 -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; 17 Aug 2014 17:18:22 -0000 Received: (qmail 7443 invoked by uid 634); 17 Aug 2014 17:18:22 -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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 18:18:20 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 17 Aug 2014 12:18:19 -0500 Message-Id: References: To: Phil Tomson 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 and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5053728979786401709==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5053728979786401709== Content-Type: multipart/alternative; boundary="Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54" --Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 17 Aug 2014, at 12:14, Phil Tomson wrote: > I'm interested in Mirage for some embedded applications that interact = with the Internet of Things either by http or other protocols (like MQTT = or COAP). >=20 > So for example, let's say I've got a Cubieboard2 and I connect up an = A/D board to collect data (temperature, weather data, etc.) and I want = to setup an http server using Mirage that would serve up this data. The = http part is straightforward. However, how does one interact with the = GPIO pins on the Cubieboard? - that seems to be on the "other side of" = Xen. So would one need to write some kind of device driver for Xen that = interfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?=20 >=20 > 1. Is it possible? > 2. If so, can you point me in the right direction? The GPIO pins would, in the simplest instance, just be accessible from = the Linux running in dom0. After that, you can interface it to a Mirage = VM via 'vchan': http://openmirage.org/blog/update-on-vchan If you're feeling extra-paranoid, it's possible to move the GPIO = handling code into an unprivileged VM, but the first step to do is to = figure out the GPIO/Linux runes in dom0 first. I'd be very interested in seeing how this goes... -anil --Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 17 = Aug 2014, at 12:14, Phil Tomson <philtomson@gmail.com> = wrote:

I'm interested in Mirage for = some embedded applications that interact with the Internet of Things = either by http or other protocols (like MQTT or COAP).

So = for example, let's say I've got a Cubieboard2 and I connect up an A/D = board to collect data (temperature, weather data, etc.) and I want to = setup an http server using Mirage that would serve up this data. The = http part is straightforward. However, how does one interact with the = GPIO pins on the Cubieboard? - that seems to be on the "other side of" = Xen. So would one need to write some kind of device driver for Xen that = interfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?

1. Is it possible?
2. If so, can you point = me in the right = direction?

The GPIO pins = would, in the simplest instance, just be accessible from the Linux = running in dom0.  After that, you can interface it to a Mirage VM = via 'vchan': http://openmirage.org/= blog/update-on-vchan

If you're feeling = extra-paranoid, it's possible to move the GPIO handling code into an = unprivileged VM, but the first step to do is to figure out the = GPIO/Linux runes in dom0 first.

I'd be very = interested in seeing how this = goes...

-anil

= --Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54-- --===============5053728979786401709== 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 --===============5053728979786401709==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 17:18:25 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 17:18: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 1XJ465-0007jZ-Ji; Sun, 17 Aug 2014 17:18:25 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ464-0007jU-Ib for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 17:18:24 +0000 Received: from [85.158.139.211:4328] by server-8.bemta-5.messagelabs.com id 7A/42-22440-FD3E0F35; Sun, 17 Aug 2014 17:18:23 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1408295902!11780449!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16054 invoked from network); 17 Aug 2014 17:18:22 -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; 17 Aug 2014 17:18:22 -0000 Received: (qmail 7443 invoked by uid 634); 17 Aug 2014 17:18:22 -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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 17 Aug 2014 18:18:20 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Sun, 17 Aug 2014 12:18:19 -0500 Message-Id: References: To: Phil Tomson 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 and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============5053728979786401709==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============5053728979786401709== Content-Type: multipart/alternative; boundary="Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54" --Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 17 Aug 2014, at 12:14, Phil Tomson wrote: > I'm interested in Mirage for some embedded applications that interact = with the Internet of Things either by http or other protocols (like MQTT = or COAP). >=20 > So for example, let's say I've got a Cubieboard2 and I connect up an = A/D board to collect data (temperature, weather data, etc.) and I want = to setup an http server using Mirage that would serve up this data. The = http part is straightforward. However, how does one interact with the = GPIO pins on the Cubieboard? - that seems to be on the "other side of" = Xen. So would one need to write some kind of device driver for Xen that = interfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?=20 >=20 > 1. Is it possible? > 2. If so, can you point me in the right direction? The GPIO pins would, in the simplest instance, just be accessible from = the Linux running in dom0. After that, you can interface it to a Mirage = VM via 'vchan': http://openmirage.org/blog/update-on-vchan If you're feeling extra-paranoid, it's possible to move the GPIO = handling code into an unprivileged VM, but the first step to do is to = figure out the GPIO/Linux runes in dom0 first. I'd be very interested in seeing how this goes... -anil --Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii On 17 = Aug 2014, at 12:14, Phil Tomson <philtomson@gmail.com> = wrote:

I'm interested in Mirage for = some embedded applications that interact with the Internet of Things = either by http or other protocols (like MQTT or COAP).

So = for example, let's say I've got a Cubieboard2 and I connect up an A/D = board to collect data (temperature, weather data, etc.) and I want to = setup an http server using Mirage that would serve up this data. The = http part is straightforward. However, how does one interact with the = GPIO pins on the Cubieboard? - that seems to be on the "other side of" = Xen. So would one need to write some kind of device driver for Xen that = interfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?

1. Is it possible?
2. If so, can you point = me in the right = direction?

The GPIO pins = would, in the simplest instance, just be accessible from the Linux = running in dom0.  After that, you can interface it to a Mirage VM = via 'vchan': http://openmirage.org/= blog/update-on-vchan

If you're feeling = extra-paranoid, it's possible to move the GPIO handling code into an = unprivileged VM, but the first step to do is to figure out the = GPIO/Linux runes in dom0 first.

I'd be very = interested in seeing how this = goes...

-anil

= --Apple-Mail=_DBA0DC26-5EBB-489D-AC3C-5DDFDD32CF54-- --===============5053728979786401709== 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 --===============5053728979786401709==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 17:35:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 17:35: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 1XJ4Mb-0007s0-03; Sun, 17 Aug 2014 17:35:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ4MZ-0007rv-Lm for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 17:35:27 +0000 Received: from [193.109.254.147:10589] by server-9.bemta-14.messagelabs.com id B4/72-31535-FD7E0F35; Sun, 17 Aug 2014 17:35:27 +0000 X-Env-Sender: philtomson@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1408296924!12975416!1 X-Originating-IP: [209.85.213.177] 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.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19194 invoked from network); 17 Aug 2014 17:35:25 -0000 Received: from mail-ig0-f177.google.com (HELO mail-ig0-f177.google.com) (209.85.213.177) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 17:35:25 -0000 Received: by mail-ig0-f177.google.com with SMTP id hn18so5848279igb.4 for ; Sun, 17 Aug 2014 10:35: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 :content-type; bh=Jpx0Vp50+2kCjC4GAiQBH1jFjIr1YaIcN0n2NVl9aOE=; b=CQ1Qrg4Y0dzs98kdv/iS687Dlzaf34zwlNAXsOMadQlwcK1NUhP9YBwDRrP8bcjgz5 PaXOUJaeBV9nfl4o1T+Yo72ft45gxQxcBmR+zTqQgI0kBggyQuiRcMbfIeP+lRyt3BXa iSDzpqEHXi+lwhZhPoXgeU0vpJ6HUBN+iCzv/KFS9u9yt7gIHVncp7zJ5b49T8a1Mz4q MFM4WIG0CMtrFYaMSpFWNoh3aWxxB2JdnRziJjDUGgD06Ql4lCLWmxUxCYpcv0P2eagh OLr4eFxO6pimj8o4lQ5HPxXp9+TQZkDLtQ7iCqFBMemNNE5Uvqp79shsyqMaVLTVC1WE VLPA== MIME-Version: 1.0 X-Received: by 10.50.108.103 with SMTP id hj7mr74573505igb.5.1408296924007; Sun, 17 Aug 2014 10:35:24 -0700 (PDT) Received: by 10.43.111.136 with HTTP; Sun, 17 Aug 2014 10:35:23 -0700 (PDT) In-Reply-To: References: Date: Sun, 17 Aug 2014 10:35:23 -0700 Message-ID: From: Phil Tomson To: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6548734411991394967==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6548734411991394967== Content-Type: multipart/alternative; boundary=089e0149bf94e4d53c0500d6adc3 --089e0149bf94e4d53c0500d6adc3 Content-Type: text/plain; charset=UTF-8 I'm very much a Xen newbie - ok, maybe not even that far along - so I hope this question isn't completely uninformed... Do you have to have Linux running in dom0? Could it be a much simpler OS that basically just allows access to GPIO without a lot of other overhead? Maybe I should back up a step: Is there always a Linux OS running in dom0 when you're running Mirage on a Cubieboard (as in your OSCON demo for example)? Also, a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain "A driver domain is unprivileged Xen domain that has been given responsibility for a particular piece of hardware. It runs a minimal kernel with only that hardware driver and the backend driver for that device class. Thus, if the hardware driver fails, the other domains (including Dom0) will survive and, when the driver domain is restarted, will be able to use the hardware again" When they say "minimal kernel" there does that imply a Linux kernel? Phil On Sun, Aug 17, 2014 at 10:18 AM, Anil Madhavapeddy wrote: > On 17 Aug 2014, at 12:14, Phil Tomson wrote: > > I'm interested in Mirage for some embedded applications that interact with > the Internet of Things either by http or other protocols (like MQTT or > COAP). > > So for example, let's say I've got a Cubieboard2 and I connect up an A/D > board to collect data (temperature, weather data, etc.) and I want to setup > an http server using Mirage that would serve up this data. The http part is > straightforward. However, how does one interact with the GPIO pins on the > Cubieboard? - that seems to be on the "other side of" Xen. So would one > need to write some kind of device driver for Xen that interfaces to the > Cubieboard's GPIO in order to do this? And if so, how would it be accessed > by Mirage? > > 1. Is it possible? > 2. If so, can you point me in the right direction? > > > The GPIO pins would, in the simplest instance, just be accessible from the > Linux running in dom0. After that, you can interface it to a Mirage VM via > 'vchan': http://openmirage.org/blog/update-on-vchan > > If you're feeling extra-paranoid, it's possible to move the GPIO handling > code into an unprivileged VM, but the first step to do is to figure out the > GPIO/Linux runes in dom0 first. > > I'd be very interested in seeing how this goes... > > -anil > > --089e0149bf94e4d53c0500d6adc3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm very much a Xen newbie - ok, maybe not e= ven that far along - so I hope this question isn't completely uninforme= d...

Do you have to have Linux running in dom0? Could it be a = much simpler OS=C2=A0 that basically just allows access to GPIO without a l= ot of other overhead? Maybe I should back up a step: Is there always a Linu= x OS running in dom0 when you're running Mirage on a Cubieboard (as in = your OSCON demo for example)?

Also, a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain
"= ;A driver domain is unprivileged Xen domain that has been given=20 responsibility for a particular piece of hardware. It runs a minimal=20 kernel with only that hardware driver and the backend driver for that=20 device class. Thus, if the hardware driver fails, the other domains=20 (including Dom0) will survive and, when the driver domain is restarted,=20 will be able to use the hardware again"

W= hen they say "minimal kernel" there does that imply a Linux kerne= l?

Phil


On Sun, Aug 17, 2014 at 10:18 AM, Anil Madhavapeddy <= span dir=3D"ltr"><a= nil@recoil.org> wrote:
On 17 Aug 2014, at 12:14, Phil Tomson <philtomson@gmail.com> wrote:=

I'm inter= ested in Mirage for some embedded applications that interact with the Inter= net of Things either by http or other protocols (like MQTT or COAP).
So for example, let's say I've got a Cubieboard2 and I connec= t up an A/D board to collect data (temperature, weather data, etc.) and I w= ant to setup an http server using Mirage that would serve up this data. The= http part is straightforward. However, how does one interact with the GPIO= pins on the Cubieboard? - that seems to be on the "other side of"= ; Xen. So would one need to write some kind of device driver for Xen that i= nterfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?

1. Is it possible?
2. If so, can you point me = in the right direction?

<= div>The GPIO pins would, in the simplest instance, just be accessible from = the Linux running in dom0. =C2=A0After that, you can interface it to a Mira= ge VM via 'vchan':=C2=A0http://openmirage.org/blog/update-on-vchan

If you're feeling extra-paranoid, it's possible= to move the GPIO handling code into an unprivileged VM, but the first step= to do is to figure out the GPIO/Linux runes in dom0 first.

I'd be very interested in seeing how this goes...

-anil

--089e0149bf94e4d53c0500d6adc3-- --===============6548734411991394967== 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 --===============6548734411991394967==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 17:35:30 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 17:35: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 1XJ4Mb-0007s0-03; Sun, 17 Aug 2014 17:35:29 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJ4MZ-0007rv-Lm for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 17:35:27 +0000 Received: from [193.109.254.147:10589] by server-9.bemta-14.messagelabs.com id B4/72-31535-FD7E0F35; Sun, 17 Aug 2014 17:35:27 +0000 X-Env-Sender: philtomson@gmail.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1408296924!12975416!1 X-Originating-IP: [209.85.213.177] 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.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19194 invoked from network); 17 Aug 2014 17:35:25 -0000 Received: from mail-ig0-f177.google.com (HELO mail-ig0-f177.google.com) (209.85.213.177) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 17:35:25 -0000 Received: by mail-ig0-f177.google.com with SMTP id hn18so5848279igb.4 for ; Sun, 17 Aug 2014 10:35: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 :content-type; bh=Jpx0Vp50+2kCjC4GAiQBH1jFjIr1YaIcN0n2NVl9aOE=; b=CQ1Qrg4Y0dzs98kdv/iS687Dlzaf34zwlNAXsOMadQlwcK1NUhP9YBwDRrP8bcjgz5 PaXOUJaeBV9nfl4o1T+Yo72ft45gxQxcBmR+zTqQgI0kBggyQuiRcMbfIeP+lRyt3BXa iSDzpqEHXi+lwhZhPoXgeU0vpJ6HUBN+iCzv/KFS9u9yt7gIHVncp7zJ5b49T8a1Mz4q MFM4WIG0CMtrFYaMSpFWNoh3aWxxB2JdnRziJjDUGgD06Ql4lCLWmxUxCYpcv0P2eagh OLr4eFxO6pimj8o4lQ5HPxXp9+TQZkDLtQ7iCqFBMemNNE5Uvqp79shsyqMaVLTVC1WE VLPA== MIME-Version: 1.0 X-Received: by 10.50.108.103 with SMTP id hj7mr74573505igb.5.1408296924007; Sun, 17 Aug 2014 10:35:24 -0700 (PDT) Received: by 10.43.111.136 with HTTP; Sun, 17 Aug 2014 10:35:23 -0700 (PDT) In-Reply-To: References: Date: Sun, 17 Aug 2014 10:35:23 -0700 Message-ID: From: Phil Tomson To: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============6548734411991394967==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6548734411991394967== Content-Type: multipart/alternative; boundary=089e0149bf94e4d53c0500d6adc3 --089e0149bf94e4d53c0500d6adc3 Content-Type: text/plain; charset=UTF-8 I'm very much a Xen newbie - ok, maybe not even that far along - so I hope this question isn't completely uninformed... Do you have to have Linux running in dom0? Could it be a much simpler OS that basically just allows access to GPIO without a lot of other overhead? Maybe I should back up a step: Is there always a Linux OS running in dom0 when you're running Mirage on a Cubieboard (as in your OSCON demo for example)? Also, a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain "A driver domain is unprivileged Xen domain that has been given responsibility for a particular piece of hardware. It runs a minimal kernel with only that hardware driver and the backend driver for that device class. Thus, if the hardware driver fails, the other domains (including Dom0) will survive and, when the driver domain is restarted, will be able to use the hardware again" When they say "minimal kernel" there does that imply a Linux kernel? Phil On Sun, Aug 17, 2014 at 10:18 AM, Anil Madhavapeddy wrote: > On 17 Aug 2014, at 12:14, Phil Tomson wrote: > > I'm interested in Mirage for some embedded applications that interact with > the Internet of Things either by http or other protocols (like MQTT or > COAP). > > So for example, let's say I've got a Cubieboard2 and I connect up an A/D > board to collect data (temperature, weather data, etc.) and I want to setup > an http server using Mirage that would serve up this data. The http part is > straightforward. However, how does one interact with the GPIO pins on the > Cubieboard? - that seems to be on the "other side of" Xen. So would one > need to write some kind of device driver for Xen that interfaces to the > Cubieboard's GPIO in order to do this? And if so, how would it be accessed > by Mirage? > > 1. Is it possible? > 2. If so, can you point me in the right direction? > > > The GPIO pins would, in the simplest instance, just be accessible from the > Linux running in dom0. After that, you can interface it to a Mirage VM via > 'vchan': http://openmirage.org/blog/update-on-vchan > > If you're feeling extra-paranoid, it's possible to move the GPIO handling > code into an unprivileged VM, but the first step to do is to figure out the > GPIO/Linux runes in dom0 first. > > I'd be very interested in seeing how this goes... > > -anil > > --089e0149bf94e4d53c0500d6adc3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm very much a Xen newbie - ok, maybe not e= ven that far along - so I hope this question isn't completely uninforme= d...

Do you have to have Linux running in dom0? Could it be a = much simpler OS=C2=A0 that basically just allows access to GPIO without a l= ot of other overhead? Maybe I should back up a step: Is there always a Linu= x OS running in dom0 when you're running Mirage on a Cubieboard (as in = your OSCON demo for example)?

Also, a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain
"= ;A driver domain is unprivileged Xen domain that has been given=20 responsibility for a particular piece of hardware. It runs a minimal=20 kernel with only that hardware driver and the backend driver for that=20 device class. Thus, if the hardware driver fails, the other domains=20 (including Dom0) will survive and, when the driver domain is restarted,=20 will be able to use the hardware again"

W= hen they say "minimal kernel" there does that imply a Linux kerne= l?

Phil


On Sun, Aug 17, 2014 at 10:18 AM, Anil Madhavapeddy <= span dir=3D"ltr"><a= nil@recoil.org> wrote:
On 17 Aug 2014, at 12:14, Phil Tomson <philtomson@gmail.com> wrote:=

I'm inter= ested in Mirage for some embedded applications that interact with the Inter= net of Things either by http or other protocols (like MQTT or COAP).
So for example, let's say I've got a Cubieboard2 and I connec= t up an A/D board to collect data (temperature, weather data, etc.) and I w= ant to setup an http server using Mirage that would serve up this data. The= http part is straightforward. However, how does one interact with the GPIO= pins on the Cubieboard? - that seems to be on the "other side of"= ; Xen. So would one need to write some kind of device driver for Xen that i= nterfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?

1. Is it possible?
2. If so, can you point me = in the right direction?

<= div>The GPIO pins would, in the simplest instance, just be accessible from = the Linux running in dom0. =C2=A0After that, you can interface it to a Mira= ge VM via 'vchan':=C2=A0http://openmirage.org/blog/update-on-vchan

If you're feeling extra-paranoid, it's possible= to move the GPIO handling code into an unprivileged VM, but the first step= to do is to figure out the GPIO/Linux runes in dom0 first.

I'd be very interested in seeing how this goes...

-anil

--089e0149bf94e4d53c0500d6adc3-- --===============6548734411991394967== 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 --===============6548734411991394967==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 18:10:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 18:10: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 1XJ4us-00089b-8Z; Sun, 17 Aug 2014 18: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 1XJ4uq-00089Q-3R for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 18:10:52 +0000 Received: from [85.158.137.68:17462] by server-12.bemta-3.messagelabs.com id 18/D5-02460-B20F0F35; Sun, 17 Aug 2014 18:10:51 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1408299048!10395381!1 X-Originating-IP: [209.85.192.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 26516 invoked from network); 17 Aug 2014 18:10:49 -0000 Received: from mail-pd0-f173.google.com (HELO mail-pd0-f173.google.com) (209.85.192.173) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 18:10:49 -0000 Received: by mail-pd0-f173.google.com with SMTP id w10so6007018pde.18 for ; Sun, 17 Aug 2014 11:10:46 -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=Qk6Xuh4mcodk5jyJpcGAj1p++M4qZuYCbG2VtJDTj8k=; b=owKwXeovJ3bo9e4mB6ouZlh9Ln0rDhf0Gz8A3RE0+ln+tR0T00pEiOWzuwqDmENsCQ jsehBoa9TiIlP+FXMrwjbT0YK0OeFA1HdTP6KipbPBJoAmcBYZC2hp00WvfpTOA8YE2c KhuXNN/NmIoKylmUSAz8ltcnZ2LVE+jjpzPaHMkGYRqDumbspurRAWIWf1U0zqNK2Pjx GURyQuXOWVbeQsWtb+8iD18iTm2yDMSyPJ80Im7HdwLFgNXLTxQawNAXA2iqaO4VJZdv rCdDIM2C4Sgwbay7A48Yg+WuUCJxttzPqGpLhrxfw6WfrIOHFo0XMqiEy/GkD2GebHJF dL5w== MIME-Version: 1.0 X-Received: by 10.66.155.167 with SMTP id vx7mr5218018pab.141.1408299045841; Sun, 17 Aug 2014 11:10:45 -0700 (PDT) Received: by 10.70.65.101 with HTTP; Sun, 17 Aug 2014 11:10:45 -0700 (PDT) In-Reply-To: References: Date: Sun, 17 Aug 2014 19:10:45 +0100 Message-ID: From: David Scott To: Phil Tomson Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2899157289937671840==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2899157289937671840== Content-Type: multipart/alternative; boundary=047d7b6dc3705d71ca0500d72cb1 --047d7b6dc3705d71ca0500d72cb1 Content-Type: text/plain; charset=UTF-8 On Sun, Aug 17, 2014 at 6:35 PM, Phil Tomson wrote: > I'm very much a Xen newbie - ok, maybe not even that far along - so I hope > this question isn't completely uninformed... > > Do you have to have Linux running in dom0? Could it be a much simpler OS > that basically just allows access to GPIO without a lot of other overhead? > Maybe I should back up a step: Is there always a Linux OS running in dom0 > when you're running Mirage on a Cubieboard (as in your OSCON demo for > example)? > On a Xen host, there's always something in dom0. Xen doesn't care what OS is running in dom0, but only certain OSes have the necessary Xen dom0 support available. Linux's Xen support is very good. You could create a cut down Linux configuration by removing all the drivers you don't need, and creating a trivial userspace (perhaps something based on an embedded Linux distro?) This is the path of least resistance for now. One day it would be interesting to create a minimal Mirage-based dom0 kernel. I don't know what state the hardware is in when dom0 starts booting -- clearly the console works already. On Intel/AMD you'd "just" need to initialise the hardware to allow PCI devices to be passed-through to driver domains (running Linux/FreeBSD). How hard could it be? ;-) > Also, a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain > "A driver domain is unprivileged Xen domain that has been given > responsibility for a particular piece of hardware. It runs a minimal kernel > with only that hardware driver and the backend driver for that device > class. Thus, if the hardware driver fails, the other domains (including > Dom0) will survive and, when the driver domain is restarted, will be able > to use the hardware again" > > When they say "minimal kernel" there does that imply a Linux kernel? > A driver domain can have any kernel (Linux, FreeBSD, Mirage etc) but it needs a device driver for the physical hardware. If you wanted to run the same software on lots of different bits of hardware (say generic PCs or laptops) then you'll need a large number of drivers -- Linux would be a good choice for that. I doubt Mirage will ever rival Linux's physical hardware support :-) However if you have fixed hardware in mind then it's up to you. I think Anil's suggestion of accessing GPIO in dom0 and serving requests over vchan is a good place to start. It would be worth asking on xen-devel whether a driver domain could be given access to the GPIO hardware-- I don't know what the possibilities are on ARM devices. On Intel/AMD driver-domains operate at the granularity of PCI devices. It's possible to "pass-through" specific PCI devices to driver domains, where they can perform DMA to virtual memory addresses handled by the IOMMU. I'm optimistic about ARM, since they seem to have done a nice job of their hardware virtualisation support generally. Cheers, Dave > Phil > > > On Sun, Aug 17, 2014 at 10:18 AM, Anil Madhavapeddy > wrote: > >> On 17 Aug 2014, at 12:14, Phil Tomson wrote: >> >> I'm interested in Mirage for some embedded applications that interact >> with the Internet of Things either by http or other protocols (like MQTT or >> COAP). >> >> So for example, let's say I've got a Cubieboard2 and I connect up an A/D >> board to collect data (temperature, weather data, etc.) and I want to setup >> an http server using Mirage that would serve up this data. The http part is >> straightforward. However, how does one interact with the GPIO pins on the >> Cubieboard? - that seems to be on the "other side of" Xen. So would one >> need to write some kind of device driver for Xen that interfaces to the >> Cubieboard's GPIO in order to do this? And if so, how would it be accessed >> by Mirage? >> >> 1. Is it possible? >> 2. If so, can you point me in the right direction? >> >> >> The GPIO pins would, in the simplest instance, just be accessible from >> the Linux running in dom0. After that, you can interface it to a Mirage VM >> via 'vchan': http://openmirage.org/blog/update-on-vchan >> >> If you're feeling extra-paranoid, it's possible to move the GPIO handling >> code into an unprivileged VM, but the first step to do is to figure out the >> GPIO/Linux runes in dom0 first. >> >> I'd be very interested in seeing how this goes... >> >> -anil >> >> > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > -- Dave Scott --047d7b6dc3705d71ca0500d72cb1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Sun, Aug 17, 2014 at 6:35 PM, Phil Tomson <= philtomson@gmail.= com> wrote:
I'm very much= a Xen newbie - ok, maybe not even that far along - so I hope this question= isn't completely uninformed...

Do you have to have Linux running in dom0? Could it be a much sim= pler OS=C2=A0 that basically just allows access to GPIO without a lot of ot= her overhead? Maybe I should back up a step: Is there always a Linux OS run= ning in dom0 when you're running Mirage on a Cubieboard (as in your OSC= ON demo for example)?

On a Xen host, there's alw= ays something in dom0. Xen doesn't care what OS is running in dom0, but= only certain OSes have the necessary Xen dom0 support available. Linux'= ;s Xen support is very good. You could create a cut down Linux configuratio= n by removing all the drivers you don't need, and creating a trivial us= erspace (perhaps something based on an embedded Linux distro?) This is the = path of least resistance for now.

One day it would be interesting to create a minimal Mir= age-based dom0 kernel. I don't know what state the hardware is in when = dom0 starts booting -- clearly the console works already. On Intel/AMD you&= #39;d "just" need to initialise the hardware to allow PCI devices= to be passed-through to driver domains (running Linux/FreeBSD). How hard c= ould it be? ;-)
=C2=A0
Also,= a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain
"A driver domain is unprivileged Xen domain that has been given=20 responsibility for a particular piece of hardware. It runs a minimal=20 kernel with only that hardware driver and the backend driver for that=20 device class. Thus, if the hardware driver fails, the other domains=20 (including Dom0) will survive and, when the driver domain is restarted,=20 will be able to use the hardware again"

W= hen they say "minimal kernel" there does that imply a Linux kerne= l?

A driver domain can have any= kernel (Linux, FreeBSD, Mirage etc) but it needs a device driver for the p= hysical hardware. If you wanted to run the same software on lots of differe= nt bits of hardware (say generic PCs or laptops) then you'll need a lar= ge number of drivers -- Linux would be a good choice for that. I doubt Mira= ge will ever rival Linux's physical hardware support :-) However if you= have fixed hardware in mind then it's up to you.

I think Anil's suggestion of accessing GPIO in dom0= and serving requests over vchan is a good place to start. It would be wort= h asking on xen-devel whether a driver domain could be given access to the = GPIO hardware-- I don't know what the possibilities are on ARM devices.= On Intel/AMD driver-domains operate at the granularity of PCI devices. It&= #39;s possible to "pass-through" specific PCI devices to driver d= omains, where they can perform DMA to virtual memory addresses handled by t= he IOMMU. I'm optimistic about ARM, since they seem to have done a nice= job of their hardware virtualisation support generally.

Cheers,
Dave
=C2=A0
Phil
<= div class=3D"gmail_extra">

On Sun, Aug 17= , 2014 at 10:18 AM, Anil Madhavapeddy <anil@recoil.org> wrote:=
On 17 Aug 2014, at 12:14, Phil Tomson <philtomson@gmail.com> wrote:

I'm inter= ested in Mirage for some embedded applications that interact with the Inter= net of Things either by http or other protocols (like MQTT or COAP).
So for example, let's say I've got a Cubieboard2 and I connec= t up an A/D board to collect data (temperature, weather data, etc.) and I w= ant to setup an http server using Mirage that would serve up this data. The= http part is straightforward. However, how does one interact with the GPIO= pins on the Cubieboard? - that seems to be on the "other side of"= ; Xen. So would one need to write some kind of device driver for Xen that i= nterfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?

1. Is it possible?
2. If so, can you point me = in the right direction?

<= div>The GPIO pins would, in the simplest instance, just be accessible from = the Linux running in dom0. =C2=A0After that, you can interface it to a Mira= ge VM via 'vchan':=C2=A0http://openmirage.org/blog/update-on-vchan

If you're feeling extra-paranoid, it's possible= to move the GPIO handling code into an unprivileged VM, but the first step= to do is to figure out the GPIO/Linux runes in dom0 first.

I'd be very interested in seeing how this goes...

-anil

<= /div>


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




--
Dave Sco= tt --047d7b6dc3705d71ca0500d72cb1-- --===============2899157289937671840== 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 --===============2899157289937671840==-- From mirageos-devel-bounces@lists.xenproject.org Sun Aug 17 18:10:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 17 Aug 2014 18:10: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 1XJ4us-00089b-8Z; Sun, 17 Aug 2014 18: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 1XJ4uq-00089Q-3R for mirageos-devel@lists.xenproject.org; Sun, 17 Aug 2014 18:10:52 +0000 Received: from [85.158.137.68:17462] by server-12.bemta-3.messagelabs.com id 18/D5-02460-B20F0F35; Sun, 17 Aug 2014 18:10:51 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-9.tower-31.messagelabs.com!1408299048!10395381!1 X-Originating-IP: [209.85.192.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 26516 invoked from network); 17 Aug 2014 18:10:49 -0000 Received: from mail-pd0-f173.google.com (HELO mail-pd0-f173.google.com) (209.85.192.173) by server-9.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 17 Aug 2014 18:10:49 -0000 Received: by mail-pd0-f173.google.com with SMTP id w10so6007018pde.18 for ; Sun, 17 Aug 2014 11:10:46 -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=Qk6Xuh4mcodk5jyJpcGAj1p++M4qZuYCbG2VtJDTj8k=; b=owKwXeovJ3bo9e4mB6ouZlh9Ln0rDhf0Gz8A3RE0+ln+tR0T00pEiOWzuwqDmENsCQ jsehBoa9TiIlP+FXMrwjbT0YK0OeFA1HdTP6KipbPBJoAmcBYZC2hp00WvfpTOA8YE2c KhuXNN/NmIoKylmUSAz8ltcnZ2LVE+jjpzPaHMkGYRqDumbspurRAWIWf1U0zqNK2Pjx GURyQuXOWVbeQsWtb+8iD18iTm2yDMSyPJ80Im7HdwLFgNXLTxQawNAXA2iqaO4VJZdv rCdDIM2C4Sgwbay7A48Yg+WuUCJxttzPqGpLhrxfw6WfrIOHFo0XMqiEy/GkD2GebHJF dL5w== MIME-Version: 1.0 X-Received: by 10.66.155.167 with SMTP id vx7mr5218018pab.141.1408299045841; Sun, 17 Aug 2014 11:10:45 -0700 (PDT) Received: by 10.70.65.101 with HTTP; Sun, 17 Aug 2014 11:10:45 -0700 (PDT) In-Reply-To: References: Date: Sun, 17 Aug 2014 19:10:45 +0100 Message-ID: From: David Scott To: Phil Tomson Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage and sensor data X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2899157289937671840==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2899157289937671840== Content-Type: multipart/alternative; boundary=047d7b6dc3705d71ca0500d72cb1 --047d7b6dc3705d71ca0500d72cb1 Content-Type: text/plain; charset=UTF-8 On Sun, Aug 17, 2014 at 6:35 PM, Phil Tomson wrote: > I'm very much a Xen newbie - ok, maybe not even that far along - so I hope > this question isn't completely uninformed... > > Do you have to have Linux running in dom0? Could it be a much simpler OS > that basically just allows access to GPIO without a lot of other overhead? > Maybe I should back up a step: Is there always a Linux OS running in dom0 > when you're running Mirage on a Cubieboard (as in your OSCON demo for > example)? > On a Xen host, there's always something in dom0. Xen doesn't care what OS is running in dom0, but only certain OSes have the necessary Xen dom0 support available. Linux's Xen support is very good. You could create a cut down Linux configuration by removing all the drivers you don't need, and creating a trivial userspace (perhaps something based on an embedded Linux distro?) This is the path of least resistance for now. One day it would be interesting to create a minimal Mirage-based dom0 kernel. I don't know what state the hardware is in when dom0 starts booting -- clearly the console works already. On Intel/AMD you'd "just" need to initialise the hardware to allow PCI devices to be passed-through to driver domains (running Linux/FreeBSD). How hard could it be? ;-) > Also, a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain > "A driver domain is unprivileged Xen domain that has been given > responsibility for a particular piece of hardware. It runs a minimal kernel > with only that hardware driver and the backend driver for that device > class. Thus, if the hardware driver fails, the other domains (including > Dom0) will survive and, when the driver domain is restarted, will be able > to use the hardware again" > > When they say "minimal kernel" there does that imply a Linux kernel? > A driver domain can have any kernel (Linux, FreeBSD, Mirage etc) but it needs a device driver for the physical hardware. If you wanted to run the same software on lots of different bits of hardware (say generic PCs or laptops) then you'll need a large number of drivers -- Linux would be a good choice for that. I doubt Mirage will ever rival Linux's physical hardware support :-) However if you have fixed hardware in mind then it's up to you. I think Anil's suggestion of accessing GPIO in dom0 and serving requests over vchan is a good place to start. It would be worth asking on xen-devel whether a driver domain could be given access to the GPIO hardware-- I don't know what the possibilities are on ARM devices. On Intel/AMD driver-domains operate at the granularity of PCI devices. It's possible to "pass-through" specific PCI devices to driver domains, where they can perform DMA to virtual memory addresses handled by the IOMMU. I'm optimistic about ARM, since they seem to have done a nice job of their hardware virtualisation support generally. Cheers, Dave > Phil > > > On Sun, Aug 17, 2014 at 10:18 AM, Anil Madhavapeddy > wrote: > >> On 17 Aug 2014, at 12:14, Phil Tomson wrote: >> >> I'm interested in Mirage for some embedded applications that interact >> with the Internet of Things either by http or other protocols (like MQTT or >> COAP). >> >> So for example, let's say I've got a Cubieboard2 and I connect up an A/D >> board to collect data (temperature, weather data, etc.) and I want to setup >> an http server using Mirage that would serve up this data. The http part is >> straightforward. However, how does one interact with the GPIO pins on the >> Cubieboard? - that seems to be on the "other side of" Xen. So would one >> need to write some kind of device driver for Xen that interfaces to the >> Cubieboard's GPIO in order to do this? And if so, how would it be accessed >> by Mirage? >> >> 1. Is it possible? >> 2. If so, can you point me in the right direction? >> >> >> The GPIO pins would, in the simplest instance, just be accessible from >> the Linux running in dom0. After that, you can interface it to a Mirage VM >> via 'vchan': http://openmirage.org/blog/update-on-vchan >> >> If you're feeling extra-paranoid, it's possible to move the GPIO handling >> code into an unprivileged VM, but the first step to do is to figure out the >> GPIO/Linux runes in dom0 first. >> >> I'd be very interested in seeing how this goes... >> >> -anil >> >> > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > -- Dave Scott --047d7b6dc3705d71ca0500d72cb1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Sun, Aug 17, 2014 at 6:35 PM, Phil Tomson <= philtomson@gmail.= com> wrote:
I'm very much= a Xen newbie - ok, maybe not even that far along - so I hope this question= isn't completely uninformed...

Do you have to have Linux running in dom0? Could it be a much sim= pler OS=C2=A0 that basically just allows access to GPIO without a lot of ot= her overhead? Maybe I should back up a step: Is there always a Linux OS run= ning in dom0 when you're running Mirage on a Cubieboard (as in your OSC= ON demo for example)?

On a Xen host, there's alw= ays something in dom0. Xen doesn't care what OS is running in dom0, but= only certain OSes have the necessary Xen dom0 support available. Linux'= ;s Xen support is very good. You could create a cut down Linux configuratio= n by removing all the drivers you don't need, and creating a trivial us= erspace (perhaps something based on an embedded Linux distro?) This is the = path of least resistance for now.

One day it would be interesting to create a minimal Mir= age-based dom0 kernel. I don't know what state the hardware is in when = dom0 starts booting -- clearly the console works already. On Intel/AMD you&= #39;d "just" need to initialise the hardware to allow PCI devices= to be passed-through to driver domains (running Linux/FreeBSD). How hard c= ould it be? ;-)
=C2=A0
Also,= a bit of googling reveals http://wiki.xen.org/wiki/Driver_Domain
"A driver domain is unprivileged Xen domain that has been given=20 responsibility for a particular piece of hardware. It runs a minimal=20 kernel with only that hardware driver and the backend driver for that=20 device class. Thus, if the hardware driver fails, the other domains=20 (including Dom0) will survive and, when the driver domain is restarted,=20 will be able to use the hardware again"

W= hen they say "minimal kernel" there does that imply a Linux kerne= l?

A driver domain can have any= kernel (Linux, FreeBSD, Mirage etc) but it needs a device driver for the p= hysical hardware. If you wanted to run the same software on lots of differe= nt bits of hardware (say generic PCs or laptops) then you'll need a lar= ge number of drivers -- Linux would be a good choice for that. I doubt Mira= ge will ever rival Linux's physical hardware support :-) However if you= have fixed hardware in mind then it's up to you.

I think Anil's suggestion of accessing GPIO in dom0= and serving requests over vchan is a good place to start. It would be wort= h asking on xen-devel whether a driver domain could be given access to the = GPIO hardware-- I don't know what the possibilities are on ARM devices.= On Intel/AMD driver-domains operate at the granularity of PCI devices. It&= #39;s possible to "pass-through" specific PCI devices to driver d= omains, where they can perform DMA to virtual memory addresses handled by t= he IOMMU. I'm optimistic about ARM, since they seem to have done a nice= job of their hardware virtualisation support generally.

Cheers,
Dave
=C2=A0
Phil
<= div class=3D"gmail_extra">

On Sun, Aug 17= , 2014 at 10:18 AM, Anil Madhavapeddy <anil@recoil.org> wrote:=
On 17 Aug 2014, at 12:14, Phil Tomson <philtomson@gmail.com> wrote:

I'm inter= ested in Mirage for some embedded applications that interact with the Inter= net of Things either by http or other protocols (like MQTT or COAP).
So for example, let's say I've got a Cubieboard2 and I connec= t up an A/D board to collect data (temperature, weather data, etc.) and I w= ant to setup an http server using Mirage that would serve up this data. The= http part is straightforward. However, how does one interact with the GPIO= pins on the Cubieboard? - that seems to be on the "other side of"= ; Xen. So would one need to write some kind of device driver for Xen that i= nterfaces to the Cubieboard's GPIO in order to do this? And if so, how = would it be accessed by Mirage?

1. Is it possible?
2. If so, can you point me = in the right direction?

<= div>The GPIO pins would, in the simplest instance, just be accessible from = the Linux running in dom0. =C2=A0After that, you can interface it to a Mira= ge VM via 'vchan':=C2=A0http://openmirage.org/blog/update-on-vchan

If you're feeling extra-paranoid, it's possible= to move the GPIO handling code into an unprivileged VM, but the first step= to do is to figure out the GPIO/Linux runes in dom0 first.

I'd be very interested in seeing how this goes...

-anil

<= /div>


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




--
Dave Sco= tt --047d7b6dc3705d71ca0500d72cb1-- --===============2899157289937671840== 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 --===============2899157289937671840==-- From mirageos-devel-bounces@lists.xenproject.org Mon Aug 18 16:52:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 18 Aug 2014 16:52: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 1XJQAt-0003Zr-TD; Mon, 18 Aug 2014 16:52:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJQAs-0003Zm-7Z for mirageos-devel@lists.xenproject.org; Mon, 18 Aug 2014 16:52:50 +0000 Received: from [85.158.139.211:3745] by server-3.bemta-5.messagelabs.com id 3C/D2-13873-16F22F35; Mon, 18 Aug 2014 16:52:49 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1408380767!9120074!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 521 invoked from network); 18 Aug 2014 16:52:47 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Aug 2014 16:52:47 -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]:49866 helo=[192.168.99.66]) 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 1XJQAp-0006yh-DA (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 18 Aug 2014 17:52:47 +0100 From: Amir Chaudhry Message-Id: Date: Mon, 18 Aug 2014 17:52:46 +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, Wednesday 20th 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 Dear all, I'd just like to make it explicitly clear that the Mirage calls are open to all. The agenda is publicly visible, call details are sent out every time and its alway nice to hear from new members of the community. The only expectation is that you briefly introduce yourself (unless you've also added an agenda item - in which case you'll need to speak about that too). Please do feel free to join in! On that note, the next Mirage call will take place on *Wednesday 20th* at 4pm BST (== GMT + 1) -- Apologies about the shifting days, but we're still in conference season. This time it's because Anil is speaking at the Xen Developer Summit in Chicago - the slides are already up if you want to take a look at http://decks.openmirage.org/xendevsummit14/ If you have points you'd like to discuss on the call, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. Notes from the last call are online at: http://openmirage.org/wiki/weekly-2014-08-07 GoToMeeting details: 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: +1 (213) 493-0008 Thanks, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Aug 18 16:52:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 18 Aug 2014 16:52: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 1XJQAt-0003Zr-TD; Mon, 18 Aug 2014 16:52:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJQAs-0003Zm-7Z for mirageos-devel@lists.xenproject.org; Mon, 18 Aug 2014 16:52:50 +0000 Received: from [85.158.139.211:3745] by server-3.bemta-5.messagelabs.com id 3C/D2-13873-16F22F35; Mon, 18 Aug 2014 16:52:49 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1408380767!9120074!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.12.1; banners=-,-,- X-VirusChecked: Checked Received: (qmail 521 invoked from network); 18 Aug 2014 16:52:47 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Aug 2014 16:52:47 -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]:49866 helo=[192.168.99.66]) 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 1XJQAp-0006yh-DA (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Mon, 18 Aug 2014 17:52:47 +0100 From: Amir Chaudhry Message-Id: Date: Mon, 18 Aug 2014 17:52:46 +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, Wednesday 20th 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 Dear all, I'd just like to make it explicitly clear that the Mirage calls are open to all. The agenda is publicly visible, call details are sent out every time and its alway nice to hear from new members of the community. The only expectation is that you briefly introduce yourself (unless you've also added an agenda item - in which case you'll need to speak about that too). Please do feel free to join in! On that note, the next Mirage call will take place on *Wednesday 20th* at 4pm BST (== GMT + 1) -- Apologies about the shifting days, but we're still in conference season. This time it's because Anil is speaking at the Xen Developer Summit in Chicago - the slides are already up if you want to take a look at http://decks.openmirage.org/xendevsummit14/ If you have points you'd like to discuss on the call, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. Notes from the last call are online at: http://openmirage.org/wiki/weekly-2014-08-07 GoToMeeting details: 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: +1 (213) 493-0008 Thanks, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 10:08:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 10:08:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJgL5-0002g3-0J; Tue, 19 Aug 2014 10:08:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJgL3-0002ft-Mn for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 10:08:25 +0000 Received: from [85.158.139.211:27061] by server-17.bemta-5.messagelabs.com id CE/34-08943-91223F35; Tue, 19 Aug 2014 10:08:25 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1408442903!10763029!1 X-Originating-IP: [209.85.218.43] 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 26436 invoked from network); 19 Aug 2014 10:08:24 -0000 Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 10:08:24 -0000 Received: by mail-oi0-f43.google.com with SMTP id u20so4463971oif.16 for ; Tue, 19 Aug 2014 03:08:23 -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=Dzd3Mjrvs3apWmVa7purAfzO8gHidAVLHl4CpDfnKD4=; b=mWOb3AyVIZSQ+wvBrdEKRpfu7vsN8G/jhL+oMOJ+OvaZnm7SZe8HrFksgdZeKYfzez 6mrwra8R0DR73Om9T2hAUHXkY7hTcfohLOzNfHn6CTTIMvD1zW7VHYIAAVtxs/rgOuTH WuSnEx+3ZjqOGSqPME3/AF77idE2GcPnLMD3FVetyDx+HEW2aM+4Ap9LvXDWqr2C2NBM SIQu1vWmyO3btxgZ/NW905YW3xaFueke3gdEjArNi9z/Kfrqi1SSJtSpNFa3cxcSQATc zRGMQ3yAKh0Iv4HOXm4ffNy6oULbvB3yrOIDbEJsq1h19zgMD4AnSevu0GSUfF4xrNQH WEvg== MIME-Version: 1.0 X-Received: by 10.182.114.131 with SMTP id jg3mr42631371obb.9.1408442902849; Tue, 19 Aug 2014 03:08:22 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Tue, 19 Aug 2014 03:08:22 -0700 (PDT) Date: Tue, 19 Aug 2014 11:08:22 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [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 I see Xen allows guests to indicate that the packet checksum is blank (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or get the NIC to do it. How can I use this with Mirage? I tried using ~flags:3 (Checksum_blank + Data_validated) in mirage-net-xen's netif.ml, but I don't see any TCP packets at all this way, even when the checksum is actually still being set. DHCP still works, though. Does anyone know how this is supposed to work? -- 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 Tue Aug 19 10:08:31 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 10:08:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJgL5-0002g3-0J; Tue, 19 Aug 2014 10:08:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJgL3-0002ft-Mn for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 10:08:25 +0000 Received: from [85.158.139.211:27061] by server-17.bemta-5.messagelabs.com id CE/34-08943-91223F35; Tue, 19 Aug 2014 10:08:25 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-5.tower-206.messagelabs.com!1408442903!10763029!1 X-Originating-IP: [209.85.218.43] 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 26436 invoked from network); 19 Aug 2014 10:08:24 -0000 Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 10:08:24 -0000 Received: by mail-oi0-f43.google.com with SMTP id u20so4463971oif.16 for ; Tue, 19 Aug 2014 03:08:23 -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=Dzd3Mjrvs3apWmVa7purAfzO8gHidAVLHl4CpDfnKD4=; b=mWOb3AyVIZSQ+wvBrdEKRpfu7vsN8G/jhL+oMOJ+OvaZnm7SZe8HrFksgdZeKYfzez 6mrwra8R0DR73Om9T2hAUHXkY7hTcfohLOzNfHn6CTTIMvD1zW7VHYIAAVtxs/rgOuTH WuSnEx+3ZjqOGSqPME3/AF77idE2GcPnLMD3FVetyDx+HEW2aM+4Ap9LvXDWqr2C2NBM SIQu1vWmyO3btxgZ/NW905YW3xaFueke3gdEjArNi9z/Kfrqi1SSJtSpNFa3cxcSQATc zRGMQ3yAKh0Iv4HOXm4ffNy6oULbvB3yrOIDbEJsq1h19zgMD4AnSevu0GSUfF4xrNQH WEvg== MIME-Version: 1.0 X-Received: by 10.182.114.131 with SMTP id jg3mr42631371obb.9.1408442902849; Tue, 19 Aug 2014 03:08:22 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Tue, 19 Aug 2014 03:08:22 -0700 (PDT) Date: Tue, 19 Aug 2014 11:08:22 +0100 Message-ID: From: Thomas Leonard To: "mirageos-devel@lists.xenproject.org" Subject: [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 I see Xen allows guests to indicate that the packet checksum is blank (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or get the NIC to do it. How can I use this with Mirage? I tried using ~flags:3 (Checksum_blank + Data_validated) in mirage-net-xen's netif.ml, but I don't see any TCP packets at all this way, even when the checksum is actually still being set. DHCP still works, though. Does anyone know how this is supposed to work? -- 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 Tue Aug 19 10:18:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 10:18: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 1XJgV1-0002uW-Rj; Tue, 19 Aug 2014 10:18:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJgV0-0002uP-2M for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 10:18:42 +0000 Received: from [193.109.254.147:17002] by server-12.bemta-14.messagelabs.com id BF/92-23840-18423F35; Tue, 19 Aug 2014 10:18:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1408443520!11758709!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 31855 invoked from network); 19 Aug 2014 10:18:40 -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; 19 Aug 2014 10:18:40 -0000 Received: (qmail 2782 invoked by uid 634); 19 Aug 2014 10:18:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 11:18:39 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 05:18:37 -0500 Message-Id: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> References: 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] 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 Aug 2014, at 05:08, Thomas Leonard wrote: > I see Xen allows guests to indicate that the packet checksum is blank > (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or > get the NIC to do it. How can I use this with Mirage? > > I tried using ~flags:3 (Checksum_blank + Data_validated) in > mirage-net-xen's netif.ml, but I don't see any TCP packets at all this > way, even when the checksum is actually still being set. DHCP still > works, though. > > Does anyone know how this is supposed to work? Probably best to trace through what netback is doing here: http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 Looks like XEN_NETTXF_data_validated may need to be set as well (and local packets are treated differently from off-host ones, to add an extra twist). -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 Aug 19 10:18:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 10:18: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 1XJgV1-0002uW-Rj; Tue, 19 Aug 2014 10:18:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJgV0-0002uP-2M for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 10:18:42 +0000 Received: from [193.109.254.147:17002] by server-12.bemta-14.messagelabs.com id BF/92-23840-18423F35; Tue, 19 Aug 2014 10:18:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1408443520!11758709!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 31855 invoked from network); 19 Aug 2014 10:18:40 -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; 19 Aug 2014 10:18:40 -0000 Received: (qmail 2782 invoked by uid 634); 19 Aug 2014 10:18:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 11:18:39 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 05:18:37 -0500 Message-Id: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> References: 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] 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 Aug 2014, at 05:08, Thomas Leonard wrote: > I see Xen allows guests to indicate that the packet checksum is blank > (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or > get the NIC to do it. How can I use this with Mirage? > > I tried using ~flags:3 (Checksum_blank + Data_validated) in > mirage-net-xen's netif.ml, but I don't see any TCP packets at all this > way, even when the checksum is actually still being set. DHCP still > works, though. > > Does anyone know how this is supposed to work? Probably best to trace through what netback is doing here: http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 Looks like XEN_NETTXF_data_validated may need to be set as well (and local packets are treated differently from off-host ones, to add an extra twist). -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 Aug 19 13:44:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:44: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 1XJjhx-0000GC-RR; Tue, 19 Aug 2014 13:44:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjhw-0000Fs-FZ for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:44:16 +0000 Received: from [85.158.139.211:24846] by server-5.bemta-5.messagelabs.com id FE/9D-11546-FA453F35; Tue, 19 Aug 2014 13:44:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1408455854!10860444!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 11732 invoked from network); 19 Aug 2014 13:44:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 19 Aug 2014 13:44:14 -0000 Received: (qmail 29805 invoked by uid 634); 19 Aug 2014 13:44:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 14:44:13 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 08:44:10 -0500 Message-Id: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> References: To: mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Felipe Huici Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 11:01, Anil Madhavapeddy wrote: > I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. > > Slides here: http://decks.openmirage.org/xendevsummit14#/ > Repo: https://github.com/mirage/mirage-decks as usual > [+xen-api-devel] Talk went well, quick notes here: - git workflow very popular. Lots of people twigged onto the maintainability benefits of `git bisect` automation in particular. - questions about why Xenstore transactions are still necessary in the modern world. Can replace with consensus protocols instead? Maybe time for an ABI bump to deprecate the ancient xenstore protocol. - space usage is a concern -- building an RRD-style constant size library to maintain progressive history would be a big win. - *excellent* talk from Felipe Huici (CCed) from NEC about building much denser VM workloads, and he observed that Xenstored/xenconsoled are a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some sub notes: - we could write a mirage xenconsoled to log to irmin and drain guest console rings much faster. - a distributed xenstored+irmin would allow significantly more scalability than attempting to build a serially fast version. - felipe has the beginning of a simple c++ xenstored that doesn't implement the full semantics, but is enough for MiniOS. - it may be useful to negotiate a xenstore v2 protocol and use that for new guests. It could use a simple fixed-length binary protocol (protobuf-style?), and eliminate the need for transactions perhaps. -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 Aug 19 13:44:23 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:44: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 1XJjhx-0000GC-RR; Tue, 19 Aug 2014 13:44:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjhw-0000Fs-FZ for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:44:16 +0000 Received: from [85.158.139.211:24846] by server-5.bemta-5.messagelabs.com id FE/9D-11546-FA453F35; Tue, 19 Aug 2014 13:44:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1408455854!10860444!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 11732 invoked from network); 19 Aug 2014 13:44:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 19 Aug 2014 13:44:14 -0000 Received: (qmail 29805 invoked by uid 634); 19 Aug 2014 13:44:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 14:44:13 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 08:44:10 -0500 Message-Id: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> References: To: mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Felipe Huici Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 11:01, Anil Madhavapeddy wrote: > I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. > > Slides here: http://decks.openmirage.org/xendevsummit14#/ > Repo: https://github.com/mirage/mirage-decks as usual > [+xen-api-devel] Talk went well, quick notes here: - git workflow very popular. Lots of people twigged onto the maintainability benefits of `git bisect` automation in particular. - questions about why Xenstore transactions are still necessary in the modern world. Can replace with consensus protocols instead? Maybe time for an ABI bump to deprecate the ancient xenstore protocol. - space usage is a concern -- building an RRD-style constant size library to maintain progressive history would be a big win. - *excellent* talk from Felipe Huici (CCed) from NEC about building much denser VM workloads, and he observed that Xenstored/xenconsoled are a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some sub notes: - we could write a mirage xenconsoled to log to irmin and drain guest console rings much faster. - a distributed xenstored+irmin would allow significantly more scalability than attempting to build a serially fast version. - felipe has the beginning of a simple c++ xenstored that doesn't implement the full semantics, but is enough for MiniOS. - it may be useful to negotiate a xenstore v2 protocol and use that for new guests. It could use a simple fixed-length binary protocol (protobuf-style?), and eliminate the need for transactions perhaps. -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 Aug 19 13:47:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:47: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 1XJjlH-0000NR-5a; Tue, 19 Aug 2014 13:47:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjlG-0000NG-2E for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:47:42 +0000 Received: from [85.158.139.211:29727] by server-9.bemta-5.messagelabs.com id BC/50-20744-D7553F35; Tue, 19 Aug 2014 13:47:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1408456060!10834606!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 25772 invoked from network); 19 Aug 2014 13:47:40 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-206.messagelabs.com with SMTP; 19 Aug 2014 13:47:40 -0000 Received: (qmail 7800 invoked by uid 634); 19 Aug 2014 13:47:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 14:47:39 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> Date: Tue, 19 Aug 2014 08:47:37 -0500 Message-Id: <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> References: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> To: mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Felipe Huici Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 08:44, Anil Madhavapeddy wrote: > On 17 Aug 2014, at 11:01, Anil Madhavapeddy wrote: > >> I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. >> >> Slides here: http://decks.openmirage.org/xendevsummit14#/ >> Repo: https://github.com/mirage/mirage-decks as usual >> > > [+xen-api-devel] Talk went well, quick notes here: > > - git workflow very popular. Lots of people twigged onto the maintainability benefits of `git bisect` automation in particular. > > - questions about why Xenstore transactions are still necessary in the modern world. Can replace with consensus protocols instead? Maybe time for an ABI bump to deprecate the ancient xenstore protocol. > > - space usage is a concern -- building an RRD-style constant size library to maintain progressive history would be a big win. > > - *excellent* talk from Felipe Huici (CCed) from NEC about building much denser VM workloads, and he observed that Xenstored/xenconsoled are a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some sub notes: > > - we could write a mirage xenconsoled to log to irmin and drain guest console rings much faster. > - a distributed xenstored+irmin would allow significantly more scalability than attempting to build a serially fast version. > - felipe has the beginning of a simple c++ xenstored that doesn't implement the full semantics, but is enough for MiniOS. > - it may be useful to negotiate a xenstore v2 protocol and use that for new guests. It could use a simple fixed-length binary protocol (protobuf-style?), and eliminate the need for transactions perhaps. sent 'send' too quickly. The most important point: - xenstore need consistent indices. Using domain names in the current stack results in a linear search through all domids -- very slow with 10000 VMs! Irmin could maintain a branch that updates a 'name -> domid' that is consistent within the transaction, and do constant time lookups for the toolstack. -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 Aug 19 13:47:44 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:47: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 1XJjlH-0000NR-5a; Tue, 19 Aug 2014 13:47:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjlG-0000NG-2E for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:47:42 +0000 Received: from [85.158.139.211:29727] by server-9.bemta-5.messagelabs.com id BC/50-20744-D7553F35; Tue, 19 Aug 2014 13:47:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-206.messagelabs.com!1408456060!10834606!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 25772 invoked from network); 19 Aug 2014 13:47:40 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-206.messagelabs.com with SMTP; 19 Aug 2014 13:47:40 -0000 Received: (qmail 7800 invoked by uid 634); 19 Aug 2014 13:47:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 14:47:39 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> Date: Tue, 19 Aug 2014 08:47:37 -0500 Message-Id: <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> References: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> To: mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Felipe Huici Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Aug 2014, at 08:44, Anil Madhavapeddy wrote: > On 17 Aug 2014, at 11:01, Anil Madhavapeddy wrote: > >> I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. >> >> Slides here: http://decks.openmirage.org/xendevsummit14#/ >> Repo: https://github.com/mirage/mirage-decks as usual >> > > [+xen-api-devel] Talk went well, quick notes here: > > - git workflow very popular. Lots of people twigged onto the maintainability benefits of `git bisect` automation in particular. > > - questions about why Xenstore transactions are still necessary in the modern world. Can replace with consensus protocols instead? Maybe time for an ABI bump to deprecate the ancient xenstore protocol. > > - space usage is a concern -- building an RRD-style constant size library to maintain progressive history would be a big win. > > - *excellent* talk from Felipe Huici (CCed) from NEC about building much denser VM workloads, and he observed that Xenstored/xenconsoled are a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some sub notes: > > - we could write a mirage xenconsoled to log to irmin and drain guest console rings much faster. > - a distributed xenstored+irmin would allow significantly more scalability than attempting to build a serially fast version. > - felipe has the beginning of a simple c++ xenstored that doesn't implement the full semantics, but is enough for MiniOS. > - it may be useful to negotiate a xenstore v2 protocol and use that for new guests. It could use a simple fixed-length binary protocol (protobuf-style?), and eliminate the need for transactions perhaps. sent 'send' too quickly. The most important point: - xenstore need consistent indices. Using domain names in the current stack results in a linear search through all domids -- very slow with 10000 VMs! Irmin could maintain a branch that updates a 'name -> domid' that is consistent within the transaction, and do constant time lookups for the toolstack. -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 Aug 19 13:55:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:55: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 1XJjsL-0000VZ-2F; Tue, 19 Aug 2014 13:55:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjsJ-0000VU-Tc for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:55:00 +0000 Received: from [85.158.143.35:58985] by server-3.bemta-4.messagelabs.com id 50/9A-06192-33753F35; Tue, 19 Aug 2014 13:54:59 +0000 X-Env-Sender: bgercken@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1408456497!11934123!1 X-Originating-IP: [209.85.216.170] 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 12137 invoked from network); 19 Aug 2014 13:54:58 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 13:54:58 -0000 Received: by mail-qc0-f170.google.com with SMTP id x3so6288666qcv.1 for ; Tue, 19 Aug 2014 06:54: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=jupPBt+MX2NiP2J7RwVqMygmjiup2rKSCY/lXNfU8kQ=; b=F3p9JZb210wW3BCmM/+/fgx038u4b2JO+/a5+VfVS3bxT8Ks7MChy7kzlNT95DOEug g6+/s6vdg8LLACs0ZemZAZbH38SNO04aQ8yuav4ojQ8LUBGFQrDJvg5AqRVUFsIh09tD hF3A4Iguk3BUB1MBxZvbxFKxaoBR2GElInWznv+KypLWDfvGJj1Bf6/R81q964Da55d6 MAKAVAblriwwTR4P6xsCf1eOZ3SnyvNvCr7zXbJl2r+o+3B4wJbamvtBHZEsw4nB187I R4yW3DUJYoc8q16qnR1atHqrMZ94cAsOaLlIW58osNWNtp+6DGmnSghEtPV0S1YpCZEy JtfQ== MIME-Version: 1.0 X-Received: by 10.140.41.133 with SMTP id z5mr62568851qgz.99.1408456496597; Tue, 19 Aug 2014 06:54:56 -0700 (PDT) Received: by 10.96.53.106 with HTTP; Tue, 19 Aug 2014 06:54:56 -0700 (PDT) Date: Tue, 19 Aug 2014 09:54:56 -0400 Message-ID: From: Bill Gercken To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] MirageOS KVM 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="===============4647845568348632905==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4647845568348632905== Content-Type: multipart/alternative; boundary=001a11c11fd829524a0500fbd55e --001a11c11fd829524a0500fbd55e Content-Type: text/plain; charset=UTF-8 Hello, Is anybody actively working on support for KVM? We are in a situation where we need to deploy to both Xen and KVM and I would love to be able to create unikernel applications that can be compiled for both environments. Thank you for your time. -bill --001a11c11fd829524a0500fbd55e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,
=C2=A0
Is anybody actively= working on support for KVM?
=C2=A0
We are in a situati= on where we need to=C2=A0deploy to=C2=A0both Xen and KVM and I would love t= o be able to create unikernel applications that can be compiled=C2=A0for bo= th environments.
=C2=A0
Thank you for your time.
=C2=A0
-= bill
=C2=A0
=C2=A0
--001a11c11fd829524a0500fbd55e-- --===============4647845568348632905== 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 --===============4647845568348632905==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 13:55:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:55: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 1XJjsL-0000VZ-2F; Tue, 19 Aug 2014 13:55:01 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjsJ-0000VU-Tc for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:55:00 +0000 Received: from [85.158.143.35:58985] by server-3.bemta-4.messagelabs.com id 50/9A-06192-33753F35; Tue, 19 Aug 2014 13:54:59 +0000 X-Env-Sender: bgercken@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1408456497!11934123!1 X-Originating-IP: [209.85.216.170] 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 12137 invoked from network); 19 Aug 2014 13:54:58 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 13:54:58 -0000 Received: by mail-qc0-f170.google.com with SMTP id x3so6288666qcv.1 for ; Tue, 19 Aug 2014 06:54: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=jupPBt+MX2NiP2J7RwVqMygmjiup2rKSCY/lXNfU8kQ=; b=F3p9JZb210wW3BCmM/+/fgx038u4b2JO+/a5+VfVS3bxT8Ks7MChy7kzlNT95DOEug g6+/s6vdg8LLACs0ZemZAZbH38SNO04aQ8yuav4ojQ8LUBGFQrDJvg5AqRVUFsIh09tD hF3A4Iguk3BUB1MBxZvbxFKxaoBR2GElInWznv+KypLWDfvGJj1Bf6/R81q964Da55d6 MAKAVAblriwwTR4P6xsCf1eOZ3SnyvNvCr7zXbJl2r+o+3B4wJbamvtBHZEsw4nB187I R4yW3DUJYoc8q16qnR1atHqrMZ94cAsOaLlIW58osNWNtp+6DGmnSghEtPV0S1YpCZEy JtfQ== MIME-Version: 1.0 X-Received: by 10.140.41.133 with SMTP id z5mr62568851qgz.99.1408456496597; Tue, 19 Aug 2014 06:54:56 -0700 (PDT) Received: by 10.96.53.106 with HTTP; Tue, 19 Aug 2014 06:54:56 -0700 (PDT) Date: Tue, 19 Aug 2014 09:54:56 -0400 Message-ID: From: Bill Gercken To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] MirageOS KVM 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="===============4647845568348632905==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4647845568348632905== Content-Type: multipart/alternative; boundary=001a11c11fd829524a0500fbd55e --001a11c11fd829524a0500fbd55e Content-Type: text/plain; charset=UTF-8 Hello, Is anybody actively working on support for KVM? We are in a situation where we need to deploy to both Xen and KVM and I would love to be able to create unikernel applications that can be compiled for both environments. Thank you for your time. -bill --001a11c11fd829524a0500fbd55e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,
=C2=A0
Is anybody actively= working on support for KVM?
=C2=A0
We are in a situati= on where we need to=C2=A0deploy to=C2=A0both Xen and KVM and I would love t= o be able to create unikernel applications that can be compiled=C2=A0for bo= th environments.
=C2=A0
Thank you for your time.
=C2=A0
-= bill
=C2=A0
=C2=A0
--001a11c11fd829524a0500fbd55e-- --===============4647845568348632905== 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 --===============4647845568348632905==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 13:58:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:58: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 1XJjw5-0000Xe-Fw; Tue, 19 Aug 2014 13:58:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjw3-0000XV-Ta for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:58:52 +0000 Received: from [85.158.139.211:57259] by server-12.bemta-5.messagelabs.com id C9/4B-22251-B1853F35; Tue, 19 Aug 2014 13:58:51 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-206.messagelabs.com!1408456730!10883512!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 6271 invoked from network); 19 Aug 2014 13:58:50 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-206.messagelabs.com with SMTP; 19 Aug 2014 13:58:50 -0000 Received: (qmail 11314 invoked by uid 634); 19 Aug 2014 13:58:50 -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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 14:58:50 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 08:58:47 -0500 Message-Id: References: To: Bill Gercken 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 KVM Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19 Aug 2014, at 08:54, Bill Gercken wrote: > Hello, > > Is anybody actively working on support for KVM? > > We are in a situation where we need to deploy to both Xen and KVM and I would love to be able to create unikernel applications that can be compiled for both environments. > KVM is not specifically being worked on at this time, but we'd love to hear from anyone that would like to contribute towards the effort. There have been several recent developments to make this easier in Mirage 2: - the MiniOS library is now picked up from an external package - this library is in sync with the Xen development tree (should be part of Xen 4.5) and is multiarch (x86_64/x86_32 and ARM). - TODO: add a HVM boot mode to upstream MiniOS to let it boot in Xen hardware virt mode (Jon Ludlam had some patches against an earlier MiniOS that did this). After this, KVM support is pretty easy; it just needs the addition of virtio drivers in OCaml, which isn't a complex task. -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 Aug 19 13:58:54 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 13:58: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 1XJjw5-0000Xe-Fw; Tue, 19 Aug 2014 13:58:53 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJjw3-0000XV-Ta for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 13:58:52 +0000 Received: from [85.158.139.211:57259] by server-12.bemta-5.messagelabs.com id C9/4B-22251-B1853F35; Tue, 19 Aug 2014 13:58:51 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-206.messagelabs.com!1408456730!10883512!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 6271 invoked from network); 19 Aug 2014 13:58:50 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-206.messagelabs.com with SMTP; 19 Aug 2014 13:58:50 -0000 Received: (qmail 11314 invoked by uid 634); 19 Aug 2014 13:58:50 -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 173-15-26-62-Illinois.hfc.comcastbusiness.net (HELO [10.228.243.189]) (173.15.26.62) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 14:58:50 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 08:58:47 -0500 Message-Id: References: To: Bill Gercken 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 KVM Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19 Aug 2014, at 08:54, Bill Gercken wrote: > Hello, > > Is anybody actively working on support for KVM? > > We are in a situation where we need to deploy to both Xen and KVM and I would love to be able to create unikernel applications that can be compiled for both environments. > KVM is not specifically being worked on at this time, but we'd love to hear from anyone that would like to contribute towards the effort. There have been several recent developments to make this easier in Mirage 2: - the MiniOS library is now picked up from an external package - this library is in sync with the Xen development tree (should be part of Xen 4.5) and is multiarch (x86_64/x86_32 and ARM). - TODO: add a HVM boot mode to upstream MiniOS to let it boot in Xen hardware virt mode (Jon Ludlam had some patches against an earlier MiniOS that did this). After this, KVM support is pretty easy; it just needs the addition of virtio drivers in OCaml, which isn't a complex task. -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 Aug 19 14:33:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 14:33: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 1XJkT9-00023T-NJ; Tue, 19 Aug 2014 14:33:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJkT7-00023M-LK for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 14:33:02 +0000 Received: from [85.158.143.35:19299] by server-3.bemta-4.messagelabs.com id 70/9E-06192-D1063F35; Tue, 19 Aug 2014 14:33:01 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1408458778!11592321!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 7158 invoked from network); 19 Aug 2014 14:33:00 -0000 Received: from mail-oi0-f52.google.com (HELO mail-oi0-f52.google.com) (209.85.218.52) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 14:33:00 -0000 Received: by mail-oi0-f52.google.com with SMTP id h136so4632786oig.39 for ; Tue, 19 Aug 2014 07:32:58 -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=x+GCN9wvPBVgKLCDIvwoGuI5rT8owt9JOXZgr8+FZCk=; b=VenRRodFN0EIPxY5zoDABnjnGgziqBHmvOVuowoiMUkpaCadcj2u1iv4FWsftbxubl Cbt6qYdCvCJmNNcQiUXMeg8uibUbrHd8oPcV3WkcAYHc2CA/kkcnG9sPmmkb0H+Ss0lZ shFk60MlTv4YjrXvy2hpmlhH3NvQ2JFc9E1Lfc9M3lbfJXkzuoRNxk8VhSR/+H4m9Yje mQz5jVWrjtVPwiqk5/EFXvEMOVwQLstM6ptkgvxwNb8OdCQuTkq6ADSeclzijZ7+p34w FFyiEqhb063bOZYgryOTY4/76rBbUGBhl6218SZsNMDdBrbti5O09EgWrjG/tpEGZ5Mo ejVg== MIME-Version: 1.0 X-Received: by 10.182.104.104 with SMTP id gd8mr42486861obb.17.1408458778713; Tue, 19 Aug 2014 07:32:58 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Tue, 19 Aug 2014 07:32:58 -0700 (PDT) In-Reply-To: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> Date: Tue, 19 Aug 2014 15:32:58 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "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 11:18, Anil Madhavapeddy wrote: > > On 19 Aug 2014, at 05:08, Thomas Leonard wrote: > >> I see Xen allows guests to indicate that the packet checksum is blank >> (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or >> get the NIC to do it. How can I use this with Mirage? >> >> I tried using ~flags:3 (Checksum_blank + Data_validated) in >> mirage-net-xen's netif.ml, but I don't see any TCP packets at all this >> way, even when the checksum is actually still being set. DHCP still >> works, though. >> >> Does anyone know how this is supposed to work? > > Probably best to trace through what netback is doing here: > http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 > > Looks like XEN_NETTXF_data_validated may need to be set as well > (and local packets are treated differently from off-host ones, to > add an extra twist). The problem turned out to be that I was setting the flag for all packets, including ARPs. Getting this to work properly will require so API changes, because NETWORK needs to tell the ethernet driver which types of packet can be offloaded, and let the driver say which packets require checksums to be added. Then similar changes are needed to ETHIF. Here are the hacks I used to test it: https://github.com/talex5/mirage/commits/csum-offload https://github.com/talex5/mirage-net-xen/commits/csum-offload https://github.com/talex5/mirage-tcpip/commits/csum-offload -- 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 Tue Aug 19 14:33:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 14:33: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 1XJkT9-00023T-NJ; Tue, 19 Aug 2014 14:33:03 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJkT7-00023M-LK for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 14:33:02 +0000 Received: from [85.158.143.35:19299] by server-3.bemta-4.messagelabs.com id 70/9E-06192-D1063F35; Tue, 19 Aug 2014 14:33:01 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-21.messagelabs.com!1408458778!11592321!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 7158 invoked from network); 19 Aug 2014 14:33:00 -0000 Received: from mail-oi0-f52.google.com (HELO mail-oi0-f52.google.com) (209.85.218.52) by server-3.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 14:33:00 -0000 Received: by mail-oi0-f52.google.com with SMTP id h136so4632786oig.39 for ; Tue, 19 Aug 2014 07:32:58 -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=x+GCN9wvPBVgKLCDIvwoGuI5rT8owt9JOXZgr8+FZCk=; b=VenRRodFN0EIPxY5zoDABnjnGgziqBHmvOVuowoiMUkpaCadcj2u1iv4FWsftbxubl Cbt6qYdCvCJmNNcQiUXMeg8uibUbrHd8oPcV3WkcAYHc2CA/kkcnG9sPmmkb0H+Ss0lZ shFk60MlTv4YjrXvy2hpmlhH3NvQ2JFc9E1Lfc9M3lbfJXkzuoRNxk8VhSR/+H4m9Yje mQz5jVWrjtVPwiqk5/EFXvEMOVwQLstM6ptkgvxwNb8OdCQuTkq6ADSeclzijZ7+p34w FFyiEqhb063bOZYgryOTY4/76rBbUGBhl6218SZsNMDdBrbti5O09EgWrjG/tpEGZ5Mo ejVg== MIME-Version: 1.0 X-Received: by 10.182.104.104 with SMTP id gd8mr42486861obb.17.1408458778713; Tue, 19 Aug 2014 07:32:58 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Tue, 19 Aug 2014 07:32:58 -0700 (PDT) In-Reply-To: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> Date: Tue, 19 Aug 2014 15:32:58 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "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 11:18, Anil Madhavapeddy wrote: > > On 19 Aug 2014, at 05:08, Thomas Leonard wrote: > >> I see Xen allows guests to indicate that the packet checksum is blank >> (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or >> get the NIC to do it. How can I use this with Mirage? >> >> I tried using ~flags:3 (Checksum_blank + Data_validated) in >> mirage-net-xen's netif.ml, but I don't see any TCP packets at all this >> way, even when the checksum is actually still being set. DHCP still >> works, though. >> >> Does anyone know how this is supposed to work? > > Probably best to trace through what netback is doing here: > http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 > > Looks like XEN_NETTXF_data_validated may need to be set as well > (and local packets are treated differently from off-host ones, to > add an extra twist). The problem turned out to be that I was setting the flag for all packets, including ARPs. Getting this to work properly will require so API changes, because NETWORK needs to tell the ethernet driver which types of packet can be offloaded, and let the driver say which packets require checksums to be added. Then similar changes are needed to ETHIF. Here are the hacks I used to test it: https://github.com/talex5/mirage/commits/csum-offload https://github.com/talex5/mirage-net-xen/commits/csum-offload https://github.com/talex5/mirage-tcpip/commits/csum-offload -- 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 Tue Aug 19 14:35:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 14:35: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 1XJkVI-000259-Uo; Tue, 19 Aug 2014 14:35:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJkVH-000254-8H for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 14:35:15 +0000 Received: from [85.158.143.35:40803] by server-2.bemta-4.messagelabs.com id 2A/20-04525-2A063F35; Tue, 19 Aug 2014 14:35:14 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1408458913!11899942!1 X-Originating-IP: [74.125.82.172] 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 13596 invoked from network); 19 Aug 2014 14:35:14 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 14:35:14 -0000 Received: by mail-we0-f172.google.com with SMTP id x48so6615203wes.31 for ; Tue, 19 Aug 2014 07:35:13 -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:date:message-id:subject:from:to :content-type; bh=n9kLt8MH7AKlSYxImeLtlp4CPgyskgAPiwaBvC2wKNc=; b=MXE7rlkfF86bZwRkJToCWw09h2rcymvWcpE29HyZxcf4yTbT8IGvLffCaNuOfgFVvX Tg7R9ibimjwqTY4+KJ8l5fGJy0UYzUY+HbMqusy9BpmQI2FdztR5y3KkW2r31gtP+den hRd2CpMPKHB2hZZ61Rwj719FRVNtawudAQMZJlAx6IqDYQmhTbc8r6ruhfizbeGKV+Jc NLGXiSw4GbSaxexK6Qv2XPRIFBg+N1nAiyLb0inJVWq/fqbIrXBoIf0ex6FRMRy3/O+7 GRS1EsteXwf2QUXXUBSPE5lE2LcEMaf1Z8bXEYgcg5007HOJLj7Wj74G7v4UcRE0UmE6 qOWQ== X-Gm-Message-State: ALoCoQndV3FUPtdGX+n75xsO5L4zkwvayVOtiqi0u9YpWD3ZRPK/8S989ZYUTOIrpNuxQ8g61Pzt MIME-Version: 1.0 X-Received: by 10.180.108.212 with SMTP id hm20mr6374972wib.4.1408458913536; Tue, 19 Aug 2014 07:35:13 -0700 (PDT) Received: by 10.194.63.180 with HTTP; Tue, 19 Aug 2014 07:35:13 -0700 (PDT) Date: Tue, 19 Aug 2014 10:35:13 -0400 Message-ID: From: Len Maxwell To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage on EC2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, I have not been able to successfully boot a unikernel-based AMI on EC2 (something I will revisit later). In the meantime, I found that you can replace the kernel on a standard Linux instance without much trouble: - Build a unikernel, ex. mirage-skeleton/static_website. - Launch an instance with the "Amazon Linux AMI ... PV" (on us-east-1: ami-7c807d14 for instance-backed, ami-7c807d14 for EBS-backed). This will select the proper AKI for pvgrub. Make sure to set up an SSH key, and a security group that allows ssh and http. - Once the instance is up, push the kernel to ec2-user's home directory: scp mir-www.xen ec2-user@:. - Log in as ec2-user: ssh ec2-user@ - Move the kernel to /boot: sudo mv mir-www.xen /boot - Edit the grub menu: sudo vi /boot/grub/menu.lst - Add the following menu entry, before (or instead of) the "title Amazon Linux" entry: title mirage root (hd0) kernel /boot/mir-www.xen - Restart: sudo shutdown -r now This should work OK as long as the unikernel uses only memory and network; the disk is full of Linux cruft. It's not ideal, but I think that using a Linux AMI to bootstrap an instance might be a practical alternative to minting an AMI for each update. -- 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 Tue Aug 19 14:35:17 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 14:35: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 1XJkVI-000259-Uo; Tue, 19 Aug 2014 14:35:16 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJkVH-000254-8H for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 14:35:15 +0000 Received: from [85.158.143.35:40803] by server-2.bemta-4.messagelabs.com id 2A/20-04525-2A063F35; Tue, 19 Aug 2014 14:35:14 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-4.tower-21.messagelabs.com!1408458913!11899942!1 X-Originating-IP: [74.125.82.172] 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 13596 invoked from network); 19 Aug 2014 14:35:14 -0000 Received: from mail-we0-f172.google.com (HELO mail-we0-f172.google.com) (74.125.82.172) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 14:35:14 -0000 Received: by mail-we0-f172.google.com with SMTP id x48so6615203wes.31 for ; Tue, 19 Aug 2014 07:35:13 -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:date:message-id:subject:from:to :content-type; bh=n9kLt8MH7AKlSYxImeLtlp4CPgyskgAPiwaBvC2wKNc=; b=MXE7rlkfF86bZwRkJToCWw09h2rcymvWcpE29HyZxcf4yTbT8IGvLffCaNuOfgFVvX Tg7R9ibimjwqTY4+KJ8l5fGJy0UYzUY+HbMqusy9BpmQI2FdztR5y3KkW2r31gtP+den hRd2CpMPKHB2hZZ61Rwj719FRVNtawudAQMZJlAx6IqDYQmhTbc8r6ruhfizbeGKV+Jc NLGXiSw4GbSaxexK6Qv2XPRIFBg+N1nAiyLb0inJVWq/fqbIrXBoIf0ex6FRMRy3/O+7 GRS1EsteXwf2QUXXUBSPE5lE2LcEMaf1Z8bXEYgcg5007HOJLj7Wj74G7v4UcRE0UmE6 qOWQ== X-Gm-Message-State: ALoCoQndV3FUPtdGX+n75xsO5L4zkwvayVOtiqi0u9YpWD3ZRPK/8S989ZYUTOIrpNuxQ8g61Pzt MIME-Version: 1.0 X-Received: by 10.180.108.212 with SMTP id hm20mr6374972wib.4.1408458913536; Tue, 19 Aug 2014 07:35:13 -0700 (PDT) Received: by 10.194.63.180 with HTTP; Tue, 19 Aug 2014 07:35:13 -0700 (PDT) Date: Tue, 19 Aug 2014 10:35:13 -0400 Message-ID: From: Len Maxwell To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Mirage on EC2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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, I have not been able to successfully boot a unikernel-based AMI on EC2 (something I will revisit later). In the meantime, I found that you can replace the kernel on a standard Linux instance without much trouble: - Build a unikernel, ex. mirage-skeleton/static_website. - Launch an instance with the "Amazon Linux AMI ... PV" (on us-east-1: ami-7c807d14 for instance-backed, ami-7c807d14 for EBS-backed). This will select the proper AKI for pvgrub. Make sure to set up an SSH key, and a security group that allows ssh and http. - Once the instance is up, push the kernel to ec2-user's home directory: scp mir-www.xen ec2-user@:. - Log in as ec2-user: ssh ec2-user@ - Move the kernel to /boot: sudo mv mir-www.xen /boot - Edit the grub menu: sudo vi /boot/grub/menu.lst - Add the following menu entry, before (or instead of) the "title Amazon Linux" entry: title mirage root (hd0) kernel /boot/mir-www.xen - Restart: sudo shutdown -r now This should work OK as long as the unikernel uses only memory and network; the disk is full of Linux cruft. It's not ideal, but I think that using a Linux AMI to bootstrap an instance might be a practical alternative to minting an AMI for each update. -- 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 Tue Aug 19 15:16:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 15:16: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 1XJl9P-0002QL-6S; Tue, 19 Aug 2014 15:16:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJl9O-0002QG-BC for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 15:16:42 +0000 Received: from [193.109.254.147:64762] by server-6.bemta-14.messagelabs.com id 41/2A-31278-95A63F35; Tue, 19 Aug 2014 15:16:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1408461392!11837321!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 13991 invoked from network); 19 Aug 2014 15:16:32 -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; 19 Aug 2014 15:16:32 -0000 Received: (qmail 13553 invoked by uid 634); 19 Aug 2014 15:16:32 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [172.18.15.137]) (208.59.64.2) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 16:16:31 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 10:07:00 -0500 Message-Id: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@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] 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 Aug 2014, at 09:32, Thomas Leonard wrote: > On 19 August 2014 11:18, Anil Madhavapeddy wrote: >> >> On 19 Aug 2014, at 05:08, Thomas Leonard wrote: >> >>> I see Xen allows guests to indicate that the packet checksum is blank >>> (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or >>> get the NIC to do it. How can I use this with Mirage? >>> >>> I tried using ~flags:3 (Checksum_blank + Data_validated) in >>> mirage-net-xen's netif.ml, but I don't see any TCP packets at all this >>> way, even when the checksum is actually still being set. DHCP still >>> works, though. >>> >>> Does anyone know how this is supposed to work? >> >> Probably best to trace through what netback is doing here: >> http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 >> >> Looks like XEN_NETTXF_data_validated may need to be set as well >> (and local packets are treated differently from off-host ones, to >> add an extra twist). > > The problem turned out to be that I was setting the flag for all > packets, including ARPs. > Getting this to work properly will require so API changes, because > NETWORK needs to tell the ethernet driver which types of packet can be > offloaded, and let the driver say which packets require checksums to > be added. > > Then similar changes are needed to ETHIF. Here are the hacks I used to test it: > > https://github.com/talex5/mirage/commits/csum-offload > https://github.com/talex5/mirage-net-xen/commits/csum-offload > https://github.com/talex5/mirage-tcpip/commits/csum-offload Looks good -- since V2.mli isn't tagged yet, this can just extend the call to `write` instead of having a `write2`. 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. A pull request to mirage/mirage of the WIP patches would be good to track this in the issue tracker. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 15:16:45 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 15:16: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 1XJl9P-0002QL-6S; Tue, 19 Aug 2014 15:16:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJl9O-0002QG-BC for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 15:16:42 +0000 Received: from [193.109.254.147:64762] by server-6.bemta-14.messagelabs.com id 41/2A-31278-95A63F35; Tue, 19 Aug 2014 15:16:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1408461392!11837321!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 13991 invoked from network); 19 Aug 2014 15:16:32 -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; 19 Aug 2014 15:16:32 -0000 Received: (qmail 13553 invoked by uid 634); 19 Aug 2014 15:16:32 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from Unknown (HELO [172.18.15.137]) (208.59.64.2) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 16:16:31 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 19 Aug 2014 10:07:00 -0500 Message-Id: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@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] 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 Aug 2014, at 09:32, Thomas Leonard wrote: > On 19 August 2014 11:18, Anil Madhavapeddy wrote: >> >> On 19 Aug 2014, at 05:08, Thomas Leonard wrote: >> >>> I see Xen allows guests to indicate that the packet checksum is blank >>> (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or >>> get the NIC to do it. How can I use this with Mirage? >>> >>> I tried using ~flags:3 (Checksum_blank + Data_validated) in >>> mirage-net-xen's netif.ml, but I don't see any TCP packets at all this >>> way, even when the checksum is actually still being set. DHCP still >>> works, though. >>> >>> Does anyone know how this is supposed to work? >> >> Probably best to trace through what netback is doing here: >> http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 >> >> Looks like XEN_NETTXF_data_validated may need to be set as well >> (and local packets are treated differently from off-host ones, to >> add an extra twist). > > The problem turned out to be that I was setting the flag for all > packets, including ARPs. > Getting this to work properly will require so API changes, because > NETWORK needs to tell the ethernet driver which types of packet can be > offloaded, and let the driver say which packets require checksums to > be added. > > Then similar changes are needed to ETHIF. Here are the hacks I used to test it: > > https://github.com/talex5/mirage/commits/csum-offload > https://github.com/talex5/mirage-net-xen/commits/csum-offload > https://github.com/talex5/mirage-tcpip/commits/csum-offload Looks good -- since V2.mli isn't tagged yet, this can just extend the call to `write` instead of having a `write2`. 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. A pull request to mirage/mirage of the WIP patches would be good to track this in the issue tracker. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 15:34:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 15:34: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 1XJlQE-0002YN-IL; Tue, 19 Aug 2014 15:34:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJlQD-0002YI-Nl for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 15:34:05 +0000 Received: from [193.109.254.147:53052] by server-2.bemta-14.messagelabs.com id 9C/47-09196-D6E63F35; Tue, 19 Aug 2014 15:34:05 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1408462442!11841590!1 X-Originating-IP: [209.85.214.169] 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 24724 invoked from network); 19 Aug 2014 15:34:03 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 15:34:03 -0000 Received: by mail-ob0-f169.google.com with SMTP id uz6so3270610obc.14 for ; Tue, 19 Aug 2014 08:34: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=OWIKJFLhQP3fEaUEQv9tE+zrTL+3yblNTk4i1ZfN0vA=; b=aP6KsacIOK+7sGP7VT/MCFp2ty3xUvH3fIvkyqAOeHUOGo6jlUTbn8+43tFZ7gFDwO vVjMPtuEL/YBKpzVq8G00LXUHdal9youFcdnd5El8RcEDV3hbwUe5jngzR54lOaoZqZ8 Oyw95bAtFYKTqyaxH64VTZe9zTUpOdzEytSzgJbWDkd/arLaKHbMci6wJQ13v93YPl5k 51jBwSD5NI16+Gok35GeMLWfCx8K9z49qFn1KJxzqgu/BfBJ7rc01iPR/nWogZIZ7mEX 9FRY1ACotzogMrRDZ8QJjSZOh8kf1zK05D0M0/cj+rluWv7Oc3HAgiQSNiCm0JnZA06p fzSw== MIME-Version: 1.0 X-Received: by 10.182.24.101 with SMTP id t5mr42744867obf.31.1408462442337; Tue, 19 Aug 2014 08:34:02 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Tue, 19 Aug 2014 08:34:02 -0700 (PDT) In-Reply-To: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> Date: Tue, 19 Aug 2014 16:34:02 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "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 16:07, Anil Madhavapeddy wrote: > On 19 Aug 2014, at 09:32, Thomas Leonard wrote: > >> On 19 August 2014 11:18, Anil Madhavapeddy wrote: >>> >>> On 19 Aug 2014, at 05:08, Thomas Leonard wrote: >>> >>>> I see Xen allows guests to indicate that the packet checksum is blank >>>> (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or >>>> get the NIC to do it. How can I use this with Mirage? >>>> >>>> I tried using ~flags:3 (Checksum_blank + Data_validated) in >>>> mirage-net-xen's netif.ml, but I don't see any TCP packets at all this >>>> way, even when the checksum is actually still being set. DHCP still >>>> works, though. >>>> >>>> Does anyone know how this is supposed to work? >>> >>> Probably best to trace through what netback is doing here: >>> http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 >>> >>> Looks like XEN_NETTXF_data_validated may need to be set as well >>> (and local packets are treated differently from off-host ones, to >>> add an extra twist). >> >> The problem turned out to be that I was setting the flag for all >> packets, including ARPs. >> Getting this to work properly will require so API changes, because >> NETWORK needs to tell the ethernet driver which types of packet can be >> offloaded, and let the driver say which packets require checksums to >> be added. >> >> Then similar changes are needed to ETHIF. Here are the hacks I used to test it: >> >> https://github.com/talex5/mirage/commits/csum-offload >> https://github.com/talex5/mirage-net-xen/commits/csum-offload >> https://github.com/talex5/mirage-tcpip/commits/csum-offload > > 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. > 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 pull request to mirage/mirage of the WIP patches would be good to track > this in the issue tracker. Done: https://github.com/mirage/mirage/pull/286 -- 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 Tue Aug 19 15:34:08 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 15:34: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 1XJlQE-0002YN-IL; Tue, 19 Aug 2014 15:34:06 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJlQD-0002YI-Nl for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 15:34:05 +0000 Received: from [193.109.254.147:53052] by server-2.bemta-14.messagelabs.com id 9C/47-09196-D6E63F35; Tue, 19 Aug 2014 15:34:05 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1408462442!11841590!1 X-Originating-IP: [209.85.214.169] 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 24724 invoked from network); 19 Aug 2014 15:34:03 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 15:34:03 -0000 Received: by mail-ob0-f169.google.com with SMTP id uz6so3270610obc.14 for ; Tue, 19 Aug 2014 08:34: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=OWIKJFLhQP3fEaUEQv9tE+zrTL+3yblNTk4i1ZfN0vA=; b=aP6KsacIOK+7sGP7VT/MCFp2ty3xUvH3fIvkyqAOeHUOGo6jlUTbn8+43tFZ7gFDwO vVjMPtuEL/YBKpzVq8G00LXUHdal9youFcdnd5El8RcEDV3hbwUe5jngzR54lOaoZqZ8 Oyw95bAtFYKTqyaxH64VTZe9zTUpOdzEytSzgJbWDkd/arLaKHbMci6wJQ13v93YPl5k 51jBwSD5NI16+Gok35GeMLWfCx8K9z49qFn1KJxzqgu/BfBJ7rc01iPR/nWogZIZ7mEX 9FRY1ACotzogMrRDZ8QJjSZOh8kf1zK05D0M0/cj+rluWv7Oc3HAgiQSNiCm0JnZA06p fzSw== MIME-Version: 1.0 X-Received: by 10.182.24.101 with SMTP id t5mr42744867obf.31.1408462442337; Tue, 19 Aug 2014 08:34:02 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Tue, 19 Aug 2014 08:34:02 -0700 (PDT) In-Reply-To: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> Date: Tue, 19 Aug 2014 16:34:02 +0100 Message-ID: From: Thomas Leonard To: Anil Madhavapeddy Cc: "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 16:07, Anil Madhavapeddy wrote: > On 19 Aug 2014, at 09:32, Thomas Leonard wrote: > >> On 19 August 2014 11:18, Anil Madhavapeddy wrote: >>> >>> On 19 Aug 2014, at 05:08, Thomas Leonard wrote: >>> >>>> I see Xen allows guests to indicate that the packet checksum is blank >>>> (XEN_NETTXF_csum_blank). Then dom0 will either fill it in itself or >>>> get the NIC to do it. How can I use this with Mirage? >>>> >>>> I tried using ~flags:3 (Checksum_blank + Data_validated) in >>>> mirage-net-xen's netif.ml, but I don't see any TCP packets at all this >>>> way, even when the checksum is actually still being set. DHCP still >>>> works, though. >>>> >>>> Does anyone know how this is supposed to work? >>> >>> Probably best to trace through what netback is doing here: >>> http://lxr.free-electrons.com/source/drivers/net/xen-netback/netback.c#L1580 >>> >>> Looks like XEN_NETTXF_data_validated may need to be set as well >>> (and local packets are treated differently from off-host ones, to >>> add an extra twist). >> >> The problem turned out to be that I was setting the flag for all >> packets, including ARPs. >> Getting this to work properly will require so API changes, because >> NETWORK needs to tell the ethernet driver which types of packet can be >> offloaded, and let the driver say which packets require checksums to >> be added. >> >> Then similar changes are needed to ETHIF. Here are the hacks I used to test it: >> >> https://github.com/talex5/mirage/commits/csum-offload >> https://github.com/talex5/mirage-net-xen/commits/csum-offload >> https://github.com/talex5/mirage-tcpip/commits/csum-offload > > 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. > 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 pull request to mirage/mirage of the WIP patches would be good to track > this in the issue tracker. Done: https://github.com/mirage/mirage/pull/286 -- 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 Tue Aug 19 16:26:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 16:26: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 1XJmFH-0003jr-Kx; Tue, 19 Aug 2014 16:26:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJmFF-0003jT-Kx for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 16:26:49 +0000 Received: from [85.158.137.68:4552] by server-16.bemta-3.messagelabs.com id BC/16-08587-8CA73F35; Tue, 19 Aug 2014 16:26:48 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1408465607!12129214!1 X-Originating-IP: [74.125.82.44] 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 6152 invoked from network); 19 Aug 2014 16:26:47 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 16:26:47 -0000 Received: by mail-wg0-f44.google.com with SMTP id m15so6541859wgh.3 for ; Tue, 19 Aug 2014 09:26:47 -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=0BXoamxDv9wjaw+x48ezPLpAt/BC/Wx6iqWmRQRcdok=; b=jVDNA/D/YXb7iDuWlrEMFa6CYal/rb+OylGeR7DK3EM3a0/0O3QHIKCyyFu6awFZsn lYiw8GHrhz8yR34hYijhQEDdloqIiVCLYvB2Woq1yCwQZmay2dhVxM0IRvZ8JvjTCubA wKV0DBgUgIq+4ax6LCdg3zhgdNjfS01WRHGa+AJhwITA8WXdxlugJ/YrGwq24DNyjBBN 1YhflYk8JRZ7fgxqYyS4byBpkD57V5+I9EXgxSqvnN4SLqz1f6JbfNNV1a1TyfVfbsLC JJHCIpLYFF88Rw8WE4LoiqExiVH6tfkWEq8RYheWbTuva1C4WzllqHJ0Z+c1YYHkemxK O5Qw== X-Received: by 10.194.119.41 with SMTP id kr9mr18723553wjb.114.1408465607464; Tue, 19 Aug 2014 09:26:47 -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 bi3sm37759258wib.6.2014.08.19.09.26.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Aug 2014 09:26:46 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> Date: Tue, 19 Aug 2014 17:26:45 +0100 Message-Id: <53C9FA12-8EE1-42E9-BD75-37BDE6FA6560@gazagnaire.org> References: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) Cc: Felipe Huici , mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >>> I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. >>> >>> Slides here: http://decks.openmirage.org/xendevsummit14#/ >>> Repo: https://github.com/mirage/mirage-decks as usual >>> >> >> [+xen-api-devel] Talk went well, quick notes here: >> >> - git workflow very popular. Lots of people twigged onto the maintainability benefits of `git bisect` automation in particular. >> >> - questions about why Xenstore transactions are still necessary in the modern world. Can replace with consensus protocols instead? Maybe time for an ABI bump to deprecate the ancient xenstore protocol. >> >> - space usage is a concern -- building an RRD-style constant size library to maintain progressive history would be a big win. A note on that: during his internship, Benjamin Farinier wrote a very simple backend for Irmin which maps Irmin objects to the OCaml heap directly[1], which means that 1/ no SHA1 needs to be computed (so it's fast) and 2/ we picky-bag the OCaml GC to collect Irmin objects. I think this is a good base for an in-memory store, we just need to understand how to expose it efficiently to the Git backend (ie. you don't want to recompute all the SHA1 on every export). But yes, having an RRD-style history is the way to go. [1] https://github.com/BFarinier/irmin/blob/master/examples/objAO.ml#L7 >> - *excellent* talk from Felipe Huici (CCed) from NEC about building much denser VM workloads, and he observed that Xenstored/xenconsoled are a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some sub notes: >> >> - we could write a mirage xenconsoled to log to irmin and drain guest console rings much faster. >> - a distributed xenstored+irmin would allow significantly more scalability than attempting to build a serially fast version. >> - felipe has the beginning of a simple c++ xenstored that doesn't implement the full semantics, but is enough for MiniOS. >> - it may be useful to negotiate a xenstore v2 protocol and use that for new guests. It could use a simple fixed-length binary protocol (protobuf-style?), and eliminate the need for transactions perhaps. > > sent 'send' too quickly. The most important point: > > - xenstore need consistent indices. Using domain names in the current stack results in a linear search through all domids -- very slow with 10000 VMs! Irmin could maintain a branch that updates a 'name -> domid' that is consistent within the transaction, and do constant time lookups for the toolstack. Irmin use persistent map to store sub-paths, so we already have logarithmic lookup (initially it was stored in a list, but my initial benchmarks pointed that as a bottleneck very quickly). Using maps is very efficient in practice. Thomas > > -anil > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 16:26:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 16:26: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 1XJmFH-0003jr-Kx; Tue, 19 Aug 2014 16:26:51 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJmFF-0003jT-Kx for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 16:26:49 +0000 Received: from [85.158.137.68:4552] by server-16.bemta-3.messagelabs.com id BC/16-08587-8CA73F35; Tue, 19 Aug 2014 16:26:48 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-31.messagelabs.com!1408465607!12129214!1 X-Originating-IP: [74.125.82.44] 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 6152 invoked from network); 19 Aug 2014 16:26:47 -0000 Received: from mail-wg0-f44.google.com (HELO mail-wg0-f44.google.com) (74.125.82.44) by server-14.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 16:26:47 -0000 Received: by mail-wg0-f44.google.com with SMTP id m15so6541859wgh.3 for ; Tue, 19 Aug 2014 09:26:47 -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=0BXoamxDv9wjaw+x48ezPLpAt/BC/Wx6iqWmRQRcdok=; b=jVDNA/D/YXb7iDuWlrEMFa6CYal/rb+OylGeR7DK3EM3a0/0O3QHIKCyyFu6awFZsn lYiw8GHrhz8yR34hYijhQEDdloqIiVCLYvB2Woq1yCwQZmay2dhVxM0IRvZ8JvjTCubA wKV0DBgUgIq+4ax6LCdg3zhgdNjfS01WRHGa+AJhwITA8WXdxlugJ/YrGwq24DNyjBBN 1YhflYk8JRZ7fgxqYyS4byBpkD57V5+I9EXgxSqvnN4SLqz1f6JbfNNV1a1TyfVfbsLC JJHCIpLYFF88Rw8WE4LoiqExiVH6tfkWEq8RYheWbTuva1C4WzllqHJ0Z+c1YYHkemxK O5Qw== X-Received: by 10.194.119.41 with SMTP id kr9mr18723553wjb.114.1408465607464; Tue, 19 Aug 2014 09:26:47 -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 bi3sm37759258wib.6.2014.08.19.09.26.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Aug 2014 09:26:46 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> Date: Tue, 19 Aug 2014 17:26:45 +0100 Message-Id: <53C9FA12-8EE1-42E9-BD75-37BDE6FA6560@gazagnaire.org> References: <5C05B2BA-CF52-4CFE-9D83-3E4A14E7EA2C@recoil.org> <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) Cc: Felipe Huici , mirageos-devel@lists.xenproject.org, xen-api@lists.xen.org Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >>> I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on the work that we've (primarily Dave Scott and Thomas Gazagnaire) on improving the Xenstore via Irmin features. >>> >>> Slides here: http://decks.openmirage.org/xendevsummit14#/ >>> Repo: https://github.com/mirage/mirage-decks as usual >>> >> >> [+xen-api-devel] Talk went well, quick notes here: >> >> - git workflow very popular. Lots of people twigged onto the maintainability benefits of `git bisect` automation in particular. >> >> - questions about why Xenstore transactions are still necessary in the modern world. Can replace with consensus protocols instead? Maybe time for an ABI bump to deprecate the ancient xenstore protocol. >> >> - space usage is a concern -- building an RRD-style constant size library to maintain progressive history would be a big win. A note on that: during his internship, Benjamin Farinier wrote a very simple backend for Irmin which maps Irmin objects to the OCaml heap directly[1], which means that 1/ no SHA1 needs to be computed (so it's fast) and 2/ we picky-bag the OCaml GC to collect Irmin objects. I think this is a good base for an in-memory store, we just need to understand how to expose it efficiently to the Git backend (ie. you don't want to recompute all the SHA1 on every export). But yes, having an RRD-style history is the way to go. [1] https://github.com/BFarinier/irmin/blob/master/examples/objAO.ml#L7 >> - *excellent* talk from Felipe Huici (CCed) from NEC about building much denser VM workloads, and he observed that Xenstored/xenconsoled are a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some sub notes: >> >> - we could write a mirage xenconsoled to log to irmin and drain guest console rings much faster. >> - a distributed xenstored+irmin would allow significantly more scalability than attempting to build a serially fast version. >> - felipe has the beginning of a simple c++ xenstored that doesn't implement the full semantics, but is enough for MiniOS. >> - it may be useful to negotiate a xenstore v2 protocol and use that for new guests. It could use a simple fixed-length binary protocol (protobuf-style?), and eliminate the need for transactions perhaps. > > sent 'send' too quickly. The most important point: > > - xenstore need consistent indices. Using domain names in the current stack results in a linear search through all domids -- very slow with 10000 VMs! Irmin could maintain a branch that updates a 'name -> domid' that is consistent within the transaction, and do constant time lookups for the toolstack. Irmin use persistent map to store sub-paths, so we already have logarithmic lookup (initially it was stored in a list, but my initial benchmarks pointed that as a bottleneck very quickly). Using maps is very efficient in practice. Thomas > > -anil > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 17:16:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 17:16: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 1XJn1B-0004va-3H; Tue, 19 Aug 2014 17:16:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJn1A-0004vV-5K for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 17:16:20 +0000 Received: from [85.158.143.35:3970] by server-3.bemta-4.messagelabs.com id 07/C7-06192-36683F35; Tue, 19 Aug 2014 17:16:19 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-15.tower-21.messagelabs.com!1408468578!11953028!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 1446 invoked from network); 19 Aug 2014 17:16:18 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Aug 2014 17:16:18 -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=44247 helo=[10.80.3.75]) 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 1XJn18-00071w-qZ (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 19 Aug 2014 18:16:18 +0100 Message-ID: <53F38661.5000709@cam.ac.uk> Date: Tue, 19 Aug 2014 18:16:17 +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: In-Reply-To: Subject: Re: [MirageOS-devel] MirageOS KVM Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19/08/14 14:58, Anil Madhavapeddy wrote: > On 19 Aug 2014, at 08:54, Bill Gercken wrote: > >> Hello, >> >> Is anybody actively working on support for KVM? >> >> We are in a situation where we need to deploy to both Xen and KVM and I would love to be able to create unikernel applications that can be compiled for both environments. >> > KVM is not specifically being worked on at this time, but we'd love to hear from anyone that would like to contribute towards the effort. There have been several recent developments to make this easier in Mirage 2: > > - the MiniOS library is now picked up from an external package > - this library is in sync with the Xen development tree (should be part of Xen 4.5) and is multiarch (x86_64/x86_32 and ARM). > - TODO: add a HVM boot mode to upstream MiniOS to let it boot in Xen hardware virt mode (Jon Ludlam had some patches against an earlier MiniOS that did this). Mostly what I did was forward-port some earlier patches by Dave Scott. The branch is here: https://github.com/jonludlam/mirage-platform/tree/hvm. What we did back then was use Pure64 to bootstrap, which leaves you in an environment all set up, so we just skipped out some of the mini-os setup. I now think it would be much better to do a full-on multiboot compliant kernel. I suspect it's actually relatively straightforward for Xen, since all we really need to do is set up the memory map (parsing e820 & co.) - I don't think we need to worry about interrupts (I think) as that can all be done via 'block domain' calls as we do with PV (as hvmloader does). For KVM you'd presumably need to do a bit more with the IDTs and making interrupt routines and whatnot. Having said that, it'd be really nice to do the interrupts stuff; writing some nice type-safe PCI drivers would be fun :-) Jon > After this, KVM support is pretty easy; it just needs the addition of virtio drivers in OCaml, which isn't a complex task. > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 17:16:22 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 17:16: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 1XJn1B-0004va-3H; Tue, 19 Aug 2014 17:16:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJn1A-0004vV-5K for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 17:16:20 +0000 Received: from [85.158.143.35:3970] by server-3.bemta-4.messagelabs.com id 07/C7-06192-36683F35; Tue, 19 Aug 2014 17:16:19 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-15.tower-21.messagelabs.com!1408468578!11953028!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 1446 invoked from network); 19 Aug 2014 17:16:18 -0000 Received: from ppsw-50.csi.cam.ac.uk (HELO ppsw-50.csi.cam.ac.uk) (131.111.8.150) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Aug 2014 17:16:18 -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=44247 helo=[10.80.3.75]) 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 1XJn18-00071w-qZ (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 19 Aug 2014 18:16:18 +0100 Message-ID: <53F38661.5000709@cam.ac.uk> Date: Tue, 19 Aug 2014 18:16:17 +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: In-Reply-To: Subject: Re: [MirageOS-devel] MirageOS KVM Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19/08/14 14:58, Anil Madhavapeddy wrote: > On 19 Aug 2014, at 08:54, Bill Gercken wrote: > >> Hello, >> >> Is anybody actively working on support for KVM? >> >> We are in a situation where we need to deploy to both Xen and KVM and I would love to be able to create unikernel applications that can be compiled for both environments. >> > KVM is not specifically being worked on at this time, but we'd love to hear from anyone that would like to contribute towards the effort. There have been several recent developments to make this easier in Mirage 2: > > - the MiniOS library is now picked up from an external package > - this library is in sync with the Xen development tree (should be part of Xen 4.5) and is multiarch (x86_64/x86_32 and ARM). > - TODO: add a HVM boot mode to upstream MiniOS to let it boot in Xen hardware virt mode (Jon Ludlam had some patches against an earlier MiniOS that did this). Mostly what I did was forward-port some earlier patches by Dave Scott. The branch is here: https://github.com/jonludlam/mirage-platform/tree/hvm. What we did back then was use Pure64 to bootstrap, which leaves you in an environment all set up, so we just skipped out some of the mini-os setup. I now think it would be much better to do a full-on multiboot compliant kernel. I suspect it's actually relatively straightforward for Xen, since all we really need to do is set up the memory map (parsing e820 & co.) - I don't think we need to worry about interrupts (I think) as that can all be done via 'block domain' calls as we do with PV (as hvmloader does). For KVM you'd presumably need to do a bit more with the IDTs and making interrupt routines and whatnot. Having said that, it'd be really nice to do the interrupts stuff; writing some nice type-safe PCI drivers would be fun :-) Jon > After this, KVM support is pretty easy; it just needs the addition of virtio drivers in OCaml, which isn't a complex task. > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 17:25:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 17:25: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 1XJnAS-00050N-T4; Tue, 19 Aug 2014 17:25:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJnAR-00050I-M2 for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 17:25:55 +0000 Received: from [85.158.137.68:32239] by server-3.bemta-3.messagelabs.com id 1C/40-22751-2A883F35; Tue, 19 Aug 2014 17:25:54 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1408469154!14464869!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12340 invoked from network); 19 Aug 2014 17:25:54 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-15.tower-31.messagelabs.com with SMTP; 19 Aug 2014 17:25:54 -0000 X-IronPort-AV: E=Sophos;i="5.01,896,1400025600"; d="scan'208";a="24085105" From: Dave Scott To: Jon Ludlam Thread-Topic: [MirageOS-devel] MirageOS KVM Development Thread-Index: AQHPu7U1+B6wbfJb+0iXfkzkUa70FpvX0nKAgAA3L4CAAAKrAA== Date: Tue, 19 Aug 2014 17:25:52 +0000 Message-ID: References: <53F38661.5000709@cam.ac.uk> In-Reply-To: <53F38661.5000709@cam.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <1C0D94591BBBFE4E9DEA4C003CB1DB68@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] MirageOS KVM Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19 Aug 2014, at 18:16, Jon Ludlam wrote: > On 19/08/14 14:58, Anil Madhavapeddy wrote: >> On 19 Aug 2014, at 08:54, Bill Gercken wrote: >> = >>> Hello, >>> = >>> Is anybody actively working on support for KVM? >>> = >>> We are in a situation where we need to deploy to both Xen and KVM and I= would love to be able to create unikernel applications that can be compile= d for both environments. >>> = >> KVM is not specifically being worked on at this time, but we'd love to h= ear from anyone that would like to contribute towards the effort. There ha= ve been several recent developments to make this easier in Mirage 2: >> = >> - the MiniOS library is now picked up from an external package >> - this library is in sync with the Xen development tree (should be part = of Xen 4.5) and is multiarch (x86_64/x86_32 and ARM). >> - TODO: add a HVM boot mode to upstream MiniOS to let it boot in Xen har= dware virt mode (Jon Ludlam had some patches against an earlier MiniOS that= did this). > = > Mostly what I did was forward-port some earlier patches by Dave Scott. > The branch is here: https://github.com/jonludlam/mirage-platform/tree/hvm. > = > What we did back then was use Pure64 to bootstrap, which leaves you in > an environment all set up, so we just skipped out some of the mini-os > setup. I now think it would be much better to do a full-on multiboot > compliant kernel. I suspect it's actually relatively straightforward for > Xen, since all we really need to do is set up the memory map (parsing > e820 & co.) - I don't think we need to worry about interrupts (I think) > as that can all be done via 'block domain' calls as we do with PV (as > hvmloader does). For KVM you'd presumably need to do a bit more with the > IDTs and making interrupt routines and whatnot. > = > Having said that, it'd be really nice to do the interrupts stuff; > writing some nice type-safe PCI drivers would be fun :-) For this we might be able to share some code with =91snowflake OS=92: https://code.google.com/p/snowflake-os/ The code looks interesting, for example: kernel djs$ ls *.mli DMA.mli interrupts.mli ELF.mli ircTypes.mli ICH0.mli keyboard.mli IDE.mli linkerTest.mli PCI.mli multiboot.mli asm.mli networkProtocolStack.mli audioMixer.mli networkStack.mli blockIO.mli objectFile.mli debug.mli partitions.mli deviceManager.mli realTek8139.mli dhcpClient.mli sb16.mli e1000.mli snowflake.mli elfLinking.mli tarFile.mli elfParsing.mli trie.mli elfPrinting.mli tulip.mli elfTypes.mli vga.mli kernel djs$ grep probe PCI* PCI.ml:let probe bus device funct =3D PCI.ml:let probe_bus () =3D PCI.ml: list :=3D probe i j 0 :: !list PCI.mli:val probe : int -> int -> int -> device PCI.mli:val probe_bus : unit -> device list Cheers, Dave > = > Jon > = > = >> After this, KVM support is pretty easy; it just needs the addition of vi= rtio drivers in OCaml, which isn't a complex task. >> = >> -anil >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > = > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 17:25:58 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 17:25: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 1XJnAS-00050N-T4; Tue, 19 Aug 2014 17:25:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJnAR-00050I-M2 for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 17:25:55 +0000 Received: from [85.158.137.68:32239] by server-3.bemta-3.messagelabs.com id 1C/40-22751-2A883F35; Tue, 19 Aug 2014 17:25:54 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-15.tower-31.messagelabs.com!1408469154!14464869!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12340 invoked from network); 19 Aug 2014 17:25:54 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-15.tower-31.messagelabs.com with SMTP; 19 Aug 2014 17:25:54 -0000 X-IronPort-AV: E=Sophos;i="5.01,896,1400025600"; d="scan'208";a="24085105" From: Dave Scott To: Jon Ludlam Thread-Topic: [MirageOS-devel] MirageOS KVM Development Thread-Index: AQHPu7U1+B6wbfJb+0iXfkzkUa70FpvX0nKAgAA3L4CAAAKrAA== Date: Tue, 19 Aug 2014 17:25:52 +0000 Message-ID: References: <53F38661.5000709@cam.ac.uk> In-Reply-To: <53F38661.5000709@cam.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <1C0D94591BBBFE4E9DEA4C003CB1DB68@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] MirageOS KVM Development X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 19 Aug 2014, at 18:16, Jon Ludlam wrote: > On 19/08/14 14:58, Anil Madhavapeddy wrote: >> On 19 Aug 2014, at 08:54, Bill Gercken wrote: >> = >>> Hello, >>> = >>> Is anybody actively working on support for KVM? >>> = >>> We are in a situation where we need to deploy to both Xen and KVM and I= would love to be able to create unikernel applications that can be compile= d for both environments. >>> = >> KVM is not specifically being worked on at this time, but we'd love to h= ear from anyone that would like to contribute towards the effort. There ha= ve been several recent developments to make this easier in Mirage 2: >> = >> - the MiniOS library is now picked up from an external package >> - this library is in sync with the Xen development tree (should be part = of Xen 4.5) and is multiarch (x86_64/x86_32 and ARM). >> - TODO: add a HVM boot mode to upstream MiniOS to let it boot in Xen har= dware virt mode (Jon Ludlam had some patches against an earlier MiniOS that= did this). > = > Mostly what I did was forward-port some earlier patches by Dave Scott. > The branch is here: https://github.com/jonludlam/mirage-platform/tree/hvm. > = > What we did back then was use Pure64 to bootstrap, which leaves you in > an environment all set up, so we just skipped out some of the mini-os > setup. I now think it would be much better to do a full-on multiboot > compliant kernel. I suspect it's actually relatively straightforward for > Xen, since all we really need to do is set up the memory map (parsing > e820 & co.) - I don't think we need to worry about interrupts (I think) > as that can all be done via 'block domain' calls as we do with PV (as > hvmloader does). For KVM you'd presumably need to do a bit more with the > IDTs and making interrupt routines and whatnot. > = > Having said that, it'd be really nice to do the interrupts stuff; > writing some nice type-safe PCI drivers would be fun :-) For this we might be able to share some code with =91snowflake OS=92: https://code.google.com/p/snowflake-os/ The code looks interesting, for example: kernel djs$ ls *.mli DMA.mli interrupts.mli ELF.mli ircTypes.mli ICH0.mli keyboard.mli IDE.mli linkerTest.mli PCI.mli multiboot.mli asm.mli networkProtocolStack.mli audioMixer.mli networkStack.mli blockIO.mli objectFile.mli debug.mli partitions.mli deviceManager.mli realTek8139.mli dhcpClient.mli sb16.mli e1000.mli snowflake.mli elfLinking.mli tarFile.mli elfParsing.mli trie.mli elfPrinting.mli tulip.mli elfTypes.mli vga.mli kernel djs$ grep probe PCI* PCI.ml:let probe bus device funct =3D PCI.ml:let probe_bus () =3D PCI.ml: list :=3D probe i j 0 :: !list PCI.mli:val probe : int -> int -> int -> device PCI.mli:val probe_bus : unit -> device list Cheers, Dave > = > Jon > = > = >> After this, KVM support is pretty easy; it just needs the addition of vi= rtio drivers in OCaml, which isn't a complex task. >> = >> -anil >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > = > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Aug 19 19:26:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 19:26: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 1XJp2t-0005rh-KU; Tue, 19 Aug 2014 19:26:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJp2s-0005ra-Ov for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 19:26:14 +0000 Received: from [193.109.254.147:11089] by server-10.bemta-14.messagelabs.com id 36/93-06615-6D4A3F35; Tue, 19 Aug 2014 19:26:14 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1408476373!11850105!1 X-Originating-IP: [74.125.82.43] 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 14705 invoked from network); 19 Aug 2014 19:26:13 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 19:26:13 -0000 Received: by mail-wg0-f43.google.com with SMTP id l18so6794526wgh.26 for ; Tue, 19 Aug 2014 12:26:12 -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=rSdM1/iqr2/FnanMkovgowkjrLGpVlC8RK2iVc9yTY0=; b=llDN0PMb6BrwKp/X1aXYvMRYoW1qc4h3US9CYtIzf+90GLtGn4F+ABAHBdZYdMVKb8 TOpYsjtzSkV9QUDpIVRZU7ulbLOHsRP5QgGUKQ9PI/gcTEGAI/tcb8NnI7bstHW55B2c 0+KsJ1a75juGNe//PlWOAxDtcYAyIiPC+Oaw5JuQ9Z0gbi4bnQ13UXpru1DvFtFIsdmd WKLvKtzFBjK0EZjpTBiSD2xxEu6iPc9zUZFsS3nuC3EQc18uZg/izGz0c8LFZeDdkzK+ iwKpeum+JvwXmUUBw2/Bu6+QQ3T+4vl7fscPGrA0VIAa5U1zP+ZI5znGXKreVudXxWYo lINQ== X-Received: by 10.180.39.73 with SMTP id n9mr9088069wik.70.1408476372807; Tue, 19 Aug 2014 12:26:12 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id c8sm52621534wjw.6.2014.08.19.12.26.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Aug 2014 12:26:10 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 19 Aug 2014 20:26:09 +0100 Message-Id: <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) Cc: "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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> 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. Thomas >> A pull request to mirage/mirage of the WIP patches would be good to track >> this in the issue tracker. > > Done: > > https://github.com/mirage/mirage/pull/286 > > > -- > 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 _______________________________________________ MirageOS-devel 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 Aug 19 19:26:20 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 19:26: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 1XJp2t-0005rh-KU; Tue, 19 Aug 2014 19:26:15 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJp2s-0005ra-Ov for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 19:26:14 +0000 Received: from [193.109.254.147:11089] by server-10.bemta-14.messagelabs.com id 36/93-06615-6D4A3F35; Tue, 19 Aug 2014 19:26:14 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1408476373!11850105!1 X-Originating-IP: [74.125.82.43] 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 14705 invoked from network); 19 Aug 2014 19:26:13 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 19 Aug 2014 19:26:13 -0000 Received: by mail-wg0-f43.google.com with SMTP id l18so6794526wgh.26 for ; Tue, 19 Aug 2014 12:26:12 -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=rSdM1/iqr2/FnanMkovgowkjrLGpVlC8RK2iVc9yTY0=; b=llDN0PMb6BrwKp/X1aXYvMRYoW1qc4h3US9CYtIzf+90GLtGn4F+ABAHBdZYdMVKb8 TOpYsjtzSkV9QUDpIVRZU7ulbLOHsRP5QgGUKQ9PI/gcTEGAI/tcb8NnI7bstHW55B2c 0+KsJ1a75juGNe//PlWOAxDtcYAyIiPC+Oaw5JuQ9Z0gbi4bnQ13UXpru1DvFtFIsdmd WKLvKtzFBjK0EZjpTBiSD2xxEu6iPc9zUZFsS3nuC3EQc18uZg/izGz0c8LFZeDdkzK+ iwKpeum+JvwXmUUBw2/Bu6+QQ3T+4vl7fscPGrA0VIAa5U1zP+ZI5znGXKreVudXxWYo lINQ== X-Received: by 10.180.39.73 with SMTP id n9mr9088069wik.70.1408476372807; Tue, 19 Aug 2014 12:26:12 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id c8sm52621534wjw.6.2014.08.19.12.26.10 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Aug 2014 12:26:10 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 19 Aug 2014 20:26:09 +0100 Message-Id: <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) Cc: "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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> 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. Thomas >> A pull request to mirage/mirage of the WIP patches would be good to track >> this in the issue tracker. > > Done: > > https://github.com/mirage/mirage/pull/286 > > > -- > 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 _______________________________________________ MirageOS-devel 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 Aug 19 19:28:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 19:28: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 1XJp5T-0005yg-Ss; Tue, 19 Aug 2014 19:28:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJp5S-0005yb-Vi for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 19:28:55 +0000 Received: from [85.158.137.68:56035] by server-3.bemta-3.messagelabs.com id 54/DF-22751-575A3F35; Tue, 19 Aug 2014 19:28:53 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-31.messagelabs.com!1408476532!12151431!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 7905 invoked from network); 19 Aug 2014 19:28:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-31.messagelabs.com with SMTP; 19 Aug 2014 19:28:52 -0000 Received: (qmail 21695 invoked by uid 634); 19 Aug 2014 19:28:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from sheratonips43.s.subnet.rcn.com (HELO sheratonips43.s.subnet.rcn.com) (216.80.65.42) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 20:28:51 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> Date: Tue, 19 Aug 2014 14:28:50 -0500 Message-Id: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> To: Thomas Gazagnaire 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] 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 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. Agreed on both counts... -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 Aug 19 19:28:55 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 19 Aug 2014 19:28: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 1XJp5T-0005yg-Ss; Tue, 19 Aug 2014 19:28:55 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XJp5S-0005yb-Vi for mirageos-devel@lists.xenproject.org; Tue, 19 Aug 2014 19:28:55 +0000 Received: from [85.158.137.68:56035] by server-3.bemta-3.messagelabs.com id 54/DF-22751-575A3F35; Tue, 19 Aug 2014 19:28:53 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-31.messagelabs.com!1408476532!12151431!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 7905 invoked from network); 19 Aug 2014 19:28:52 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-31.messagelabs.com with SMTP; 19 Aug 2014 19:28:52 -0000 Received: (qmail 21695 invoked by uid 634); 19 Aug 2014 19:28:52 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from sheratonips43.s.subnet.rcn.com (HELO sheratonips43.s.subnet.rcn.com) (216.80.65.42) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 19 Aug 2014 20:28:51 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> Date: Tue, 19 Aug 2014 14:28:50 -0500 Message-Id: References: <1D1E6FA0-D4AA-4B30-B451-E345BAF187B3@recoil.org> <22715550-9A10-482D-9A66-BF818FBE4D50@gazagnaire.org> To: Thomas Gazagnaire 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] 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 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. Agreed on both counts... -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 Aug 20 09:28:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 09:28: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 1XK2Bv-0000In-HX; Wed, 20 Aug 2014 09:28:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK2Bu-0000If-5x for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 09:28:26 +0000 Received: from [85.158.139.211:25442] by server-15.bemta-5.messagelabs.com id 7E/AE-12002-93A64F35; Wed, 20 Aug 2014 09:28:25 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1408526904!6875651!1 X-Originating-IP: [209.85.212.175] 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 26293 invoked from network); 20 Aug 2014 09:28:24 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Aug 2014 09:28:24 -0000 Received: by mail-wi0-f175.google.com with SMTP id ho1so6747923wib.14 for ; Wed, 20 Aug 2014 02:28:24 -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=i3az4Hgw03hhYc3JJ/+9O6c8JyUuGC6yM9mMmkxz0QY=; b=GWJn4RBp/uQUxgLZVyRLmvssUAbpaVwhgjajF59Hgo9fqxY6gNTf76CPh+S3/RTNee vOIw4XY0mr58v9vR4ii1/+Wvrd6MnT7hLcCwnhmUCNI9gO/KIiyWYG5jc+R7dgtsg4T+ 00j7aElnOblO9L65cjKSOJg0wJ2fBeC6VjSK2rBjw3As3BzCe+lkztqjzG+cFUAXEFrc wb/giNv4fgIodmAsB7aRPMQVOkyaxap6j9MoV/XWnC1Gwe4XKZAn2RueozMZbBtuFLYy i0PaulPaUAKeaiOSDoJMLQWV4Z/GqcaA84pIXMDayDP2nppYdjHAagIBaUsg+6iiWqy3 66tQ== X-Received: by 10.180.183.36 with SMTP id ej4mr13329265wic.77.1408526904145; Wed, 20 Aug 2014 02:28:24 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id a11sm57176772wjx.46.2014.08.20.02.28.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Aug 2014 02:28:23 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 20 Aug 2014 10:28:22 +0100 Message-Id: <9A23EE2B-493D-4FD4-9D1D-FC2D007B1F2D@gazagnaire.org> References: To: Gregory Tsipenyuk X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] papers on immutable storage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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/ the Mirage list as the list of pointers can be interested to other. Some talks to understand weak consistency models: - consistency models vs. baseball games: http://cacm.acm.org/magazines/2013/12/169945-replicated-data-consistency-explained-through-baseball/abstract - basho, immutability changes everything: http://vimeo.com/52831373 (a very short list) of related papers to branch consistency: - bayou: http://zoo.cs.yale.edu/classes/cs422/2013/bib/terry95managing.pdf - cloud type: http://research.microsoft.com/apps/pubs/default.aspx?id=163842 (and other papers of Burckhard around the fork/join model) To understand what values are created when a new entry is added: look at radix/prefix/suffix trie (or tries) papers - http://www.comp.nus.edu.sg/~stevenha/visualization/suffixtree.html# - http://en.wikipedia.org/wiki/Radix_tree Basically every block in a normal heap is translated to a new file (in the Git backend at least). Best, Thomas > Thomas, > > Can you recommend any reading on Irmin like database? I want to understand better the use-cases and how they are handled. I want specifically to look at two opposite cases, one where the database is distributed between many nodes and many clients write to it so concurrency and consistency are a challenge and another where there the database is on one node and only one client. > > Also what happens in Irmin backend when a new key/value is added? Is a new file created every time (if the value is different every time)? Is there support for encryption? > > Thanks, > > Gregory _______________________________________________ MirageOS-devel 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 Aug 20 09:28:32 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 09:28: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 1XK2Bv-0000In-HX; Wed, 20 Aug 2014 09:28:27 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK2Bu-0000If-5x for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 09:28:26 +0000 Received: from [85.158.139.211:25442] by server-15.bemta-5.messagelabs.com id 7E/AE-12002-93A64F35; Wed, 20 Aug 2014 09:28:25 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1408526904!6875651!1 X-Originating-IP: [209.85.212.175] 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 26293 invoked from network); 20 Aug 2014 09:28:24 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Aug 2014 09:28:24 -0000 Received: by mail-wi0-f175.google.com with SMTP id ho1so6747923wib.14 for ; Wed, 20 Aug 2014 02:28:24 -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=i3az4Hgw03hhYc3JJ/+9O6c8JyUuGC6yM9mMmkxz0QY=; b=GWJn4RBp/uQUxgLZVyRLmvssUAbpaVwhgjajF59Hgo9fqxY6gNTf76CPh+S3/RTNee vOIw4XY0mr58v9vR4ii1/+Wvrd6MnT7hLcCwnhmUCNI9gO/KIiyWYG5jc+R7dgtsg4T+ 00j7aElnOblO9L65cjKSOJg0wJ2fBeC6VjSK2rBjw3As3BzCe+lkztqjzG+cFUAXEFrc wb/giNv4fgIodmAsB7aRPMQVOkyaxap6j9MoV/XWnC1Gwe4XKZAn2RueozMZbBtuFLYy i0PaulPaUAKeaiOSDoJMLQWV4Z/GqcaA84pIXMDayDP2nppYdjHAagIBaUsg+6iiWqy3 66tQ== X-Received: by 10.180.183.36 with SMTP id ej4mr13329265wic.77.1408526904145; Wed, 20 Aug 2014 02:28:24 -0700 (PDT) Received: from [192.168.0.8] (cpc25-cmbg14-2-0-cust121.5-4.cable.virginm.net. [213.106.112.122]) by mx.google.com with ESMTPSA id a11sm57176772wjx.46.2014.08.20.02.28.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Aug 2014 02:28:23 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 20 Aug 2014 10:28:22 +0100 Message-Id: <9A23EE2B-493D-4FD4-9D1D-FC2D007B1F2D@gazagnaire.org> References: To: Gregory Tsipenyuk X-Mailer: Apple Mail (2.1878.6) Cc: mirageos-devel , Anil Madhavapeddy Subject: Re: [MirageOS-devel] papers on immutable storage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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/ the Mirage list as the list of pointers can be interested to other. Some talks to understand weak consistency models: - consistency models vs. baseball games: http://cacm.acm.org/magazines/2013/12/169945-replicated-data-consistency-explained-through-baseball/abstract - basho, immutability changes everything: http://vimeo.com/52831373 (a very short list) of related papers to branch consistency: - bayou: http://zoo.cs.yale.edu/classes/cs422/2013/bib/terry95managing.pdf - cloud type: http://research.microsoft.com/apps/pubs/default.aspx?id=163842 (and other papers of Burckhard around the fork/join model) To understand what values are created when a new entry is added: look at radix/prefix/suffix trie (or tries) papers - http://www.comp.nus.edu.sg/~stevenha/visualization/suffixtree.html# - http://en.wikipedia.org/wiki/Radix_tree Basically every block in a normal heap is translated to a new file (in the Git backend at least). Best, Thomas > Thomas, > > Can you recommend any reading on Irmin like database? I want to understand better the use-cases and how they are handled. I want specifically to look at two opposite cases, one where the database is distributed between many nodes and many clients write to it so concurrency and consistency are a challenge and another where there the database is on one node and only one client. > > Also what happens in Irmin backend when a new key/value is added? Is a new file created every time (if the value is different every time)? Is there support for encryption? > > Thanks, > > Gregory _______________________________________________ MirageOS-devel 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 Aug 20 10:04:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 10:04: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 1XK2ke-0000y8-CH; Wed, 20 Aug 2014 10:04:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK1q5-0000BJ-MZ for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 09:05:53 +0000 Received: from [85.158.143.35:21462] by server-1.bemta-4.messagelabs.com id 0A/1F-05872-1F464F35; Wed, 20 Aug 2014 09:05:53 +0000 X-Env-Sender: Felipe.Huici@neclab.eu X-Msg-Ref: server-16.tower-21.messagelabs.com!1408525551!8641102!1 X-Originating-IP: [195.37.70.40] 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 28238 invoked from network); 20 Aug 2014 09:05:51 -0000 Received: from mailer1.neclab.eu (HELO mailer1.neclab.eu) (195.37.70.40) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Aug 2014 09:05:51 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3ADDE107B29; Wed, 20 Aug 2014 11:05:51 +0200 (CEST) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUztuICx0qA7; Wed, 20 Aug 2014 11:05:51 +0200 (CEST) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 1A0D5100471; Wed, 20 Aug 2014 11:05:45 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.182]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 20 Aug 2014 11:05:44 +0200 From: Felipe Huici To: Anil Madhavapeddy , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Thread-Topic: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore Thread-Index: AQHPu7SbtlEGfUkxsEytUO/q2n8fypvXz1WAgAFlFoA= Date: Wed, 20 Aug 2014 09:05:44 +0000 Message-ID: In-Reply-To: <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 x-originating-ip: [10.1.99.81] Content-ID: <587D796215150A459C07ADFF3AD79C73@office.hd> MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 20 Aug 2014 10:04:19 +0000 Cc: Filipe Manco Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 SGkgQW5pbCwgYWxsLA0KDQpBcyBhIGNsYXJpZmljYXRpb24sIHRoZSB0YWxrIHdhcyBnaXZlbiBi eSBteSBjb2xsZWFndWUgRmlsaXBlIE1hbmNvLCBpbg0KY2MsIG5vdCBtZS4gSeKAmXZlIHRlbXBv cmFyaWx5IHBsYWNlZCB0aGUgc2xpZGVzIGF0Og0KDQpodHRwOi8vd3d3MC5jcy51Y2wuYWMudWsv c3RhZmYvZi5odWljaS9wcmVzZW50YXRpb25zL2NsaWNrb3MteGVuZGV2c3VtbWl0MTQNCi5wZGYN Cg0KVGhleSBzaG91bGQgYXBwZWFyIG9uIHRoZSBYZW4gc3VtbWl0IGJyaWVmbHksIGFuZCBtb3Jl IHBlcm1hbmVudGx5IG9uIG91cg0Kd2Vic2l0ZSBhdDoNCg0KaHR0cHM6Ly9jbnAubmVjbGFiLmV1 DQoNClRoYW5rcywNCg0K4oCUIEZlbGlwZQ0KDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCkRyLiBGZWxpcGUgSHVpY2kNClNlbmlv ciBSZXNlYXJjaGVyLCBOZXR3b3JrZWQgU3lzdGVtcyBhbmQgRGF0YQ0KQW5hbHl0aWNzIEdyb3Vw DQpORUMgTGFib3JhdG9yaWVzIEV1cm9wZSwgTmV0d29yayBSZXNlYXJjaCBEaXZpc2lvbg0KS3Vy ZnVlcnN0ZW5hbmxhZ2UgMzYsIEQtNjkxMTUgSGVpZGVsYmVyZw0KVGVsLiAgICAgKzQ5DQooMCk2 MjIxIDQzNDItMjQxDQpGYXg6ICAgICArNDkNCigwKTYyMjEgNDM0Mi0xNTUNCg0KZS1tYWlsOiAN CmZlbGlwZS5odWljaUBuZWNsYWIuZXUNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KTkVDIEV1cm9wZSBMaW1pdGVkIFJlZ2lzdGVy ZWQgT2ZmaWNlOiBORUMgSG91c2UsIDENClZpY3RvcmlhIFJvYWQsIExvbmRvbiBXMyA2QkwgUmVn aXN0ZXJlZCBpbiBFbmdsYW5kIDI4MzIwMTQNCg0KDQoNCg0KT24gOC8xOS8xNCwgMzo0NyBQTSwg IkFuaWwgTWFkaGF2YXBlZGR5IiA8YW5pbEByZWNvaWwub3JnPiB3cm90ZToNCg0KPk9uIDE5IEF1 ZyAyMDE0LCBhdCAwODo0NCwgQW5pbCBNYWRoYXZhcGVkZHkgPGFuaWxAcmVjb2lsLm9yZz4gd3Jv dGU6DQo+DQo+PiBPbiAxNyBBdWcgMjAxNCwgYXQgMTE6MDEsIEFuaWwgTWFkaGF2YXBlZGR5IDxh bmlsQHJlY29pbC5vcmc+IHdyb3RlOg0KPj4gDQo+Pj4gSSdtIGdpdmluZyBhIHRhbGsgYXQgdGhl IFhlbiBEZXZlbG9wZXIgU3VtbWl0IGF0IExpbnV4Y29uIHRvbW9ycm93IG9uDQo+Pj50aGUgd29y ayB0aGF0IHdlJ3ZlIChwcmltYXJpbHkgRGF2ZSBTY290dCBhbmQgVGhvbWFzIEdhemFnbmFpcmUp IG9uDQo+Pj5pbXByb3ZpbmcgdGhlIFhlbnN0b3JlIHZpYSBJcm1pbiBmZWF0dXJlcy4NCj4+PiAN Cj4+PiBTbGlkZXMgaGVyZTogaHR0cDovL2RlY2tzLm9wZW5taXJhZ2Uub3JnL3hlbmRldnN1bW1p dDE0Iy8NCj4+PiBSZXBvOiBodHRwczovL2dpdGh1Yi5jb20vbWlyYWdlL21pcmFnZS1kZWNrcyBh cyB1c3VhbA0KPj4+IA0KPj4gDQo+PiBbK3hlbi1hcGktZGV2ZWxdIFRhbGsgd2VudCB3ZWxsLCBx dWljayBub3RlcyBoZXJlOg0KPj4gDQo+PiAtIGdpdCB3b3JrZmxvdyB2ZXJ5IHBvcHVsYXIuIExv dHMgb2YgcGVvcGxlIHR3aWdnZWQgb250byB0aGUNCj4+bWFpbnRhaW5hYmlsaXR5IGJlbmVmaXRz IG9mIGBnaXQgYmlzZWN0YCBhdXRvbWF0aW9uIGluIHBhcnRpY3VsYXIuDQo+PiANCj4+IC0gcXVl c3Rpb25zIGFib3V0IHdoeSBYZW5zdG9yZSB0cmFuc2FjdGlvbnMgYXJlIHN0aWxsIG5lY2Vzc2Fy eSBpbiB0aGUNCj4+bW9kZXJuIHdvcmxkLiAgQ2FuIHJlcGxhY2Ugd2l0aCBjb25zZW5zdXMgcHJv dG9jb2xzIGluc3RlYWQ/ICBNYXliZSB0aW1lDQo+PmZvciBhbiBBQkkgYnVtcCB0byBkZXByZWNh dGUgdGhlIGFuY2llbnQgeGVuc3RvcmUgcHJvdG9jb2wuDQo+PiANCj4+IC0gc3BhY2UgdXNhZ2Ug aXMgYSBjb25jZXJuIC0tIGJ1aWxkaW5nIGFuIFJSRC1zdHlsZSBjb25zdGFudCBzaXplDQo+Pmxp YnJhcnkgdG8gbWFpbnRhaW4gcHJvZ3Jlc3NpdmUgaGlzdG9yeSB3b3VsZCBiZSBhIGJpZyB3aW4u DQo+PiANCj4+IC0gKmV4Y2VsbGVudCogdGFsayBmcm9tIEZlbGlwZSBIdWljaSAoQ0NlZCkgZnJv bSBORUMgYWJvdXQgYnVpbGRpbmcNCj4+bXVjaCBkZW5zZXIgVk0gd29ya2xvYWRzLCBhbmQgaGUg b2JzZXJ2ZWQgdGhhdCBYZW5zdG9yZWQveGVuY29uc29sZWQgYXJlDQo+PmEgYmlnIGJvdHRsZW5l Y2sgYXQgfjEwMDAwIFZNcy4gIEFyZSB5b3VyIHNsaWRlcyBhdmFpbGFibGUgRmVsaXBlPyAgU29t ZQ0KPj5zdWIgbm90ZXM6DQo+PiANCj4+IC0gd2UgY291bGQgd3JpdGUgYSBtaXJhZ2UgeGVuY29u c29sZWQgdG8gbG9nIHRvIGlybWluIGFuZCBkcmFpbiBndWVzdA0KPj5jb25zb2xlIHJpbmdzIG11 Y2ggZmFzdGVyLg0KPj4gLSBhIGRpc3RyaWJ1dGVkIHhlbnN0b3JlZCtpcm1pbiB3b3VsZCBhbGxv dyBzaWduaWZpY2FudGx5IG1vcmUNCj4+c2NhbGFiaWxpdHkgdGhhbiBhdHRlbXB0aW5nIHRvIGJ1 aWxkIGEgc2VyaWFsbHkgZmFzdCB2ZXJzaW9uLg0KPj4gLSBmZWxpcGUgaGFzIHRoZSBiZWdpbm5p bmcgb2YgYSBzaW1wbGUgYysrIHhlbnN0b3JlZCB0aGF0IGRvZXNuJ3QNCj4+aW1wbGVtZW50IHRo ZSBmdWxsIHNlbWFudGljcywgYnV0IGlzIGVub3VnaCBmb3IgTWluaU9TLg0KPj4gLSBpdCBtYXkg YmUgdXNlZnVsIHRvIG5lZ290aWF0ZSBhIHhlbnN0b3JlIHYyIHByb3RvY29sIGFuZCB1c2UgdGhh dCBmb3INCj4+bmV3IGd1ZXN0cy4gIEl0IGNvdWxkIHVzZSBhIHNpbXBsZSBmaXhlZC1sZW5ndGgg YmluYXJ5IHByb3RvY29sDQo+Pihwcm90b2J1Zi1zdHlsZT8pLCBhbmQgZWxpbWluYXRlIHRoZSBu ZWVkIGZvciB0cmFuc2FjdGlvbnMgcGVyaGFwcy4NCj4NCj5zZW50ICdzZW5kJyB0b28gcXVpY2ts eS4gIFRoZSBtb3N0IGltcG9ydGFudCBwb2ludDoNCj4NCj4tIHhlbnN0b3JlIG5lZWQgY29uc2lz dGVudCBpbmRpY2VzLiAgVXNpbmcgZG9tYWluIG5hbWVzIGluIHRoZSBjdXJyZW50DQo+c3RhY2sg cmVzdWx0cyBpbiBhIGxpbmVhciBzZWFyY2ggdGhyb3VnaCBhbGwgZG9taWRzIC0tIHZlcnkgc2xv dyB3aXRoDQo+MTAwMDAgVk1zISAgSXJtaW4gY291bGQgbWFpbnRhaW4gYSBicmFuY2ggdGhhdCB1 cGRhdGVzIGEgJ25hbWUgLT4gZG9taWQnDQo+dGhhdCBpcyBjb25zaXN0ZW50IHdpdGhpbiB0aGUg dHJhbnNhY3Rpb24sIGFuZCBkbyBjb25zdGFudCB0aW1lIGxvb2t1cHMNCj5mb3IgdGhlIHRvb2xz dGFjay4NCj4NCj4tYW5pbA0KPg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxA bGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4v bWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 10:04:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 10:04: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 1XK2ke-0000y8-CH; Wed, 20 Aug 2014 10:04:20 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK1q5-0000BJ-MZ for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 09:05:53 +0000 Received: from [85.158.143.35:21462] by server-1.bemta-4.messagelabs.com id 0A/1F-05872-1F464F35; Wed, 20 Aug 2014 09:05:53 +0000 X-Env-Sender: Felipe.Huici@neclab.eu X-Msg-Ref: server-16.tower-21.messagelabs.com!1408525551!8641102!1 X-Originating-IP: [195.37.70.40] 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 28238 invoked from network); 20 Aug 2014 09:05:51 -0000 Received: from mailer1.neclab.eu (HELO mailer1.neclab.eu) (195.37.70.40) by server-16.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 20 Aug 2014 09:05:51 -0000 Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3ADDE107B29; Wed, 20 Aug 2014 11:05:51 +0200 (CEST) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUztuICx0qA7; Wed, 20 Aug 2014 11:05:51 +0200 (CEST) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 1A0D5100471; Wed, 20 Aug 2014 11:05:45 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.182]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 20 Aug 2014 11:05:44 +0200 From: Felipe Huici To: Anil Madhavapeddy , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Thread-Topic: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore Thread-Index: AQHPu7SbtlEGfUkxsEytUO/q2n8fypvXz1WAgAFlFoA= Date: Wed, 20 Aug 2014 09:05:44 +0000 Message-ID: In-Reply-To: <3FAF9918-7C12-4343-BF51-D27715110960@recoil.org> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.4.120824 x-originating-ip: [10.1.99.81] Content-ID: <587D796215150A459C07ADFF3AD79C73@office.hd> MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 20 Aug 2014 10:04:19 +0000 Cc: Filipe Manco Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 SGkgQW5pbCwgYWxsLA0KDQpBcyBhIGNsYXJpZmljYXRpb24sIHRoZSB0YWxrIHdhcyBnaXZlbiBi eSBteSBjb2xsZWFndWUgRmlsaXBlIE1hbmNvLCBpbg0KY2MsIG5vdCBtZS4gSeKAmXZlIHRlbXBv cmFyaWx5IHBsYWNlZCB0aGUgc2xpZGVzIGF0Og0KDQpodHRwOi8vd3d3MC5jcy51Y2wuYWMudWsv c3RhZmYvZi5odWljaS9wcmVzZW50YXRpb25zL2NsaWNrb3MteGVuZGV2c3VtbWl0MTQNCi5wZGYN Cg0KVGhleSBzaG91bGQgYXBwZWFyIG9uIHRoZSBYZW4gc3VtbWl0IGJyaWVmbHksIGFuZCBtb3Jl IHBlcm1hbmVudGx5IG9uIG91cg0Kd2Vic2l0ZSBhdDoNCg0KaHR0cHM6Ly9jbnAubmVjbGFiLmV1 DQoNClRoYW5rcywNCg0K4oCUIEZlbGlwZQ0KDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCkRyLiBGZWxpcGUgSHVpY2kNClNlbmlv ciBSZXNlYXJjaGVyLCBOZXR3b3JrZWQgU3lzdGVtcyBhbmQgRGF0YQ0KQW5hbHl0aWNzIEdyb3Vw DQpORUMgTGFib3JhdG9yaWVzIEV1cm9wZSwgTmV0d29yayBSZXNlYXJjaCBEaXZpc2lvbg0KS3Vy ZnVlcnN0ZW5hbmxhZ2UgMzYsIEQtNjkxMTUgSGVpZGVsYmVyZw0KVGVsLiAgICAgKzQ5DQooMCk2 MjIxIDQzNDItMjQxDQpGYXg6ICAgICArNDkNCigwKTYyMjEgNDM0Mi0xNTUNCg0KZS1tYWlsOiAN CmZlbGlwZS5odWljaUBuZWNsYWIuZXUNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KTkVDIEV1cm9wZSBMaW1pdGVkIFJlZ2lzdGVy ZWQgT2ZmaWNlOiBORUMgSG91c2UsIDENClZpY3RvcmlhIFJvYWQsIExvbmRvbiBXMyA2QkwgUmVn aXN0ZXJlZCBpbiBFbmdsYW5kIDI4MzIwMTQNCg0KDQoNCg0KT24gOC8xOS8xNCwgMzo0NyBQTSwg IkFuaWwgTWFkaGF2YXBlZGR5IiA8YW5pbEByZWNvaWwub3JnPiB3cm90ZToNCg0KPk9uIDE5IEF1 ZyAyMDE0LCBhdCAwODo0NCwgQW5pbCBNYWRoYXZhcGVkZHkgPGFuaWxAcmVjb2lsLm9yZz4gd3Jv dGU6DQo+DQo+PiBPbiAxNyBBdWcgMjAxNCwgYXQgMTE6MDEsIEFuaWwgTWFkaGF2YXBlZGR5IDxh bmlsQHJlY29pbC5vcmc+IHdyb3RlOg0KPj4gDQo+Pj4gSSdtIGdpdmluZyBhIHRhbGsgYXQgdGhl IFhlbiBEZXZlbG9wZXIgU3VtbWl0IGF0IExpbnV4Y29uIHRvbW9ycm93IG9uDQo+Pj50aGUgd29y ayB0aGF0IHdlJ3ZlIChwcmltYXJpbHkgRGF2ZSBTY290dCBhbmQgVGhvbWFzIEdhemFnbmFpcmUp IG9uDQo+Pj5pbXByb3ZpbmcgdGhlIFhlbnN0b3JlIHZpYSBJcm1pbiBmZWF0dXJlcy4NCj4+PiAN Cj4+PiBTbGlkZXMgaGVyZTogaHR0cDovL2RlY2tzLm9wZW5taXJhZ2Uub3JnL3hlbmRldnN1bW1p dDE0Iy8NCj4+PiBSZXBvOiBodHRwczovL2dpdGh1Yi5jb20vbWlyYWdlL21pcmFnZS1kZWNrcyBh cyB1c3VhbA0KPj4+IA0KPj4gDQo+PiBbK3hlbi1hcGktZGV2ZWxdIFRhbGsgd2VudCB3ZWxsLCBx dWljayBub3RlcyBoZXJlOg0KPj4gDQo+PiAtIGdpdCB3b3JrZmxvdyB2ZXJ5IHBvcHVsYXIuIExv dHMgb2YgcGVvcGxlIHR3aWdnZWQgb250byB0aGUNCj4+bWFpbnRhaW5hYmlsaXR5IGJlbmVmaXRz IG9mIGBnaXQgYmlzZWN0YCBhdXRvbWF0aW9uIGluIHBhcnRpY3VsYXIuDQo+PiANCj4+IC0gcXVl c3Rpb25zIGFib3V0IHdoeSBYZW5zdG9yZSB0cmFuc2FjdGlvbnMgYXJlIHN0aWxsIG5lY2Vzc2Fy eSBpbiB0aGUNCj4+bW9kZXJuIHdvcmxkLiAgQ2FuIHJlcGxhY2Ugd2l0aCBjb25zZW5zdXMgcHJv dG9jb2xzIGluc3RlYWQ/ICBNYXliZSB0aW1lDQo+PmZvciBhbiBBQkkgYnVtcCB0byBkZXByZWNh dGUgdGhlIGFuY2llbnQgeGVuc3RvcmUgcHJvdG9jb2wuDQo+PiANCj4+IC0gc3BhY2UgdXNhZ2Ug aXMgYSBjb25jZXJuIC0tIGJ1aWxkaW5nIGFuIFJSRC1zdHlsZSBjb25zdGFudCBzaXplDQo+Pmxp YnJhcnkgdG8gbWFpbnRhaW4gcHJvZ3Jlc3NpdmUgaGlzdG9yeSB3b3VsZCBiZSBhIGJpZyB3aW4u DQo+PiANCj4+IC0gKmV4Y2VsbGVudCogdGFsayBmcm9tIEZlbGlwZSBIdWljaSAoQ0NlZCkgZnJv bSBORUMgYWJvdXQgYnVpbGRpbmcNCj4+bXVjaCBkZW5zZXIgVk0gd29ya2xvYWRzLCBhbmQgaGUg b2JzZXJ2ZWQgdGhhdCBYZW5zdG9yZWQveGVuY29uc29sZWQgYXJlDQo+PmEgYmlnIGJvdHRsZW5l Y2sgYXQgfjEwMDAwIFZNcy4gIEFyZSB5b3VyIHNsaWRlcyBhdmFpbGFibGUgRmVsaXBlPyAgU29t ZQ0KPj5zdWIgbm90ZXM6DQo+PiANCj4+IC0gd2UgY291bGQgd3JpdGUgYSBtaXJhZ2UgeGVuY29u c29sZWQgdG8gbG9nIHRvIGlybWluIGFuZCBkcmFpbiBndWVzdA0KPj5jb25zb2xlIHJpbmdzIG11 Y2ggZmFzdGVyLg0KPj4gLSBhIGRpc3RyaWJ1dGVkIHhlbnN0b3JlZCtpcm1pbiB3b3VsZCBhbGxv dyBzaWduaWZpY2FudGx5IG1vcmUNCj4+c2NhbGFiaWxpdHkgdGhhbiBhdHRlbXB0aW5nIHRvIGJ1 aWxkIGEgc2VyaWFsbHkgZmFzdCB2ZXJzaW9uLg0KPj4gLSBmZWxpcGUgaGFzIHRoZSBiZWdpbm5p bmcgb2YgYSBzaW1wbGUgYysrIHhlbnN0b3JlZCB0aGF0IGRvZXNuJ3QNCj4+aW1wbGVtZW50IHRo ZSBmdWxsIHNlbWFudGljcywgYnV0IGlzIGVub3VnaCBmb3IgTWluaU9TLg0KPj4gLSBpdCBtYXkg YmUgdXNlZnVsIHRvIG5lZ290aWF0ZSBhIHhlbnN0b3JlIHYyIHByb3RvY29sIGFuZCB1c2UgdGhh dCBmb3INCj4+bmV3IGd1ZXN0cy4gIEl0IGNvdWxkIHVzZSBhIHNpbXBsZSBmaXhlZC1sZW5ndGgg YmluYXJ5IHByb3RvY29sDQo+Pihwcm90b2J1Zi1zdHlsZT8pLCBhbmQgZWxpbWluYXRlIHRoZSBu ZWVkIGZvciB0cmFuc2FjdGlvbnMgcGVyaGFwcy4NCj4NCj5zZW50ICdzZW5kJyB0b28gcXVpY2ts eS4gIFRoZSBtb3N0IGltcG9ydGFudCBwb2ludDoNCj4NCj4tIHhlbnN0b3JlIG5lZWQgY29uc2lz dGVudCBpbmRpY2VzLiAgVXNpbmcgZG9tYWluIG5hbWVzIGluIHRoZSBjdXJyZW50DQo+c3RhY2sg cmVzdWx0cyBpbiBhIGxpbmVhciBzZWFyY2ggdGhyb3VnaCBhbGwgZG9taWRzIC0tIHZlcnkgc2xv dyB3aXRoDQo+MTAwMDAgVk1zISAgSXJtaW4gY291bGQgbWFpbnRhaW4gYSBicmFuY2ggdGhhdCB1 cGRhdGVzIGEgJ25hbWUgLT4gZG9taWQnDQo+dGhhdCBpcyBjb25zaXN0ZW50IHdpdGhpbiB0aGUg dHJhbnNhY3Rpb24sIGFuZCBkbyBjb25zdGFudCB0aW1lIGxvb2t1cHMNCj5mb3IgdGhlIHRvb2xz dGFjay4NCj4NCj4tYW5pbA0KPg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpNaXJhZ2VPUy1kZXZlbCBtYWlsaW5nIGxpc3QKTWlyYWdlT1MtZGV2ZWxA bGlzdHMueGVucHJvamVjdC5vcmcKaHR0cDovL2xpc3RzLnhlbnByb2plY3Qub3JnL2NnaS1iaW4v bWFpbG1hbi9saXN0aW5mby9taXJhZ2Vvcy1kZXZlbAo= From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 13:18:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 13:18: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 1XK5mm-0004fi-KW; Wed, 20 Aug 2014 13:18:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK5ml-0004fQ-28 for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 13:18:43 +0000 Received: from [193.109.254.147:9162] by server-7.bemta-14.messagelabs.com id C0/25-13362-230A4F35; Wed, 20 Aug 2014 13:18:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1408540721!12050024!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 19524 invoked from network); 20 Aug 2014 13:18:41 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 20 Aug 2014 13:18:41 -0000 Received: (qmail 15943 invoked by uid 634); 20 Aug 2014 13:18:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 20 Aug 2014 14:18:39 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 20 Aug 2014 08:18:36 -0500 Message-Id: References: To: Felipe Huici X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Filipe Manco , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 Thanks Felipe! (Huici and Manco :-) Terrible wifi at the dev summit this year, so it was difficult to share more information in real time. best, Anil On 20 Aug 2014, at 04:05, Felipe Huici wrote: > Hi Anil, all, > = > As a clarification, the talk was given by my colleague Filipe Manco, in > cc, not me. I=92ve temporarily placed the slides at: > = > http://www0.cs.ucl.ac.uk/staff/f.huici/presentations/clickos-xendevsummit= 14 > .pdf > = > They should appear on the Xen summit briefly, and more permanently on our > website at: > = > https://cnp.neclab.eu > = > Thanks, > = > =97 Felipe > = > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Dr. Felipe Huici > Senior Researcher, Networked Systems and Data > Analytics Group > NEC Laboratories Europe, Network Research Division > Kurfuerstenanlage 36, D-69115 Heidelberg > Tel. +49 > (0)6221 4342-241 > Fax: +49 > (0)6221 4342-155 > = > e-mail: = > felipe.huici@neclab.eu > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > NEC Europe Limited Registered Office: NEC House, 1 > Victoria Road, London W3 6BL Registered in England 2832014 > = > = > = > = > On 8/19/14, 3:47 PM, "Anil Madhavapeddy" wrote: > = >> On 19 Aug 2014, at 08:44, Anil Madhavapeddy wrote: >> = >>> On 17 Aug 2014, at 11:01, Anil Madhavapeddy wrote: >>> = >>>> I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on >>>> the work that we've (primarily Dave Scott and Thomas Gazagnaire) on >>>> improving the Xenstore via Irmin features. >>>> = >>>> Slides here: http://decks.openmirage.org/xendevsummit14#/ >>>> Repo: https://github.com/mirage/mirage-decks as usual >>>> = >>> = >>> [+xen-api-devel] Talk went well, quick notes here: >>> = >>> - git workflow very popular. Lots of people twigged onto the >>> maintainability benefits of `git bisect` automation in particular. >>> = >>> - questions about why Xenstore transactions are still necessary in the >>> modern world. Can replace with consensus protocols instead? Maybe time >>> for an ABI bump to deprecate the ancient xenstore protocol. >>> = >>> - space usage is a concern -- building an RRD-style constant size >>> library to maintain progressive history would be a big win. >>> = >>> - *excellent* talk from Felipe Huici (CCed) from NEC about building >>> much denser VM workloads, and he observed that Xenstored/xenconsoled are >>> a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some >>> sub notes: >>> = >>> - we could write a mirage xenconsoled to log to irmin and drain guest >>> console rings much faster. >>> - a distributed xenstored+irmin would allow significantly more >>> scalability than attempting to build a serially fast version. >>> - felipe has the beginning of a simple c++ xenstored that doesn't >>> implement the full semantics, but is enough for MiniOS. >>> - it may be useful to negotiate a xenstore v2 protocol and use that for >>> new guests. It could use a simple fixed-length binary protocol >>> (protobuf-style?), and eliminate the need for transactions perhaps. >> = >> sent 'send' too quickly. The most important point: >> = >> - xenstore need consistent indices. Using domain names in the current >> stack results in a linear search through all domids -- very slow with >> 10000 VMs! Irmin could maintain a branch that updates a 'name -> domid' >> that is consistent within the transaction, and do constant time lookups >> for the toolstack. >> = >> -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 Aug 20 13:18:51 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 13:18: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 1XK5mm-0004fi-KW; Wed, 20 Aug 2014 13:18:44 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK5ml-0004fQ-28 for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 13:18:43 +0000 Received: from [193.109.254.147:9162] by server-7.bemta-14.messagelabs.com id C0/25-13362-230A4F35; Wed, 20 Aug 2014 13:18:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-27.messagelabs.com!1408540721!12050024!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 19524 invoked from network); 20 Aug 2014 13:18:41 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-27.messagelabs.com with SMTP; 20 Aug 2014 13:18:41 -0000 Received: (qmail 15943 invoked by uid 634); 20 Aug 2014 13:18:40 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 20 Aug 2014 14:18:39 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 20 Aug 2014 08:18:36 -0500 Message-Id: References: To: Felipe Huici X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Filipe Manco , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] xen dev summit talk slides: Branch Consistency for Xenstore X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 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 Thanks Felipe! (Huici and Manco :-) Terrible wifi at the dev summit this year, so it was difficult to share more information in real time. best, Anil On 20 Aug 2014, at 04:05, Felipe Huici wrote: > Hi Anil, all, > = > As a clarification, the talk was given by my colleague Filipe Manco, in > cc, not me. I=92ve temporarily placed the slides at: > = > http://www0.cs.ucl.ac.uk/staff/f.huici/presentations/clickos-xendevsummit= 14 > .pdf > = > They should appear on the Xen summit briefly, and more permanently on our > website at: > = > https://cnp.neclab.eu > = > Thanks, > = > =97 Felipe > = > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Dr. Felipe Huici > Senior Researcher, Networked Systems and Data > Analytics Group > NEC Laboratories Europe, Network Research Division > Kurfuerstenanlage 36, D-69115 Heidelberg > Tel. +49 > (0)6221 4342-241 > Fax: +49 > (0)6221 4342-155 > = > e-mail: = > felipe.huici@neclab.eu > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > NEC Europe Limited Registered Office: NEC House, 1 > Victoria Road, London W3 6BL Registered in England 2832014 > = > = > = > = > On 8/19/14, 3:47 PM, "Anil Madhavapeddy" wrote: > = >> On 19 Aug 2014, at 08:44, Anil Madhavapeddy wrote: >> = >>> On 17 Aug 2014, at 11:01, Anil Madhavapeddy wrote: >>> = >>>> I'm giving a talk at the Xen Developer Summit at Linuxcon tomorrow on >>>> the work that we've (primarily Dave Scott and Thomas Gazagnaire) on >>>> improving the Xenstore via Irmin features. >>>> = >>>> Slides here: http://decks.openmirage.org/xendevsummit14#/ >>>> Repo: https://github.com/mirage/mirage-decks as usual >>>> = >>> = >>> [+xen-api-devel] Talk went well, quick notes here: >>> = >>> - git workflow very popular. Lots of people twigged onto the >>> maintainability benefits of `git bisect` automation in particular. >>> = >>> - questions about why Xenstore transactions are still necessary in the >>> modern world. Can replace with consensus protocols instead? Maybe time >>> for an ABI bump to deprecate the ancient xenstore protocol. >>> = >>> - space usage is a concern -- building an RRD-style constant size >>> library to maintain progressive history would be a big win. >>> = >>> - *excellent* talk from Felipe Huici (CCed) from NEC about building >>> much denser VM workloads, and he observed that Xenstored/xenconsoled are >>> a big bottleneck at ~10000 VMs. Are your slides available Felipe? Some >>> sub notes: >>> = >>> - we could write a mirage xenconsoled to log to irmin and drain guest >>> console rings much faster. >>> - a distributed xenstored+irmin would allow significantly more >>> scalability than attempting to build a serially fast version. >>> - felipe has the beginning of a simple c++ xenstored that doesn't >>> implement the full semantics, but is enough for MiniOS. >>> - it may be useful to negotiate a xenstore v2 protocol and use that for >>> new guests. It could use a simple fixed-length binary protocol >>> (protobuf-style?), and eliminate the need for transactions perhaps. >> = >> sent 'send' too quickly. The most important point: >> = >> - xenstore need consistent indices. Using domain names in the current >> stack results in a linear search through all domids -- very slow with >> 10000 VMs! Irmin could maintain a branch that updates a 'name -> domid' >> that is consistent within the transaction, and do constant time lookups >> for the toolstack. >> = >> -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 Aug 20 15:09:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 15:09: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 1XK7VW-0007MC-4L; Wed, 20 Aug 2014 15:09:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK7VV-0007M6-Jo for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 15:09:01 +0000 Received: from [85.158.137.68:21491] by server-7.bemta-3.messagelabs.com id B5/4B-01084-C0AB4F35; Wed, 20 Aug 2014 15:09:00 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1408547339!14743972!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 12274 invoked from network); 20 Aug 2014 15:09:00 -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; 20 Aug 2014 15:09:00 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-155-141.eduroam.wireless.private.cam.ac.uk ([172.17.155.141]:52955) 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 1XK7VT-0006KV-QV (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 20 Aug 2014 16:08:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 20 Aug 2014 16:08:58 +0100 Message-Id: <074403EA-99F6-4862-8CFC-8F7EFF84EF01@cam.ac.uk> References: To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call, Wednesday 20th 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 Dear all, I can't reach Dave, who's the organiser of the Go To Meeting account. We're switching to google Hangouts again. Please accept my apologies. https://plus.google.com/hangouts/_/grf2vgkqchgyf3u6j3tdpzkyyqa Amir On 18 Aug 2014, at 17:52, Amir Chaudhry wrote: > Dear all, > > I'd just like to make it explicitly clear that the Mirage calls are open to all. The agenda is publicly visible, call details are sent out every time and its alway nice to hear from new members of the community. The only expectation is that you briefly introduce yourself (unless you've also added an agenda item - in which case you'll need to speak about that too). > > Please do feel free to join in! On that note, the next Mirage call will take place on *Wednesday 20th* at 4pm BST (== GMT + 1) -- Apologies about the shifting days, but we're still in conference season. This time it's because Anil is speaking at the Xen Developer Summit in Chicago - the slides are already up if you want to take a look at http://decks.openmirage.org/xendevsummit14/ > > If you have points you'd like to discuss on the call, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. > > Notes from the last call are online at: http://openmirage.org/wiki/weekly-2014-08-07 > > GoToMeeting details: > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: > > +1 (213) 493-0008 > > Thanks, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 15:09:03 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 15:09: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 1XK7VW-0007MC-4L; Wed, 20 Aug 2014 15:09:02 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK7VV-0007M6-Jo for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 15:09:01 +0000 Received: from [85.158.137.68:21491] by server-7.bemta-3.messagelabs.com id B5/4B-01084-C0AB4F35; Wed, 20 Aug 2014 15:09:00 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1408547339!14743972!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 12274 invoked from network); 20 Aug 2014 15:09:00 -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; 20 Aug 2014 15:09:00 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-155-141.eduroam.wireless.private.cam.ac.uk ([172.17.155.141]:52955) 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 1XK7VT-0006KV-QV (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 20 Aug 2014 16:08:59 +0100 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 20 Aug 2014 16:08:58 +0100 Message-Id: <074403EA-99F6-4862-8CFC-8F7EFF84EF01@cam.ac.uk> References: To: "mirageos-devel@lists.xenproject.org" X-Mailer: Apple Mail (2.1510) Subject: Re: [MirageOS-devel] Mirage fortnightly call, Wednesday 20th 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 Dear all, I can't reach Dave, who's the organiser of the Go To Meeting account. We're switching to google Hangouts again. Please accept my apologies. https://plus.google.com/hangouts/_/grf2vgkqchgyf3u6j3tdpzkyyqa Amir On 18 Aug 2014, at 17:52, Amir Chaudhry wrote: > Dear all, > > I'd just like to make it explicitly clear that the Mirage calls are open to all. The agenda is publicly visible, call details are sent out every time and its alway nice to hear from new members of the community. The only expectation is that you briefly introduce yourself (unless you've also added an agenda item - in which case you'll need to speak about that too). > > Please do feel free to join in! On that note, the next Mirage call will take place on *Wednesday 20th* at 4pm BST (== GMT + 1) -- Apologies about the shifting days, but we're still in conference season. This time it's because Anil is speaking at the Xen Developer Summit in Chicago - the slides are already up if you want to take a look at http://decks.openmirage.org/xendevsummit14/ > > If you have points you'd like to discuss on the call, please do add them to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I'll structure them shortly before the call. > > Notes from the last call are online at: http://openmirage.org/wiki/weekly-2014-08-07 > > GoToMeeting details: > > 1. Please join my meeting. > https://www1.gotomeeting.com/join/591890401 > > Note the dial-in numbers seem to have changed. The new ones are visible if you join the meeting online but I believe the US one is: > > +1 (213) 493-0008 > > Thanks, > Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 15:25:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 15:25: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 1XK7lt-0007iN-75; Wed, 20 Aug 2014 15:25:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK7lq-0007iA-G6 for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 15:25:54 +0000 Received: from [85.158.139.211:47055] by server-5.bemta-5.messagelabs.com id 8E/27-11546-10EB4F35; Wed, 20 Aug 2014 15:25:53 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1408548353!8220292!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16970 invoked from network); 20 Aug 2014 15:25:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-16.tower-206.messagelabs.com with SMTP; 20 Aug 2014 15:25:53 -0000 X-IronPort-AV: E=Sophos;i="5.01,902,1400025600"; d="scan'208";a="24114705" From: Dave Scott To: Amir Chaudhry Thread-Topic: [MirageOS-devel] Mirage fortnightly call, Wednesday 20th at 4pm BST (== GMT + 1) Thread-Index: AQHPuwTo+91PY2rHRky2CFtEY7/1DJvZecQAgAAEt4A= Date: Wed, 20 Aug 2014 15:25:51 +0000 Message-ID: References: <074403EA-99F6-4862-8CFC-8F7EFF84EF01@cam.ac.uk> In-Reply-To: <074403EA-99F6-4862-8CFC-8F7EFF84EF01@cam.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <748EB8354F1D1546A1B74E398ED121BF@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage fortnightly call, Wednesday 20th 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, I=92m really sorry! Let=92s go the google hangout route in future to avoid relying on me to rem= ember! Dave On 20 Aug 2014, at 16:08, Amir Chaudhry wrote: > Dear all, I can't reach Dave, who's the organiser of the Go To Meeting ac= count. We're switching to google Hangouts again. Please accept my apologi= es. > = > https://plus.google.com/hangouts/_/grf2vgkqchgyf3u6j3tdpzkyyqa > = > Amir > = > On 18 Aug 2014, at 17:52, Amir Chaudhry wrote: > = >> Dear all, >> = >> I'd just like to make it explicitly clear that the Mirage calls are open= to all. The agenda is publicly visible, call details are sent out every t= ime and its alway nice to hear from new members of the community. The only= expectation is that you briefly introduce yourself (unless you've also add= ed an agenda item - in which case you'll need to speak about that too). >> = >> Please do feel free to join in! On that note, the next Mirage call will= take place on *Wednesday 20th* at 4pm BST (=3D=3D GMT + 1) -- Apologies ab= out the shifting days, but we're still in conference season. This time it'= s because Anil is speaking at the Xen Developer Summit in Chicago - the sli= des are already up if you want to take a look at http://decks.openmirage.or= g/xendevsummit14/ >> = >> If you have points you'd like to discuss on the call, please do add them= to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I= 'll structure them shortly before the call. >> = >> Notes from the last call are online at: http://openmirage.org/wiki/weekl= y-2014-08-07 >> = >> GoToMeeting details: >> = >> 1. Please join my meeting. >> https://www1.gotomeeting.com/join/591890401 >> = >> Note the dial-in numbers seem to have changed. The new ones are visible = if you join the meeting online but I believe the US one is: >> = >> +1 (213) 493-0008 >> = >> Thanks, >> Amir > = > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 15:25:59 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 15:25: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 1XK7lt-0007iN-75; Wed, 20 Aug 2014 15:25:57 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK7lq-0007iA-G6 for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 15:25:54 +0000 Received: from [85.158.139.211:47055] by server-5.bemta-5.messagelabs.com id 8E/27-11546-10EB4F35; Wed, 20 Aug 2014 15:25:53 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1408548353!8220292!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR, received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16970 invoked from network); 20 Aug 2014 15:25:53 -0000 Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-16.tower-206.messagelabs.com with SMTP; 20 Aug 2014 15:25:53 -0000 X-IronPort-AV: E=Sophos;i="5.01,902,1400025600"; d="scan'208";a="24114705" From: Dave Scott To: Amir Chaudhry Thread-Topic: [MirageOS-devel] Mirage fortnightly call, Wednesday 20th at 4pm BST (== GMT + 1) Thread-Index: AQHPuwTo+91PY2rHRky2CFtEY7/1DJvZecQAgAAEt4A= Date: Wed, 20 Aug 2014 15:25:51 +0000 Message-ID: References: <074403EA-99F6-4862-8CFC-8F7EFF84EF01@cam.ac.uk> In-Reply-To: <074403EA-99F6-4862-8CFC-8F7EFF84EF01@cam.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-ID: <748EB8354F1D1546A1B74E398ED121BF@citrix.com> MIME-Version: 1.0 X-DLP: AMS1 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage fortnightly call, Wednesday 20th 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, I=92m really sorry! Let=92s go the google hangout route in future to avoid relying on me to rem= ember! Dave On 20 Aug 2014, at 16:08, Amir Chaudhry wrote: > Dear all, I can't reach Dave, who's the organiser of the Go To Meeting ac= count. We're switching to google Hangouts again. Please accept my apologi= es. > = > https://plus.google.com/hangouts/_/grf2vgkqchgyf3u6j3tdpzkyyqa > = > Amir > = > On 18 Aug 2014, at 17:52, Amir Chaudhry wrote: > = >> Dear all, >> = >> I'd just like to make it explicitly clear that the Mirage calls are open= to all. The agenda is publicly visible, call details are sent out every t= ime and its alway nice to hear from new members of the community. The only= expectation is that you briefly introduce yourself (unless you've also add= ed an agenda item - in which case you'll need to speak about that too). >> = >> Please do feel free to join in! On that note, the next Mirage call will= take place on *Wednesday 20th* at 4pm BST (=3D=3D GMT + 1) -- Apologies ab= out the shifting days, but we're still in conference season. This time it'= s because Anil is speaking at the Xen Developer Summit in Chicago - the sli= des are already up if you want to take a look at http://decks.openmirage.or= g/xendevsummit14/ >> = >> If you have points you'd like to discuss on the call, please do add them= to the agenda at https://github.com/mirage/mirage-www/wiki/Call-Agenda - I= 'll structure them shortly before the call. >> = >> Notes from the last call are online at: http://openmirage.org/wiki/weekl= y-2014-08-07 >> = >> GoToMeeting details: >> = >> 1. Please join my meeting. >> https://www1.gotomeeting.com/join/591890401 >> = >> Note the dial-in numbers seem to have changed. The new ones are visible = if you join the meeting online but I believe the US one is: >> = >> +1 (213) 493-0008 >> = >> Thanks, >> Amir > = > = > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 17:19:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 17:19: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 1XK9Xu-0002ET-83; Wed, 20 Aug 2014 17:19:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK9Xs-0002EK-6y for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 17:19:36 +0000 Received: from [193.109.254.147:41479] by server-13.bemta-14.messagelabs.com id 88/BD-19311-7A8D4F35; Wed, 20 Aug 2014 17:19:35 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1408555171!7448625!1 X-Originating-IP: [157.55.2.16] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_30_40,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 23762 invoked from network); 20 Aug 2014 17:19:32 -0000 Received: from dub004-omc3s7.hotmail.com (HELO DUB004-OMC3S7.hotmail.com) (157.55.2.16) by server-5.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 20 Aug 2014 17:19:32 -0000 Received: from DUB128-W12 ([157.55.2.7]) by DUB004-OMC3S7.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Wed, 20 Aug 2014 10:19:31 -0700 X-TMN: [P3guLCeMM7rE3N6f/DDR+DAOt+pAlT7j] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: "mirageos-devel@lists.xenproject.org" Date: Wed, 20 Aug 2014 17:19:31 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 20 Aug 2014 17:19:31.0555 (UTC) FILETIME=[E7B70330:01CFBC9A] Subject: [MirageOS-devel] static_website+ip X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7646528633557754884==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7646528633557754884== Content-Type: multipart/alternative; boundary="_533ed431-9058-4355-a352-81e8a77fbc75_" --_533ed431-9058-4355-a352-81e8a77fbc75_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C I've just come back to looking at this example and I guess things have chan= ged. When I initially tried to make this I got : File "dispatch.ml"=2C line 15=2C characters 41-46: Error: Unbound module Clock Command exited with code 2. make: *** [main.native] Error 10 So=2C I added "mirage-clock-unix" to add_to_ocamlfind_libraries in config.m= l and moved onto the next one=2C which I haven't been able to figure out -= would be very grateful if someone could give me a pointer on how to fix th= is: File "dispatch.ml"=2C line 29=2C characters 19-52: Error: Unbound module OS.Start_info Best Nick = --_533ed431-9058-4355-a352-81e8a77fbc75_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=2C

I've just come back= to looking at this example and I guess things have changed. When I initial= ly tried to make this I got :


File "dispatch.ml"=2C line 15=2C c= haracters 41-46:
Error: Unbound module Clock
Command exited with code= 2.
make: *** [main.native] Error 10


So=2C I added "mirage-cl= ock-unix" to add_to_ocamlfind_libraries in config.ml and moved onto the nex= t one=2C which I haven't been able to figure out =3B - would be very gr= ateful if someone could give me a pointer on how to fix this:

File "= dispatch.ml"=2C line 29=2C characters 19-52:
Error: Unbound module OS.St= art_info

Best
Nick
= --_533ed431-9058-4355-a352-81e8a77fbc75_-- --===============7646528633557754884== 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 --===============7646528633557754884==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 17:19:43 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 17:19: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 1XK9Xu-0002ET-83; Wed, 20 Aug 2014 17:19:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XK9Xs-0002EK-6y for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 17:19:36 +0000 Received: from [193.109.254.147:41479] by server-13.bemta-14.messagelabs.com id 88/BD-19311-7A8D4F35; Wed, 20 Aug 2014 17:19:35 +0000 X-Env-Sender: buzzheavyyear@hotmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1408555171!7448625!1 X-Originating-IP: [157.55.2.16] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, FORGED_HOTMAIL_RCVD,HTML_30_40,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 23762 invoked from network); 20 Aug 2014 17:19:32 -0000 Received: from dub004-omc3s7.hotmail.com (HELO DUB004-OMC3S7.hotmail.com) (157.55.2.16) by server-5.tower-27.messagelabs.com with AES128-SHA encrypted SMTP; 20 Aug 2014 17:19:32 -0000 Received: from DUB128-W12 ([157.55.2.7]) by DUB004-OMC3S7.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Wed, 20 Aug 2014 10:19:31 -0700 X-TMN: [P3guLCeMM7rE3N6f/DDR+DAOt+pAlT7j] X-Originating-Email: [buzzheavyyear@hotmail.com] Message-ID: From: buzz heavyyear To: "mirageos-devel@lists.xenproject.org" Date: Wed, 20 Aug 2014 17:19:31 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 20 Aug 2014 17:19:31.0555 (UTC) FILETIME=[E7B70330:01CFBC9A] Subject: [MirageOS-devel] static_website+ip X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============7646528633557754884==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7646528633557754884== Content-Type: multipart/alternative; boundary="_533ed431-9058-4355-a352-81e8a77fbc75_" --_533ed431-9058-4355-a352-81e8a77fbc75_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi=2C I've just come back to looking at this example and I guess things have chan= ged. When I initially tried to make this I got : File "dispatch.ml"=2C line 15=2C characters 41-46: Error: Unbound module Clock Command exited with code 2. make: *** [main.native] Error 10 So=2C I added "mirage-clock-unix" to add_to_ocamlfind_libraries in config.m= l and moved onto the next one=2C which I haven't been able to figure out -= would be very grateful if someone could give me a pointer on how to fix th= is: File "dispatch.ml"=2C line 29=2C characters 19-52: Error: Unbound module OS.Start_info Best Nick = --_533ed431-9058-4355-a352-81e8a77fbc75_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=2C

I've just come back= to looking at this example and I guess things have changed. When I initial= ly tried to make this I got :


File "dispatch.ml"=2C line 15=2C c= haracters 41-46:
Error: Unbound module Clock
Command exited with code= 2.
make: *** [main.native] Error 10


So=2C I added "mirage-cl= ock-unix" to add_to_ocamlfind_libraries in config.ml and moved onto the nex= t one=2C which I haven't been able to figure out =3B - would be very gr= ateful if someone could give me a pointer on how to fix this:

File "= dispatch.ml"=2C line 29=2C characters 19-52:
Error: Unbound module OS.St= art_info

Best
Nick
= --_533ed431-9058-4355-a352-81e8a77fbc75_-- --===============7646528633557754884== 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 --===============7646528633557754884==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 20:01:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 20:01: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 1XKC4l-0005TK-Tv; Wed, 20 Aug 2014 20:01:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKC4k-0005TF-IG for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 20:01:42 +0000 Received: from [85.158.139.211:35697] by server-1.bemta-5.messagelabs.com id 64/05-17892-5AEF4F35; Wed, 20 Aug 2014 20:01:41 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1408564899!11122847!1 X-Originating-IP: [209.85.219.41] 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 4873 invoked from network); 20 Aug 2014 20:01:40 -0000 Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Aug 2014 20:01:40 -0000 Received: by mail-oa0-f41.google.com with SMTP id j17so6837505oag.28 for ; Wed, 20 Aug 2014 13:01:39 -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=pkM14MSo1E6oE8X0PiIItufsm8cDvdo1impP6fjg1bc=; b=eskcucTqNzupKZI8eWmfRGehz81rGjXt+TR8a0noHHQIEJSdWcuWNeLeqatIeWGJBE 7IAJYMGd1i4BnyusC2xCLfPaCJ1+jbYnHFv6aKnjjvuKr92gx6aw4Qnf0qfxO8Yu8D8K 42FpEz1dCD9SaSoQK2j1C09X6FilneDEj5xO8ILPfOFtOu2ejqlGdaLkOk344wKg4UHB fus+pfC0exaf/SpLgjE1jWP7OghwzlDDSNfaSrdpbuwmVXoeaijZ1kbzi6cuDfkVCIbS s357SnbwMcDJH5DSGJRgU3LERVf3+NSBVxEz4uCVWaWe2OORP3lnsmQvDhYr42l0f/BL E/aw== MIME-Version: 1.0 X-Received: by 10.60.58.36 with SMTP id n4mr17734837oeq.73.1408564899041; Wed, 20 Aug 2014 13:01:39 -0700 (PDT) Received: by 10.202.197.146 with HTTP; Wed, 20 Aug 2014 13:01:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 13:01:38 -0700 Message-ID: From: Jyotsna Prakash To: Len Maxwell Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage on EC2 X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2247263085560984882==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2247263085560984882== Content-Type: multipart/alternative; boundary=089e01538baa7358f70501151268 --089e01538baa7358f70501151268 Content-Type: text/plain; charset=UTF-8 Hi Len, I have not been able to successfully boot a unikernel-based AMI on EC2 Have you tried using the EC2 AMI command line tools? As in https://github.com/mirage/mirage/blob/master/scripts/ec2.sh Alternatively I have been working on OCaml bindings EC2. Apparently (besides myself) two people have had success with them. If you try them out please let me know how it goes. They are at https://github.com/moonlightdrive/ocaml-ec2 I think that using a Linux AMI to bootstrap an instance might be a practical alternative to minting an AMI for each update. Why is this? Regards, Jyotsna On Tue, Aug 19, 2014 at 7:35 AM, Len Maxwell wrote: > Hello, > > I have not been able to successfully boot a unikernel-based AMI on EC2 > (something I will revisit later). In the meantime, I found that you > can replace the kernel on a standard Linux instance without much > trouble: > > - Build a unikernel, ex. mirage-skeleton/static_website. > > - Launch an instance with the "Amazon Linux AMI ... PV" (on us-east-1: > ami-7c807d14 for instance-backed, ami-7c807d14 for EBS-backed). This > will select the proper AKI for pvgrub. Make sure to set up an SSH > key, and a security group that allows ssh and http. > > - Once the instance is up, push the kernel to ec2-user's home directory: > scp mir-www.xen ec2-user@:. > > - Log in as ec2-user: > ssh ec2-user@ > > - Move the kernel to /boot: > sudo mv mir-www.xen /boot > > - Edit the grub menu: > sudo vi /boot/grub/menu.lst > > - Add the following menu entry, before (or instead of) the "title > Amazon Linux" entry: > title mirage > root (hd0) > kernel /boot/mir-www.xen > > - Restart: > sudo shutdown -r now > > This should work OK as long as the unikernel uses only memory and > network; the disk is full of Linux cruft. It's not ideal, but I think > that using a Linux AMI to bootstrap an instance might be a practical > alternative to minting an AMI for each update. > > -- > Len > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e01538baa7358f70501151268 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Len,

I have not been able to= successfully boot a unikernel-based AMI on EC2

Have you tried= using the EC2 AMI command line tools? As in
https://github.com/mirage/mira= ge/blob/master/scripts/ec2.sh

Alternatively I have been working on OCaml bindings EC2. Apparent= ly (besides myself) two people have had success with them.
I= f you try them out please let me know how it goes.

I think that using a Linux AMI to bootstrap an instanc= e might be a practical
alternative to minting an AMI for each update.
Why is this?

Regards,
Jyotsna





On Tue, Aug 19, 2014 at 7:35 AM, Len Maxwell <<= a href=3D"mailto:len@lnmx.org" target=3D"_blank">len@lnmx.org> wrote:
Hello,

I have not been able to successfully boot a unikernel-based AMI on EC2
(something I will revisit later).=C2=A0 In the meantime, I found that you can replace the kernel on a standard Linux instance without much
trouble:

- Build a unikernel, ex. mirage-skeleton/static_website.

- Launch an instance with the "Amazon Linux AMI ... PV" (on us-ea= st-1:
ami-7c807d14 for instance-backed, ami-7c807d14 for EBS-backed).=C2=A0 This<= br> will select the proper AKI for pvgrub.=C2=A0 Make sure to set up an SSH
key, and a security group that allows ssh and http.

- Once the instance is up, push the kernel to ec2-user's home directory= :
scp mir-www.xen ec2-user@<ip-address>:.

- Log in as ec2-user:
ssh ec2-user@<ip-address>

- Move the kernel to /boot:
sudo mv mir-www.xen /boot

- Edit the grub menu:
sudo vi /boot/grub/menu.lst

- Add the following menu entry, before (or instead of) the "title
Amazon Linux" entry:
title mirage
root (hd0)
kernel /boot/mir-www.xen

- Restart:
sudo shutdown -r now

This should work OK as long as the unikernel uses only memory and
network; the disk is full of Linux cruft.=C2=A0 It's not ideal, but I t= hink
that using a Linux AMI to bootstrap an instance might be a practical
alternative to minting an AMI for each update.

--
Len

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

--089e01538baa7358f70501151268-- --===============2247263085560984882== 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 --===============2247263085560984882==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 20:01:50 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 20:01: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 1XKC4l-0005TK-Tv; Wed, 20 Aug 2014 20:01:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKC4k-0005TF-IG for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 20:01:42 +0000 Received: from [85.158.139.211:35697] by server-1.bemta-5.messagelabs.com id 64/05-17892-5AEF4F35; Wed, 20 Aug 2014 20:01:41 +0000 X-Env-Sender: jyotsna.prakash@gmail.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1408564899!11122847!1 X-Originating-IP: [209.85.219.41] 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 4873 invoked from network); 20 Aug 2014 20:01:40 -0000 Received: from mail-oa0-f41.google.com (HELO mail-oa0-f41.google.com) (209.85.219.41) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 20 Aug 2014 20:01:40 -0000 Received: by mail-oa0-f41.google.com with SMTP id j17so6837505oag.28 for ; Wed, 20 Aug 2014 13:01:39 -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=pkM14MSo1E6oE8X0PiIItufsm8cDvdo1impP6fjg1bc=; b=eskcucTqNzupKZI8eWmfRGehz81rGjXt+TR8a0noHHQIEJSdWcuWNeLeqatIeWGJBE 7IAJYMGd1i4BnyusC2xCLfPaCJ1+jbYnHFv6aKnjjvuKr92gx6aw4Qnf0qfxO8Yu8D8K 42FpEz1dCD9SaSoQK2j1C09X6FilneDEj5xO8ILPfOFtOu2ejqlGdaLkOk344wKg4UHB fus+pfC0exaf/SpLgjE1jWP7OghwzlDDSNfaSrdpbuwmVXoeaijZ1kbzi6cuDfkVCIbS s357SnbwMcDJH5DSGJRgU3LERVf3+NSBVxEz4uCVWaWe2OORP3lnsmQvDhYr42l0f/BL E/aw== MIME-Version: 1.0 X-Received: by 10.60.58.36 with SMTP id n4mr17734837oeq.73.1408564899041; Wed, 20 Aug 2014 13:01:39 -0700 (PDT) Received: by 10.202.197.146 with HTTP; Wed, 20 Aug 2014 13:01:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 13:01:38 -0700 Message-ID: From: Jyotsna Prakash To: Len Maxwell Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage on EC2 X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2247263085560984882==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2247263085560984882== Content-Type: multipart/alternative; boundary=089e01538baa7358f70501151268 --089e01538baa7358f70501151268 Content-Type: text/plain; charset=UTF-8 Hi Len, I have not been able to successfully boot a unikernel-based AMI on EC2 Have you tried using the EC2 AMI command line tools? As in https://github.com/mirage/mirage/blob/master/scripts/ec2.sh Alternatively I have been working on OCaml bindings EC2. Apparently (besides myself) two people have had success with them. If you try them out please let me know how it goes. They are at https://github.com/moonlightdrive/ocaml-ec2 I think that using a Linux AMI to bootstrap an instance might be a practical alternative to minting an AMI for each update. Why is this? Regards, Jyotsna On Tue, Aug 19, 2014 at 7:35 AM, Len Maxwell wrote: > Hello, > > I have not been able to successfully boot a unikernel-based AMI on EC2 > (something I will revisit later). In the meantime, I found that you > can replace the kernel on a standard Linux instance without much > trouble: > > - Build a unikernel, ex. mirage-skeleton/static_website. > > - Launch an instance with the "Amazon Linux AMI ... PV" (on us-east-1: > ami-7c807d14 for instance-backed, ami-7c807d14 for EBS-backed). This > will select the proper AKI for pvgrub. Make sure to set up an SSH > key, and a security group that allows ssh and http. > > - Once the instance is up, push the kernel to ec2-user's home directory: > scp mir-www.xen ec2-user@:. > > - Log in as ec2-user: > ssh ec2-user@ > > - Move the kernel to /boot: > sudo mv mir-www.xen /boot > > - Edit the grub menu: > sudo vi /boot/grub/menu.lst > > - Add the following menu entry, before (or instead of) the "title > Amazon Linux" entry: > title mirage > root (hd0) > kernel /boot/mir-www.xen > > - Restart: > sudo shutdown -r now > > This should work OK as long as the unikernel uses only memory and > network; the disk is full of Linux cruft. It's not ideal, but I think > that using a Linux AMI to bootstrap an instance might be a practical > alternative to minting an AMI for each update. > > -- > Len > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --089e01538baa7358f70501151268 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Len,

I have not been able to= successfully boot a unikernel-based AMI on EC2

Have you tried= using the EC2 AMI command line tools? As in
https://github.com/mirage/mira= ge/blob/master/scripts/ec2.sh

Alternatively I have been working on OCaml bindings EC2. Apparent= ly (besides myself) two people have had success with them.
I= f you try them out please let me know how it goes.

I think that using a Linux AMI to bootstrap an instanc= e might be a practical
alternative to minting an AMI for each update.
Why is this?

Regards,
Jyotsna





On Tue, Aug 19, 2014 at 7:35 AM, Len Maxwell <<= a href=3D"mailto:len@lnmx.org" target=3D"_blank">len@lnmx.org> wrote:
Hello,

I have not been able to successfully boot a unikernel-based AMI on EC2
(something I will revisit later).=C2=A0 In the meantime, I found that you can replace the kernel on a standard Linux instance without much
trouble:

- Build a unikernel, ex. mirage-skeleton/static_website.

- Launch an instance with the "Amazon Linux AMI ... PV" (on us-ea= st-1:
ami-7c807d14 for instance-backed, ami-7c807d14 for EBS-backed).=C2=A0 This<= br> will select the proper AKI for pvgrub.=C2=A0 Make sure to set up an SSH
key, and a security group that allows ssh and http.

- Once the instance is up, push the kernel to ec2-user's home directory= :
scp mir-www.xen ec2-user@<ip-address>:.

- Log in as ec2-user:
ssh ec2-user@<ip-address>

- Move the kernel to /boot:
sudo mv mir-www.xen /boot

- Edit the grub menu:
sudo vi /boot/grub/menu.lst

- Add the following menu entry, before (or instead of) the "title
Amazon Linux" entry:
title mirage
root (hd0)
kernel /boot/mir-www.xen

- Restart:
sudo shutdown -r now

This should work OK as long as the unikernel uses only memory and
network; the disk is full of Linux cruft.=C2=A0 It's not ideal, but I t= hink
that using a Linux AMI to bootstrap an instance might be a practical
alternative to minting an AMI for each update.

--
Len

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

--089e01538baa7358f70501151268-- --===============2247263085560984882== 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 --===============2247263085560984882==-- From mirageos-devel-bounces@lists.xenproject.org Wed Aug 20 23:55:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 23:55: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 1XKFiV-0007uU-Qp; Wed, 20 Aug 2014 23:54:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKFiU-0007uP-U2 for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 23:54:59 +0000 Received: from [85.158.143.35:40233] by server-2.bemta-4.messagelabs.com id 3B/D1-04525-25535F35; Wed, 20 Aug 2014 23:54:58 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1408578897!12184608!1 X-Originating-IP: [74.125.82.43] 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 20646 invoked from network); 20 Aug 2014 23:54:57 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Aug 2014 23:54:57 -0000 Received: by mail-wg0-f43.google.com with SMTP id l18so8370711wgh.2 for ; Wed, 20 Aug 2014 16:54:57 -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=PVlVmGYX4atuT2oeejcCeh/HEtWPeHX75gOF8u9dNGo=; b=J55fTV57t5DHORQzxBu9B4YwLqQr6BTLWU37NtRhl3JUD5dlK857qsk6hAbscbohfS JpsRGJWBZ3idIaCuMncVUfwRZZtolYoBhj5vMgGwyAEXoCcjKf117D2EtkdX5qtJGWXT kz3vXRSpvbOBUB0igwyzHhS0ldLdpljjrTOPkyHD/9WbBmEWgl0rLk11YlkDSz6GxuBf G1ibC1SFvwTLYnwyb4TkHyJthTIL1k7FaZ5D5copThZ3Q/FcPsN50pSPZOChvB6tdzSO xTzgMPU7MezgG2lWgrtqLY5i0aA1clO0uR0D/fmWbutwquYXYcym8LaUyAag6+zlS069 3bfg== X-Gm-Message-State: ALoCoQkMV1f5LX61DTMUhFer+K8GrO9gfHS6x/P3IjR/IGnCOcdL5bgotmUQ24cXsgtwd+j6VPkF MIME-Version: 1.0 X-Received: by 10.195.13.79 with SMTP id ew15mr60390328wjd.19.1408578897085; Wed, 20 Aug 2014 16:54:57 -0700 (PDT) Received: by 10.194.100.201 with HTTP; Wed, 20 Aug 2014 16:54:57 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 19:54:57 -0400 Message-ID: From: Len Maxwell To: Jyotsna Prakash Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage on EC2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Jyotsna, On Wed, Aug 20, 2014 at 4:01 PM, Jyotsna Prakash wrote: > > Have you tried using the EC2 AMI command line tools? As in > https://github.com/mirage/mirage/blob/master/scripts/ec2.sh Yes, I started with scripts/ec2.sh, and made some changes to support us-east-1. The AMI was created/uploaded/registered successfully, but failed with errors visible in the instance's console. I will try this approach again, now that I have more confidence in my mirage build environment. > Alternatively I have been working on OCaml bindings EC2. Apparently (besides > myself) two people have had success with them. > If you try them out please let me know how it goes. > They are at https://github.com/moonlightdrive/ocaml-ec2 Noted, thanks. > > I think that using a Linux AMI to bootstrap an instance might be a practical > > alternative to minting an AMI for each update. > > Why is this? The approach I described works equally for the EBS-only t1.micro (free tier) and other instance types. If you push the unikernel to S3, the process of installing the kernel, updating menu.lst, and rebooting can be automated with a "user data" script at launch. I think it's a decent option for beginners (like me) looking to test out the mirage-skeleton examples on EC2. However, if I want to read/write to the local disk, I think it will be necessary to build an AMI with the proper partitioning and filesystem up-front. -- 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 Wed Aug 20 23:55:04 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 20 Aug 2014 23:55: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 1XKFiV-0007uU-Qp; Wed, 20 Aug 2014 23:54:59 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKFiU-0007uP-U2 for mirageos-devel@lists.xenproject.org; Wed, 20 Aug 2014 23:54:59 +0000 Received: from [85.158.143.35:40233] by server-2.bemta-4.messagelabs.com id 3B/D1-04525-25535F35; Wed, 20 Aug 2014 23:54:58 +0000 X-Env-Sender: len@inthemail.org X-Msg-Ref: server-15.tower-21.messagelabs.com!1408578897!12184608!1 X-Originating-IP: [74.125.82.43] 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 20646 invoked from network); 20 Aug 2014 23:54:57 -0000 Received: from mail-wg0-f43.google.com (HELO mail-wg0-f43.google.com) (74.125.82.43) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Aug 2014 23:54:57 -0000 Received: by mail-wg0-f43.google.com with SMTP id l18so8370711wgh.2 for ; Wed, 20 Aug 2014 16:54:57 -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=PVlVmGYX4atuT2oeejcCeh/HEtWPeHX75gOF8u9dNGo=; b=J55fTV57t5DHORQzxBu9B4YwLqQr6BTLWU37NtRhl3JUD5dlK857qsk6hAbscbohfS JpsRGJWBZ3idIaCuMncVUfwRZZtolYoBhj5vMgGwyAEXoCcjKf117D2EtkdX5qtJGWXT kz3vXRSpvbOBUB0igwyzHhS0ldLdpljjrTOPkyHD/9WbBmEWgl0rLk11YlkDSz6GxuBf G1ibC1SFvwTLYnwyb4TkHyJthTIL1k7FaZ5D5copThZ3Q/FcPsN50pSPZOChvB6tdzSO xTzgMPU7MezgG2lWgrtqLY5i0aA1clO0uR0D/fmWbutwquYXYcym8LaUyAag6+zlS069 3bfg== X-Gm-Message-State: ALoCoQkMV1f5LX61DTMUhFer+K8GrO9gfHS6x/P3IjR/IGnCOcdL5bgotmUQ24cXsgtwd+j6VPkF MIME-Version: 1.0 X-Received: by 10.195.13.79 with SMTP id ew15mr60390328wjd.19.1408578897085; Wed, 20 Aug 2014 16:54:57 -0700 (PDT) Received: by 10.194.100.201 with HTTP; Wed, 20 Aug 2014 16:54:57 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 19:54:57 -0400 Message-ID: From: Len Maxwell To: Jyotsna Prakash Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage on EC2 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 Jyotsna, On Wed, Aug 20, 2014 at 4:01 PM, Jyotsna Prakash wrote: > > Have you tried using the EC2 AMI command line tools? As in > https://github.com/mirage/mirage/blob/master/scripts/ec2.sh Yes, I started with scripts/ec2.sh, and made some changes to support us-east-1. The AMI was created/uploaded/registered successfully, but failed with errors visible in the instance's console. I will try this approach again, now that I have more confidence in my mirage build environment. > Alternatively I have been working on OCaml bindings EC2. Apparently (besides > myself) two people have had success with them. > If you try them out please let me know how it goes. > They are at https://github.com/moonlightdrive/ocaml-ec2 Noted, thanks. > > I think that using a Linux AMI to bootstrap an instance might be a practical > > alternative to minting an AMI for each update. > > Why is this? The approach I described works equally for the EBS-only t1.micro (free tier) and other instance types. If you push the unikernel to S3, the process of installing the kernel, updating menu.lst, and rebooting can be automated with a "user data" script at launch. I think it's a decent option for beginners (like me) looking to test out the mirage-skeleton examples on EC2. However, if I want to read/write to the local disk, I think it will be necessary to build an AMI with the proper partitioning and filesystem up-front. -- 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 Thu Aug 21 09:13:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 09:13: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 1XKOR7-0003LC-W6; Thu, 21 Aug 2014 09:13:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKOR6-0003L3-PR for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 09:13:36 +0000 Received: from [85.158.139.211:7464] by server-8.bemta-5.messagelabs.com id 83/24-22440-048B5F35; Thu, 21 Aug 2014 09:13:36 +0000 X-Env-Sender: vb@luminar.eu.org X-Msg-Ref: server-12.tower-206.messagelabs.com!1408612119!11227011!1 X-Originating-IP: [94.23.24.152] 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 21397 invoked from network); 21 Aug 2014 09:08:39 -0000 Received: from luminar.eu.org (HELO luminar.eu.org) (94.23.24.152) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Aug 2014 09:08:39 -0000 Received: from [IPv6:2a01:e35:2e2c:85e0:585:11eb:9d25:106] (unknown [IPv6:2a01:e35:2e2c:85e0:585:11eb:9d25:106]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by luminar.eu.org (Postfix) with ESMTPSA id 0612B60A7E; Thu, 21 Aug 2014 11:08:37 +0200 (CEST) Message-ID: <53F5B715.7000700@luminar.eu.org> Date: Thu, 21 Aug 2014 11:08:37 +0200 From: "Vincent B." User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: webmaster@websocket.org Cc: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] TLS implementation of wss://echo.websocket.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I'm testing wss://echo.websocket.org with a custom (http://github.com/mirleft/ocaml-tls) TLS implementation. Using this implementation, your server just shuts down the connection just after the "ClientHello" TLS message, and AFAIK this is not RFC complient. Could you tell me which TLS implementation echo.websocket.org uses ? Thanks, Vincent. _______________________________________________ MirageOS-devel 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 Aug 21 09:13:40 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 09:13: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 1XKOR7-0003LC-W6; Thu, 21 Aug 2014 09:13:37 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKOR6-0003L3-PR for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 09:13:36 +0000 Received: from [85.158.139.211:7464] by server-8.bemta-5.messagelabs.com id 83/24-22440-048B5F35; Thu, 21 Aug 2014 09:13:36 +0000 X-Env-Sender: vb@luminar.eu.org X-Msg-Ref: server-12.tower-206.messagelabs.com!1408612119!11227011!1 X-Originating-IP: [94.23.24.152] 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 21397 invoked from network); 21 Aug 2014 09:08:39 -0000 Received: from luminar.eu.org (HELO luminar.eu.org) (94.23.24.152) by server-12.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Aug 2014 09:08:39 -0000 Received: from [IPv6:2a01:e35:2e2c:85e0:585:11eb:9d25:106] (unknown [IPv6:2a01:e35:2e2c:85e0:585:11eb:9d25:106]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by luminar.eu.org (Postfix) with ESMTPSA id 0612B60A7E; Thu, 21 Aug 2014 11:08:37 +0200 (CEST) Message-ID: <53F5B715.7000700@luminar.eu.org> Date: Thu, 21 Aug 2014 11:08:37 +0200 From: "Vincent B." User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: webmaster@websocket.org Cc: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] TLS implementation of wss://echo.websocket.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I'm testing wss://echo.websocket.org with a custom (http://github.com/mirleft/ocaml-tls) TLS implementation. Using this implementation, your server just shuts down the connection just after the "ClientHello" TLS message, and AFAIK this is not RFC complient. Could you tell me which TLS implementation echo.websocket.org uses ? Thanks, Vincent. _______________________________________________ MirageOS-devel 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 Aug 21 11:10:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 11:10: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 1XKQFt-0005WV-Nd; Thu, 21 Aug 2014 11:10:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKQFr-0005WN-Sj for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 11:10:08 +0000 Received: from [85.158.143.35:16567] by server-2.bemta-4.messagelabs.com id 8D/C4-04525-F83D5F35; Thu, 21 Aug 2014 11:10:07 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1408619405!12325593!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 19730 invoked from network); 21 Aug 2014 11:10:06 -0000 Received: from mail-oi0-f53.google.com (HELO mail-oi0-f53.google.com) (209.85.218.53) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 11:10:06 -0000 Received: by mail-oi0-f53.google.com with SMTP id e131so6612993oig.40 for ; Thu, 21 Aug 2014 04:10:04 -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=mg5cQqoZJIOGKu+XFYN0QOExhp7NRjTy8xG56SO9Nl4=; b=yqX/TSSQEwPMjwhigsV8zgbv9+RJ4Ga0ydEygypU/Ygn32Q09HLsNURMWUIVydgFv7 EHBxBeilMd/Pb1HqMscUdRYN6wqBSGtf8xnO15FpB67AGnPEbfaSgedswYP61A3QJ4ZQ qVT2vLSvAkSDpsO/2o9FpPOZozndKcsk2+qvciEkbdGWCHadU5STwaX03zOB4I3zxgsv eRNTpCpyXMhq3nAHi8B2fuswh4xwAU/dy0jv0GSjEfOuCx5qMSBYkeG1YvDNRqCnrYvb sTlnJv7nwzNp2S+WqtD5oi/gL57hLw876+uUq91ZO++QfI2ZRQL+OvX7dfDpi/71mC+e s7PQ== MIME-Version: 1.0 X-Received: by 10.182.104.104 with SMTP id gd8mr53304428obb.17.1408619404326; Thu, 21 Aug 2014 04:10:04 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Thu, 21 Aug 2014 04:10:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 12:10:04 +0100 Message-ID: From: Thomas Leonard To: David 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 August 2014 14:04, David Scott wrote: > > On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard wrote: >> >> Has anyone made any tools for profiling on Xen? > > > The closest thing I can think of is xentrace/xenalyse: > > http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenalyze/ > > This will tell you what Xen can see: eg how the vCPUs map to pCPUs and when > they block on events etc. Thanks. For now, I've pinned dom0 to CPU 0 and my unikernel to CPU 1. >> I want to see why my network service on Xen/ARM only gets about 5 MB/s >> (while a Linux guest gets about 45 MB/s). >> >> I tried compiling with profiling on ("true: profile" in the _tags) and >> wrote a __gnu_mcount_nc function to dump all the results to a buffer >> [1], plus a script to turn the addresses back into symbols and guess >> the nesting (a bit unreliable, as it doesn't tell you when the >> function finishes). >> >> Here's an example CSV of the output (the unikernel waits for a TCP >> connection and then streams data to it as fast as it can): >> >> http://test.roscidus.com/static/sample-output.csv.bz2 >> >> I haven't checked it carefully to see if it's correct - this is just >> an example of the kind of output. It shows the call graph and the >> (cumulative) time spent in each function. Since it doesn't know the >> end times, it assumes a function runs until one of its parents calls >> something else. > > > 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! 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 From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 11:10:12 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 11:10: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 1XKQFt-0005WV-Nd; Thu, 21 Aug 2014 11:10:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKQFr-0005WN-Sj for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 11:10:08 +0000 Received: from [85.158.143.35:16567] by server-2.bemta-4.messagelabs.com id 8D/C4-04525-F83D5F35; Thu, 21 Aug 2014 11:10:07 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1408619405!12325593!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 19730 invoked from network); 21 Aug 2014 11:10:06 -0000 Received: from mail-oi0-f53.google.com (HELO mail-oi0-f53.google.com) (209.85.218.53) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 11:10:06 -0000 Received: by mail-oi0-f53.google.com with SMTP id e131so6612993oig.40 for ; Thu, 21 Aug 2014 04:10:04 -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=mg5cQqoZJIOGKu+XFYN0QOExhp7NRjTy8xG56SO9Nl4=; b=yqX/TSSQEwPMjwhigsV8zgbv9+RJ4Ga0ydEygypU/Ygn32Q09HLsNURMWUIVydgFv7 EHBxBeilMd/Pb1HqMscUdRYN6wqBSGtf8xnO15FpB67AGnPEbfaSgedswYP61A3QJ4ZQ qVT2vLSvAkSDpsO/2o9FpPOZozndKcsk2+qvciEkbdGWCHadU5STwaX03zOB4I3zxgsv eRNTpCpyXMhq3nAHi8B2fuswh4xwAU/dy0jv0GSjEfOuCx5qMSBYkeG1YvDNRqCnrYvb sTlnJv7nwzNp2S+WqtD5oi/gL57hLw876+uUq91ZO++QfI2ZRQL+OvX7dfDpi/71mC+e s7PQ== MIME-Version: 1.0 X-Received: by 10.182.104.104 with SMTP id gd8mr53304428obb.17.1408619404326; Thu, 21 Aug 2014 04:10:04 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Thu, 21 Aug 2014 04:10:04 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 12:10:04 +0100 Message-ID: From: Thomas Leonard To: David 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11 August 2014 14:04, David Scott wrote: > > On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard wrote: >> >> Has anyone made any tools for profiling on Xen? > > > The closest thing I can think of is xentrace/xenalyse: > > http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenalyze/ > > This will tell you what Xen can see: eg how the vCPUs map to pCPUs and when > they block on events etc. Thanks. For now, I've pinned dom0 to CPU 0 and my unikernel to CPU 1. >> I want to see why my network service on Xen/ARM only gets about 5 MB/s >> (while a Linux guest gets about 45 MB/s). >> >> I tried compiling with profiling on ("true: profile" in the _tags) and >> wrote a __gnu_mcount_nc function to dump all the results to a buffer >> [1], plus a script to turn the addresses back into symbols and guess >> the nesting (a bit unreliable, as it doesn't tell you when the >> function finishes). >> >> Here's an example CSV of the output (the unikernel waits for a TCP >> connection and then streams data to it as fast as it can): >> >> http://test.roscidus.com/static/sample-output.csv.bz2 >> >> I haven't checked it carefully to see if it's correct - this is just >> an example of the kind of output. It shows the call graph and the >> (cumulative) time spent in each function. Since it doesn't know the >> end times, it assumes a function runs until one of its parents calls >> something else. > > > 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! 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 From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 12:42:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 12:42: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 1XKRhT-00072a-46; Thu, 21 Aug 2014 12:42:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKRhR-00072T-Sa for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 12:42:41 +0000 Received: from [193.109.254.147:16042] by server-4.bemta-14.messagelabs.com id 0D/49-23592-149E5F35; Thu, 21 Aug 2014 12:42:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1408624960!12252183!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27715 invoked from network); 21 Aug 2014 12:42:40 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-27.messagelabs.com with SMTP; 21 Aug 2014 12:42:40 -0000 Received: (qmail 257 invoked by uid 634); 21 Aug 2014 12:42:39 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 21 Aug 2014 13:42:38 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 21 Aug 2014 07:42:35 -0500 Message-Id: <0FA5A71C-B120-4C64-AB51-3957864E727F@recoil.org> References: To: buzz heavyyear 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] static_website+ip X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2572878635582506846==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2572878635582506846== Content-Type: multipart/alternative; boundary="Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C" --Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Nick, Are your OPAM libraries up to date? mirage-skeleton requires the latest = libraries usually (until OPAM 1.2 is released, and we can specify the = exact versions we need from the command line). Try "opam update -u" to get the latest library set and "git pull" your = mirage-skeleton to the latest version cheers, Anil On 20 Aug 2014, at 12:19, buzz heavyyear = wrote: > Hi, >=20 > I've just come back to looking at this example and I guess things have = changed. When I initially tried to make this I got : >=20 >=20 > File "dispatch.ml", line 15, characters 41-46: > Error: Unbound module Clock > Command exited with code 2. > make: *** [main.native] Error 10 >=20 >=20 > So, I added "mirage-clock-unix" to add_to_ocamlfind_libraries in = config.ml and moved onto the next one, which I haven't been able to = figure out - would be very grateful if someone could give me a pointer = on how to fix this: >=20 > File "dispatch.ml", line 29, characters 19-52: > Error: Unbound module OS.Start_info >=20 > Best > Nick > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Nick,

Are your OPAM libraries up to date? =  mirage-skeleton requires the latest libraries usually (until OPAM = 1.2 is released, and we can specify the exact versions we need from the = command line).

Try "opam update -u" to get the = latest library set and "git pull" your mirage-skeleton to the latest = version

cheers,
Anil

On 20 Aug 2014, at 12:19, buzz heavyyear <buzzheavyyear@hotmail.com>= ; wrote:

Hi,

I've just = come back to looking at this example and I guess things have changed. = When I initially tried to make this I got :


File = "dispatch.ml", line 15, characters 41-46:
Error: Unbound module = Clock
Command exited with code 2.
make: *** [main.native] Error = 10


So, I added "mirage-clock-unix" to = add_to_ocamlfind_libraries in config.ml and moved onto the next one, = which I haven't been able to figure out  - would be very grateful = if someone could give me a pointer on how to fix this:

File = "dispatch.ml", line 29, characters 19-52:
Error: Unbound module = OS.Start_info

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

= --Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C-- --===============2572878635582506846== 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 --===============2572878635582506846==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 12:42:48 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 12:42: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 1XKRhT-00072a-46; Thu, 21 Aug 2014 12:42:43 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKRhR-00072T-Sa for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 12:42:41 +0000 Received: from [193.109.254.147:16042] by server-4.bemta-14.messagelabs.com id 0D/49-23592-149E5F35; Thu, 21 Aug 2014 12:42:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-27.messagelabs.com!1408624960!12252183!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=1.1 required=7.0 tests=BODY_RANDOM_LONG, HTML_40_50,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27715 invoked from network); 21 Aug 2014 12:42:40 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-27.messagelabs.com with SMTP; 21 Aug 2014 12:42:40 -0000 Received: (qmail 257 invoked by uid 634); 21 Aug 2014 12:42:39 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 21 Aug 2014 13:42:38 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: Date: Thu, 21 Aug 2014 07:42:35 -0500 Message-Id: <0FA5A71C-B120-4C64-AB51-3957864E727F@recoil.org> References: To: buzz heavyyear 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] static_website+ip X-BeenThere: mirageos-devel@lists.xenproject.org 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="===============2572878635582506846==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2572878635582506846== Content-Type: multipart/alternative; boundary="Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C" --Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Nick, Are your OPAM libraries up to date? mirage-skeleton requires the latest = libraries usually (until OPAM 1.2 is released, and we can specify the = exact versions we need from the command line). Try "opam update -u" to get the latest library set and "git pull" your = mirage-skeleton to the latest version cheers, Anil On 20 Aug 2014, at 12:19, buzz heavyyear = wrote: > Hi, >=20 > I've just come back to looking at this example and I guess things have = changed. When I initially tried to make this I got : >=20 >=20 > File "dispatch.ml", line 15, characters 41-46: > Error: Unbound module Clock > Command exited with code 2. > make: *** [main.native] Error 10 >=20 >=20 > So, I added "mirage-clock-unix" to add_to_ocamlfind_libraries in = config.ml and moved onto the next one, which I haven't been able to = figure out - would be very grateful if someone could give me a pointer = on how to fix this: >=20 > File "dispatch.ml", line 29, characters 19-52: > Error: Unbound module OS.Start_info >=20 > Best > Nick > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Nick,

Are your OPAM libraries up to date? =  mirage-skeleton requires the latest libraries usually (until OPAM = 1.2 is released, and we can specify the exact versions we need from the = command line).

Try "opam update -u" to get the = latest library set and "git pull" your mirage-skeleton to the latest = version

cheers,
Anil

On 20 Aug 2014, at 12:19, buzz heavyyear <buzzheavyyear@hotmail.com>= ; wrote:

Hi,

I've just = come back to looking at this example and I guess things have changed. = When I initially tried to make this I got :


File = "dispatch.ml", line 15, characters 41-46:
Error: Unbound module = Clock
Command exited with code 2.
make: *** [main.native] Error = 10


So, I added "mirage-clock-unix" to = add_to_ocamlfind_libraries in config.ml and moved onto the next one, = which I haven't been able to figure out  - would be very grateful = if someone could give me a pointer on how to fix this:

File = "dispatch.ml", line 29, characters 19-52:
Error: Unbound module = OS.Start_info

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

= --Apple-Mail=_1AB8EEDA-B2C6-4EC0-AF56-819E91841A2C-- --===============2572878635582506846== 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 --===============2572878635582506846==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 14:09:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 14:09: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 1XKT3B-0007jI-35; Thu, 21 Aug 2014 14:09:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKT39-0007jB-OL for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 14:09:11 +0000 Received: from [85.158.139.211:31067] by server-9.bemta-5.messagelabs.com id DD/E7-20744-78DF5F35; Thu, 21 Aug 2014 14:09:11 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1408630150!5906785!1 X-Originating-IP: [209.85.212.176] 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 26580 invoked from network); 21 Aug 2014 14:09:10 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 14:09:10 -0000 Received: by mail-wi0-f176.google.com with SMTP id bs8so8764712wib.3 for ; Thu, 21 Aug 2014 07:09:09 -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=dnwzdjoDuNdlnfY6JwdN3ba1FETE8sKxeAd1VPyOk58=; b=QEHIHnCDmFGx9w7Pw+5XGaJegFst5SLrKZMQrrDV5p+GbvOvBTTPBwkm0Ub3JDv1I1 3rZ1t+T1R95bJA8pXTGvNzcRnvahndJB9F2EDQ0W98qBsuV1WCL+97jX6SpNkZKakSWK /wTwGXvCvy2NkQyj3JwU5tYIL14ajB3687XvrmTueR6MlueUcOz4G4EOmRTevQkmv7RM TEU57J7sDl278uWFzoen6K2vG3srTx+d1NKyCbcXx1JIAJa74WRtoD4paCjJUf8JOsNG Y7scLbWgD/YjPuPsxQYj20OoSzUpoxSFo4DN0Sf7xQq0wVNnHzXQOJmSfInlTsjxGVbJ 0r1w== X-Received: by 10.194.186.178 with SMTP id fl18mr56958596wjc.8.1408630149824; Thu, 21 Aug 2014 07:09:09 -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 y6sm7997924wia.0.2014.08.21.07.09.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 07:09:07 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 21 Aug 2014 15:09:06 +0100 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> 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. Do you think the -fno-omit-frame-pointer configure options could also help to have more precise profiling information? 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 _______________________________________________ MirageOS-devel 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 Aug 21 14:09:15 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 14:09: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 1XKT3B-0007jI-35; Thu, 21 Aug 2014 14:09:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKT39-0007jB-OL for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 14:09:11 +0000 Received: from [85.158.139.211:31067] by server-9.bemta-5.messagelabs.com id DD/E7-20744-78DF5F35; Thu, 21 Aug 2014 14:09:11 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-14.tower-206.messagelabs.com!1408630150!5906785!1 X-Originating-IP: [209.85.212.176] 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 26580 invoked from network); 21 Aug 2014 14:09:10 -0000 Received: from mail-wi0-f176.google.com (HELO mail-wi0-f176.google.com) (209.85.212.176) by server-14.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 14:09:10 -0000 Received: by mail-wi0-f176.google.com with SMTP id bs8so8764712wib.3 for ; Thu, 21 Aug 2014 07:09:09 -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=dnwzdjoDuNdlnfY6JwdN3ba1FETE8sKxeAd1VPyOk58=; b=QEHIHnCDmFGx9w7Pw+5XGaJegFst5SLrKZMQrrDV5p+GbvOvBTTPBwkm0Ub3JDv1I1 3rZ1t+T1R95bJA8pXTGvNzcRnvahndJB9F2EDQ0W98qBsuV1WCL+97jX6SpNkZKakSWK /wTwGXvCvy2NkQyj3JwU5tYIL14ajB3687XvrmTueR6MlueUcOz4G4EOmRTevQkmv7RM TEU57J7sDl278uWFzoen6K2vG3srTx+d1NKyCbcXx1JIAJa74WRtoD4paCjJUf8JOsNG Y7scLbWgD/YjPuPsxQYj20OoSzUpoxSFo4DN0Sf7xQq0wVNnHzXQOJmSfInlTsjxGVbJ 0r1w== X-Received: by 10.194.186.178 with SMTP id fl18mr56958596wjc.8.1408630149824; Thu, 21 Aug 2014 07:09:09 -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 y6sm7997924wia.0.2014.08.21.07.09.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 07:09:07 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 21 Aug 2014 15:09:06 +0100 Message-Id: References: To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> 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. Do you think the -fno-omit-frame-pointer configure options could also help to have more precise profiling information? 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 _______________________________________________ MirageOS-devel 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 Aug 21 14:31:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 14:31: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 1XKTP5-00088G-29; Thu, 21 Aug 2014 14:31:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTP3-00088B-86 for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 14:31:49 +0000 Received: from [85.158.139.211:47887] by server-4.bemta-5.messagelabs.com id 60/05-10551-4D206F35; Thu, 21 Aug 2014 14:31:48 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1408631506!3746731!1 X-Originating-IP: [209.85.214.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 9373 invoked from network); 21 Aug 2014 14:31:47 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 14:31:47 -0000 Received: by mail-ob0-f181.google.com with SMTP id va2so7499403obc.40 for ; Thu, 21 Aug 2014 07:31:46 -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=2jFavaAwK6KbXti77uLYCzx2rxBpIxNvw5F7nWWd4+0=; b=WDdOX6cS0Jpr0cfxNKeOlqy+M6+pgM4lD+Z09Y3qD3IIE/EGSNxm4bdyzUjXrt8v4Y PMkuNJCGw5rLlAyfgrCelTmcBu6exEX8cswzA2GtWe+Ma3oY4Iy4vnZjXAXOsYxx6IRr 99qY3R7Ih5aS1epvu/A00w1qcTE0zUIHMgxOcb4G1UisIlfM4F3CN2l1bebALEFsvWhd P2q8pWbErni414ZzAY735RZVdIxcZY/em8Vqyb8E5ahrD7YaaSlsz33CSS8uENhST2qB CzmhEvZsUepky7A5n3nApZElWg7YQNo7ca235oxzBDb0Uo/9Mz4PApGjwpS7TebbEn4p tx0w== MIME-Version: 1.0 X-Received: by 10.60.121.67 with SMTP id li3mr54911805oeb.17.1408631506143; Thu, 21 Aug 2014 07:31:46 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Thu, 21 Aug 2014 07:31:46 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 15:31:46 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org 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 From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 14:31:52 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 14:31: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 1XKTP5-00088G-29; Thu, 21 Aug 2014 14:31:51 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTP3-00088B-86 for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 14:31:49 +0000 Received: from [85.158.139.211:47887] by server-4.bemta-5.messagelabs.com id 60/05-10551-4D206F35; Thu, 21 Aug 2014 14:31:48 +0000 X-Env-Sender: talex5@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1408631506!3746731!1 X-Originating-IP: [209.85.214.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 9373 invoked from network); 21 Aug 2014 14:31:47 -0000 Received: from mail-ob0-f181.google.com (HELO mail-ob0-f181.google.com) (209.85.214.181) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 14:31:47 -0000 Received: by mail-ob0-f181.google.com with SMTP id va2so7499403obc.40 for ; Thu, 21 Aug 2014 07:31:46 -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=2jFavaAwK6KbXti77uLYCzx2rxBpIxNvw5F7nWWd4+0=; b=WDdOX6cS0Jpr0cfxNKeOlqy+M6+pgM4lD+Z09Y3qD3IIE/EGSNxm4bdyzUjXrt8v4Y PMkuNJCGw5rLlAyfgrCelTmcBu6exEX8cswzA2GtWe+Ma3oY4Iy4vnZjXAXOsYxx6IRr 99qY3R7Ih5aS1epvu/A00w1qcTE0zUIHMgxOcb4G1UisIlfM4F3CN2l1bebALEFsvWhd P2q8pWbErni414ZzAY735RZVdIxcZY/em8Vqyb8E5ahrD7YaaSlsz33CSS8uENhST2qB CzmhEvZsUepky7A5n3nApZElWg7YQNo7ca235oxzBDb0Uo/9Mz4PApGjwpS7TebbEn4p tx0w== MIME-Version: 1.0 X-Received: by 10.60.121.67 with SMTP id li3mr54911805oeb.17.1408631506143; Thu, 21 Aug 2014 07:31:46 -0700 (PDT) Received: by 10.76.170.229 with HTTP; Thu, 21 Aug 2014 07:31:46 -0700 (PDT) In-Reply-To: References: Date: Thu, 21 Aug 2014 15:31:46 +0100 Message-ID: From: Thomas Leonard To: Thomas Gazagnaire 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org 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 From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 15:01:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 15:01: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 1XKTrI-000086-4m; Thu, 21 Aug 2014 15:01:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTrH-000081-5G for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 15:00:59 +0000 Received: from [85.158.139.211:30092] by server-12.bemta-5.messagelabs.com id B3/84-22251-AA906F35; Thu, 21 Aug 2014 15:00:58 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1408633257!7202680!1 X-Originating-IP: [74.125.82.179] 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 16721 invoked from network); 21 Aug 2014 15:00:57 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 15:00:57 -0000 Received: by mail-we0-f179.google.com with SMTP id u57so9409156wes.38 for ; Thu, 21 Aug 2014 08:00:57 -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=eV/BVjWzU1he4ymKBePr5Aa5MAI5lzNa7lspLd2PeAI=; b=PUPvmLneg6CJ2Me8uie1jcyKxc1HkNHPOPcKgAkDyVHsaHQjMjMqVGZtlOaXI3B7KW A0mbPB7kTIbMrnl6TEMv+QOfklk1uEpXF3RW0/MD7gRP2+FIO3VSA7N/VhQ9ATJ+jxdz KJ8dMcyQQlk4u2rr+38eNUbskh1YJKzZRd8xJDXLecOAAsn9U37MgkUsy0CHG4svlZXD OP2vIdZnt7WHJPlJaQId0CU1FB79ukCyC3PE3pExvaYQ6B/ETMoZi9zD8CX7Z4j7Jtxy qBUM0hMP8xo3klPfSS6TT0frZNi/JRjkyQnwaPHWP2TVITg4cDGulL3OkvmgESzOQuLC 89fQ== X-Received: by 10.194.95.198 with SMTP id dm6mr3127479wjb.131.1408633257293; Thu, 21 Aug 2014 08:00:57 -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 ca8sm67351761wjc.0.2014.08.21.08.00.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 08:00:54 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 21 Aug 2014 16:00:53 +0100 Message-Id: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> References: To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> I'm settting up a 4.01 switch with profiling on. > > Thanks! done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs: https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp Thomas > >> 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 From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 15:01:02 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 15:01: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 1XKTrI-000086-4m; Thu, 21 Aug 2014 15:01:00 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTrH-000081-5G for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 15:00:59 +0000 Received: from [85.158.139.211:30092] by server-12.bemta-5.messagelabs.com id B3/84-22251-AA906F35; Thu, 21 Aug 2014 15:00:58 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1408633257!7202680!1 X-Originating-IP: [74.125.82.179] 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 16721 invoked from network); 21 Aug 2014 15:00:57 -0000 Received: from mail-we0-f179.google.com (HELO mail-we0-f179.google.com) (74.125.82.179) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 15:00:57 -0000 Received: by mail-we0-f179.google.com with SMTP id u57so9409156wes.38 for ; Thu, 21 Aug 2014 08:00:57 -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=eV/BVjWzU1he4ymKBePr5Aa5MAI5lzNa7lspLd2PeAI=; b=PUPvmLneg6CJ2Me8uie1jcyKxc1HkNHPOPcKgAkDyVHsaHQjMjMqVGZtlOaXI3B7KW A0mbPB7kTIbMrnl6TEMv+QOfklk1uEpXF3RW0/MD7gRP2+FIO3VSA7N/VhQ9ATJ+jxdz KJ8dMcyQQlk4u2rr+38eNUbskh1YJKzZRd8xJDXLecOAAsn9U37MgkUsy0CHG4svlZXD OP2vIdZnt7WHJPlJaQId0CU1FB79ukCyC3PE3pExvaYQ6B/ETMoZi9zD8CX7Z4j7Jtxy qBUM0hMP8xo3klPfSS6TT0frZNi/JRjkyQnwaPHWP2TVITg4cDGulL3OkvmgESzOQuLC 89fQ== X-Received: by 10.194.95.198 with SMTP id dm6mr3127479wjb.131.1408633257293; Thu, 21 Aug 2014 08:00:57 -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 ca8sm67351761wjc.0.2014.08.21.08.00.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 08:00:54 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: Date: Thu, 21 Aug 2014 16:00:53 +0100 Message-Id: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> References: To: Thomas Leonard X-Mailer: Apple Mail (2.1878.6) 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> I'm settting up a 4.01 switch with profiling on. > > Thanks! done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs: https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp Thomas > >> 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 From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 15:08:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 15:08:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTym-0000Aq-T7; Thu, 21 Aug 2014 15:08:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTyl-0000Aj-QZ for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 15:08:43 +0000 Received: from [85.158.137.68:29396] by server-12.bemta-3.messagelabs.com id FF/7E-07189-B7B06F35; Thu, 21 Aug 2014 15:08:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1408633722!15099222!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 10091 invoked from network); 21 Aug 2014 15:08:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 21 Aug 2014 15:08:42 -0000 Received: (qmail 12614 invoked by uid 634); 21 Aug 2014 15:08:39 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 21 Aug 2014 16:08:38 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> Date: Thu, 21 Aug 2014 10:08:36 -0500 Message-Id: <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> References: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Louis Gesbert , "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 On 21 Aug 2014, at 10:00, Thomas Gazagnaire wrote: >>> I'm settting up a 4.01 switch with profiling on. >> >> Thanks! > > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs: > > https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp This is really useful! The lack of extensibility in the env var bugs me quite a lot, since it's not possible to locally override the OCAMLPARAM with other fields (such as -bin-annot). Do you think that an OPAM feature request to support a += field in env is worthwhile at this late stage? I'm thinking that this would be useful for environment variables that support colon-separated delimiters (which I believe OCAMLPARAM does, but I can't find any documentation for it in the manual). -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 Aug 21 15:08:46 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 15:08:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTym-0000Aq-T7; Thu, 21 Aug 2014 15:08:44 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKTyl-0000Aj-QZ for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 15:08:43 +0000 Received: from [85.158.137.68:29396] by server-12.bemta-3.messagelabs.com id FF/7E-07189-B7B06F35; Thu, 21 Aug 2014 15:08:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1408633722!15099222!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 10091 invoked from network); 21 Aug 2014 15:08:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 21 Aug 2014 15:08:42 -0000 Received: (qmail 12614 invoked by uid 634); 21 Aug 2014 15:08:39 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from 50-203-222-3-static.hfc.comcastbusiness.net (HELO [172.20.87.228]) (50.203.222.3) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 21 Aug 2014 16:08:38 +0100 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Anil Madhavapeddy In-Reply-To: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> Date: Thu, 21 Aug 2014 10:08:36 -0500 Message-Id: <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> References: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1878.6) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Louis Gesbert , "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 On 21 Aug 2014, at 10:00, Thomas Gazagnaire wrote: >>> I'm settting up a 4.01 switch with profiling on. >> >> Thanks! > > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs: > > https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp This is really useful! The lack of extensibility in the env var bugs me quite a lot, since it's not possible to locally override the OCAMLPARAM with other fields (such as -bin-annot). Do you think that an OPAM feature request to support a += field in env is worthwhile at this late stage? I'm thinking that this would be useful for environment variables that support colon-separated delimiters (which I believe OCAMLPARAM does, but I can't find any documentation for it in the manual). -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 Aug 21 15:31:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 15:31: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 1XKUKr-0000L0-UO; Thu, 21 Aug 2014 15:31:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKUKq-0000Kd-6r for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 15:31:32 +0000 Received: from [85.158.137.68:14608] by server-4.bemta-3.messagelabs.com id 2B/C2-18709-3D016F35; Thu, 21 Aug 2014 15:31:31 +0000 X-Env-Sender: louis.gesbert@ocamlpro.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1408635088!14995872!1 X-Originating-IP: [212.227.17.10] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7975 invoked from network); 21 Aug 2014 15:31:28 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.17.10) by server-10.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Aug 2014 15:31:28 -0000 Received: from agaric.localnet (jua06-3-88-189-115-104.fbx.proxad.net [88.189.115.104]) by mrelayeu.kundenserver.de (node=mreue105) with ESMTP (Nemesis) id 0Lo1CS-1WjDdv2XLE-00g2I5; Thu, 21 Aug 2014 17:31:28 +0200 From: Louis Gesbert To: Anil Madhavapeddy Date: Thu, 21 Aug 2014 17:31:25 +0200 Message-ID: <12252345.9bLNCYt63Q@agaric> Organization: OCamlPro User-Agent: KMail/4.12.4 (Linux/3.14-2-amd64; KDE/4.13.3; x86_64; ; ) In-Reply-To: <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> References: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> MIME-Version: 1.0 X-Provags-ID: V02:K0:YL8eOtj5mbLKNqdtNebKMY1JfTt2mYFS4YEZ4aAFMmZ +YuJLVtk5wQ1uwUm+SdcMDhULIeDjnSJIJlnoULn9gudWiWgHR Qk71B3mbcBHtxOPDuviIKds5jVfoOXfbAdu5pQwPIb9o8+XVK5 JovvtsQElnSg/jnnZX6jZ43m7ygZlrVEkQkXO7qPNJHbWFL4n7 LTqkLg8b1fAY2v9P5C9G37G8E9XulMs3DFIWjl5PnrHjYvsa9W PuZYtphRiLVoFMcfWzDNlz9T7QZe3aAVHgvWov5LM9MMd7mlS8 qpcxCx9tAKUynrr7IlyPJZXRp/wBsnDM6fslu4MO8nY9UKoDvG hzxfrXjkb8B2AErj1a8Y= X-UI-Out-Filterresults: notjunk:1; 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="===============1990563700763927757==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============1990563700763927757== Content-Type: multipart/alternative; boundary="nextPart3405845.DqviTjsZZ6" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart3405845.DqviTjsZZ6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" OPAM does have some handling of env variable extension ; the documentat= ion is indeed lacking though, but we do have the following in the dev-m= anual (for opam files): ``` :=3D ... ?env: [ + ] :=3D IDENT STRING :=3D =E2=80=99=3D=E2=80=99 | =E2=80=99+=3D=E2=80=99 | =E2=80=99=3D= +=E2=80=99 | =E2=80=99:=3D=E2=80=99 | =E2=80=99=3D:=E2=80=99 * env is the list of environment variables to set in the given compiler= switch: =E2=80=93 VAR =3D "value" set the variable to the given value; =E2=80=93 VAR +=3D "value" prepend the given value to the variable; =E2=80=93 VAR =3D+ "value" append the given value to the variable; =E2=80=93 VAR :=3D "value" prepend the given value to the variable, sep= arated by a colon. If the variable was empty, add the colon anyway. =E2=80=93 VAR =3D: "value" append the given value to the variable, sepa= rated by a colon. If the variable was empty, add the colon anyway. ``` Le jeudi 21 ao=C3=BBt 2014, 10:08:36 Anil Madhavapeddy a =C3=A9crit : > On 21 Aug 2014, at 10:00, Thomas Gazagnaire w= rote: >=20 > >>> I'm settting up a 4.01 switch with profiling on. > >>=20 > >> Thanks! > >=20 > > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt i= nvocation in the 4.01.0+profile switch. Feel free to modify the compile= r description to fill you needs: > >=20 > > https://github.com/ocaml/opam-repository/blob/master/compilers/4.01= .0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp >=20 > This is really useful! The lack of extensibility in the env var bugs= me quite a lot, since it's not possible to locally override the OCAMLP= ARAM with other fields (such as -bin-annot). >=20 > Do you think that an OPAM feature request to support a +=3D field in = env is worthwhile at this late stage? I'm thinking that this would be = useful for environment variables that support colon-separated delimiter= s (which I believe OCAMLPARAM does, but I can't find any documentation = for it in the manual). >=20 > -anil --nextPart3405845.DqviTjsZZ6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

OPA= M does have some handling of env variable extension ; the documentation= is indeed lacking though, but we do have the following in the dev-manu= al (for opam files):

 

```=

<= ;file> :=3D

= ...

= ?env: [ <env>+ ]

 

<= ;env> :=3D IDENT <eq> STRING

<= ;eq> :=3D =E2=80=99=3D=E2=80=99 | =E2=80=99+=3D=E2=80=99 | =E2=80=99= =3D+=E2=80=99 | =E2=80=99:=3D=E2=80=99 | =E2=80=99=3D:=E2=80=99

 

 

* e= nv is the list of environment variables to set in the given compiler sw= itch:

=E2= =80=93 VAR =3D "value" set the variable to the given value;

=E2= =80=93 VAR +=3D "value" prepend the given value to the variab= le;

=E2= =80=93 VAR =3D+ "value" append the given value to the variabl= e;

=E2= =80=93 VAR :=3D "value" prepend the given value to the variab= le, separated by a colon. If the variable

was= empty, add the colon anyway.

=E2= =80=93 VAR =3D: "value" append the given value to the variabl= e, separated by a colon. If the variable

was= empty, add the colon anyway.

```=

 

 

 

 

Le = jeudi 21 ao=C3=BBt 2014, 10:08:36 Anil Madhavapeddy a =C3=A9crit=C2=A0:=

>= ; On 21 Aug 2014, at 10:00, Thomas Gazagnaire <thomas@gazagnaire.org= > wrote:

>= ;

>= ; >>> I'm settting up a 4.01 switch with profiling on.

>= ; >>

>= ; >> Thanks!

>= ; >

>= ; > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlop= t invocation in the 4.01.0+profile switch. Feel free to modify the comp= iler description to fill you needs:

>= ; >

>= ; > https://github.com/ocaml/opam-repository/blob/master/compilers/4= .01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp

>= ;

>= ; This is really useful! The lack of extensibility in the env var bugs= me quite a lot, since it's not possible to locally override the OCAMLP= ARAM with other fields (such as -bin-annot).

>= ;

>= ; Do you think that an OPAM feature request to support a +=3D field in = env is worthwhile at this late stage? I'm thinking that this would be = useful for environment variables that support colon-separated delimiter= s (which I believe OCAMLPARAM does, but I can't find any documentation = for it in the manual).

>= ;

>= ; -anil

 

--nextPart3405845.DqviTjsZZ6-- --===============1990563700763927757== 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 --===============1990563700763927757==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 15:31:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 15:31: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 1XKUKr-0000L0-UO; Thu, 21 Aug 2014 15:31:33 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKUKq-0000Kd-6r for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 15:31:32 +0000 Received: from [85.158.137.68:14608] by server-4.bemta-3.messagelabs.com id 2B/C2-18709-3D016F35; Thu, 21 Aug 2014 15:31:31 +0000 X-Env-Sender: louis.gesbert@ocamlpro.com X-Msg-Ref: server-10.tower-31.messagelabs.com!1408635088!14995872!1 X-Originating-IP: [212.227.17.10] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n,sa_preprocessor: QmFkIElQOiAyMTIuMjI3LjE3LjEwID0+IDY3OTMx\n,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7975 invoked from network); 21 Aug 2014 15:31:28 -0000 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.17.10) by server-10.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 21 Aug 2014 15:31:28 -0000 Received: from agaric.localnet (jua06-3-88-189-115-104.fbx.proxad.net [88.189.115.104]) by mrelayeu.kundenserver.de (node=mreue105) with ESMTP (Nemesis) id 0Lo1CS-1WjDdv2XLE-00g2I5; Thu, 21 Aug 2014 17:31:28 +0200 From: Louis Gesbert To: Anil Madhavapeddy Date: Thu, 21 Aug 2014 17:31:25 +0200 Message-ID: <12252345.9bLNCYt63Q@agaric> Organization: OCamlPro User-Agent: KMail/4.12.4 (Linux/3.14-2-amd64; KDE/4.13.3; x86_64; ; ) In-Reply-To: <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> References: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> MIME-Version: 1.0 X-Provags-ID: V02:K0:YL8eOtj5mbLKNqdtNebKMY1JfTt2mYFS4YEZ4aAFMmZ +YuJLVtk5wQ1uwUm+SdcMDhULIeDjnSJIJlnoULn9gudWiWgHR Qk71B3mbcBHtxOPDuviIKds5jVfoOXfbAdu5pQwPIb9o8+XVK5 JovvtsQElnSg/jnnZX6jZ43m7ygZlrVEkQkXO7qPNJHbWFL4n7 LTqkLg8b1fAY2v9P5C9G37G8E9XulMs3DFIWjl5PnrHjYvsa9W PuZYtphRiLVoFMcfWzDNlz9T7QZe3aAVHgvWov5LM9MMd7mlS8 qpcxCx9tAKUynrr7IlyPJZXRp/wBsnDM6fslu4MO8nY9UKoDvG hzxfrXjkb8B2AErj1a8Y= X-UI-Out-Filterresults: notjunk:1; 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="===============1990563700763927757==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============1990563700763927757== Content-Type: multipart/alternative; boundary="nextPart3405845.DqviTjsZZ6" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart3405845.DqviTjsZZ6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" OPAM does have some handling of env variable extension ; the documentat= ion is indeed lacking though, but we do have the following in the dev-m= anual (for opam files): ``` :=3D ... ?env: [ + ] :=3D IDENT STRING :=3D =E2=80=99=3D=E2=80=99 | =E2=80=99+=3D=E2=80=99 | =E2=80=99=3D= +=E2=80=99 | =E2=80=99:=3D=E2=80=99 | =E2=80=99=3D:=E2=80=99 * env is the list of environment variables to set in the given compiler= switch: =E2=80=93 VAR =3D "value" set the variable to the given value; =E2=80=93 VAR +=3D "value" prepend the given value to the variable; =E2=80=93 VAR =3D+ "value" append the given value to the variable; =E2=80=93 VAR :=3D "value" prepend the given value to the variable, sep= arated by a colon. If the variable was empty, add the colon anyway. =E2=80=93 VAR =3D: "value" append the given value to the variable, sepa= rated by a colon. If the variable was empty, add the colon anyway. ``` Le jeudi 21 ao=C3=BBt 2014, 10:08:36 Anil Madhavapeddy a =C3=A9crit : > On 21 Aug 2014, at 10:00, Thomas Gazagnaire w= rote: >=20 > >>> I'm settting up a 4.01 switch with profiling on. > >>=20 > >> Thanks! > >=20 > > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt i= nvocation in the 4.01.0+profile switch. Feel free to modify the compile= r description to fill you needs: > >=20 > > https://github.com/ocaml/opam-repository/blob/master/compilers/4.01= .0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp >=20 > This is really useful! The lack of extensibility in the env var bugs= me quite a lot, since it's not possible to locally override the OCAMLP= ARAM with other fields (such as -bin-annot). >=20 > Do you think that an OPAM feature request to support a +=3D field in = env is worthwhile at this late stage? I'm thinking that this would be = useful for environment variables that support colon-separated delimiter= s (which I believe OCAMLPARAM does, but I can't find any documentation = for it in the manual). >=20 > -anil --nextPart3405845.DqviTjsZZ6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

OPA= M does have some handling of env variable extension ; the documentation= is indeed lacking though, but we do have the following in the dev-manu= al (for opam files):

 

```=

<= ;file> :=3D

= ...

= ?env: [ <env>+ ]

 

<= ;env> :=3D IDENT <eq> STRING

<= ;eq> :=3D =E2=80=99=3D=E2=80=99 | =E2=80=99+=3D=E2=80=99 | =E2=80=99= =3D+=E2=80=99 | =E2=80=99:=3D=E2=80=99 | =E2=80=99=3D:=E2=80=99

 

 

* e= nv is the list of environment variables to set in the given compiler sw= itch:

=E2= =80=93 VAR =3D "value" set the variable to the given value;

=E2= =80=93 VAR +=3D "value" prepend the given value to the variab= le;

=E2= =80=93 VAR =3D+ "value" append the given value to the variabl= e;

=E2= =80=93 VAR :=3D "value" prepend the given value to the variab= le, separated by a colon. If the variable

was= empty, add the colon anyway.

=E2= =80=93 VAR =3D: "value" append the given value to the variabl= e, separated by a colon. If the variable

was= empty, add the colon anyway.

```=

 

 

 

 

Le = jeudi 21 ao=C3=BBt 2014, 10:08:36 Anil Madhavapeddy a =C3=A9crit=C2=A0:=

>= ; On 21 Aug 2014, at 10:00, Thomas Gazagnaire <thomas@gazagnaire.org= > wrote:

>= ;

>= ; >>> I'm settting up a 4.01 switch with profiling on.

>= ; >>

>= ; >> Thanks!

>= ; >

>= ; > done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlop= t invocation in the 4.01.0+profile switch. Feel free to modify the comp= iler description to fill you needs:

>= ; >

>= ; > https://github.com/ocaml/opam-repository/blob/master/compilers/4= .01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp

>= ;

>= ; This is really useful! The lack of extensibility in the env var bugs= me quite a lot, since it's not possible to locally override the OCAMLP= ARAM with other fields (such as -bin-annot).

>= ;

>= ; Do you think that an OPAM feature request to support a +=3D field in = env is worthwhile at this late stage? I'm thinking that this would be = useful for environment variables that support colon-separated delimiter= s (which I believe OCAMLPARAM does, but I can't find any documentation = for it in the manual).

>= ;

>= ; -anil

 

--nextPart3405845.DqviTjsZZ6-- --===============1990563700763927757== 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 --===============1990563700763927757==-- From mirageos-devel-bounces@lists.xenproject.org Thu Aug 21 16:43:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 16:43: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 1XKVSV-0001uU-TZ; Thu, 21 Aug 2014 16:43:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKVSV-0001uP-96 for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 16:43:31 +0000 Received: from [85.158.139.211:45420] by server-7.bemta-5.messagelabs.com id FB/EF-30869-2B126F35; Thu, 21 Aug 2014 16:43:30 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1408639409!3784484!1 X-Originating-IP: [74.125.82.176] 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 12066 invoked from network); 21 Aug 2014 16:43:30 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 16:43:30 -0000 Received: by mail-we0-f176.google.com with SMTP id q58so9509996wes.7 for ; Thu, 21 Aug 2014 09:43:29 -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=VyJvNxiuNiN8GX+LKTUsgIrub31pEXkl9fPaewEmQ00=; b=vIY3ZcvdzZgRzIl4zAzkdB3sSqqfvqOiwBqb5JSnBFBqTpl+3NrgzlGHA2nnQUivZ0 K2Cp/WtvvOCDMKBge0ycyWAnVOTGKzWtBU7blEUHkZ81VNV2OZmJR2DjvULsMGSOM8tD AdiMolpvRP5SI4aru59Yfo4YZFjepIlPY1QtLG8v2fdKkw+H/NlO5zimOP6c1rgFxziU KEmyEPObFq82Okt24TDqCpfd5/M9awSV4iDwu5jjVwgPO9wl3H6jv4QVEnwvAry4N8as gVNDx2wsg5vU1eg/C+4lZguPXfIxwdGc5PnMvzC1VGJ96UN1Nb67u8rTD5bKK0KBoMly iy1w== X-Received: by 10.194.23.8 with SMTP id i8mr34270103wjf.104.1408639409732; Thu, 21 Aug 2014 09:43:29 -0700 (PDT) Received: from ?IPv6:2001:630:212:248:c57:ad59:d050:960f? ([2001:630:212:248:c57:ad59:d050:960f]) by mx.google.com with ESMTPSA id ex2sm67945717wjd.30.2014.08.21.09.43.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 09:43:28 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> Date: Thu, 21 Aug 2014 17:43:27 +0100 Message-Id: <4975003E-8088-49DB-A476-B8444EF6241B@gazagnaire.org> References: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) Cc: Louis Gesbert , "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 >> done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs: >> >> https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp > > This is really useful! The lack of extensibility in the env var bugs me quite a lot, since it's not possible to locally override the OCAMLPARAM with other fields (such as -bin-annot). > > Do you think that an OPAM feature request to support a += field in env is worthwhile at this late stage? I'm thinking that this would be useful for environment variables that support colon-separated delimiters (which I believe OCAMLPARAM does, but I can't find any documentation for it in the manual). As pointed out by Louis this is indeed possible. The issue is that the syntax of OCAMLPARAM is quite weird which makes it very hard to extend (ie. you can only extend on the right or the left if the variable is already defined, otherwise you have to put a '_' char somewhere). 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 Aug 21 16:43:36 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 16:43: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 1XKVSV-0001uU-TZ; Thu, 21 Aug 2014 16:43:31 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKVSV-0001uP-96 for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 16:43:31 +0000 Received: from [85.158.139.211:45420] by server-7.bemta-5.messagelabs.com id FB/EF-30869-2B126F35; Thu, 21 Aug 2014 16:43:30 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-3.tower-206.messagelabs.com!1408639409!3784484!1 X-Originating-IP: [74.125.82.176] 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 12066 invoked from network); 21 Aug 2014 16:43:30 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-3.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 21 Aug 2014 16:43:30 -0000 Received: by mail-we0-f176.google.com with SMTP id q58so9509996wes.7 for ; Thu, 21 Aug 2014 09:43:29 -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=VyJvNxiuNiN8GX+LKTUsgIrub31pEXkl9fPaewEmQ00=; b=vIY3ZcvdzZgRzIl4zAzkdB3sSqqfvqOiwBqb5JSnBFBqTpl+3NrgzlGHA2nnQUivZ0 K2Cp/WtvvOCDMKBge0ycyWAnVOTGKzWtBU7blEUHkZ81VNV2OZmJR2DjvULsMGSOM8tD AdiMolpvRP5SI4aru59Yfo4YZFjepIlPY1QtLG8v2fdKkw+H/NlO5zimOP6c1rgFxziU KEmyEPObFq82Okt24TDqCpfd5/M9awSV4iDwu5jjVwgPO9wl3H6jv4QVEnwvAry4N8as gVNDx2wsg5vU1eg/C+4lZguPXfIxwdGc5PnMvzC1VGJ96UN1Nb67u8rTD5bKK0KBoMly iy1w== X-Received: by 10.194.23.8 with SMTP id i8mr34270103wjf.104.1408639409732; Thu, 21 Aug 2014 09:43:29 -0700 (PDT) Received: from ?IPv6:2001:630:212:248:c57:ad59:d050:960f? ([2001:630:212:248:c57:ad59:d050:960f]) by mx.google.com with ESMTPSA id ex2sm67945717wjd.30.2014.08.21.09.43.28 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 09:43:28 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) From: Thomas Gazagnaire In-Reply-To: <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> Date: Thu, 21 Aug 2014 17:43:27 +0100 Message-Id: <4975003E-8088-49DB-A476-B8444EF6241B@gazagnaire.org> References: <1F26E3A7-A25C-451E-9C8C-35E4EE5ED45B@gazagnaire.org> <2ACEFB02-C203-40E7-93A6-C4394AF24EB5@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1878.6) Cc: Louis Gesbert , "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 >> done, I've set OCAMLPARAM to set -g and -p to all ocamlc/ocamlopt invocation in the 4.01.0+profile switch. Feel free to modify the compiler description to fill you needs: >> >> https://github.com/ocaml/opam-repository/blob/master/compilers/4.01.0/4.01.0%2Bprofile/4.01.0%2Bprofile.comp > > This is really useful! The lack of extensibility in the env var bugs me quite a lot, since it's not possible to locally override the OCAMLPARAM with other fields (such as -bin-annot). > > Do you think that an OPAM feature request to support a += field in env is worthwhile at this late stage? I'm thinking that this would be useful for environment variables that support colon-separated delimiters (which I believe OCAMLPARAM does, but I can't find any documentation for it in the manual). As pointed out by Louis this is indeed possible. The issue is that the syntax of OCAMLPARAM is quite weird which makes it very hard to extend (ie. you can only extend on the right or the left if the variable is already defined, otherwise you have to put a '_' char somewhere). 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 Aug 21 17:31:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 17:31: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 1XKWCZ-0002pL-1F; Thu, 21 Aug 2014 17:31:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKWCU-0002pG-0f for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 17:31:03 +0000 Received: from [85.158.143.35:48489] by server-1.bemta-4.messagelabs.com id 3A/24-05872-5DC26F35; Thu, 21 Aug 2014 17:31:01 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1408642260!12408516!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: ,received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27226 invoked from network); 21 Aug 2014 17:31:00 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-7.tower-21.messagelabs.com with SMTP; 21 Aug 2014 17:31:00 -0000 X-IronPort-AV: E=Sophos;i="5.04,909,1406592000"; d="scan'208";a="24158555" From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] Profiling Mirage on Xen Thread-Index: AQHPtVf2c0doI3AcYU6dkyFwCIGErJvLPXMAgA+XQACAAGpogA== Date: Thu, 21 Aug 2014 17:30:58 +0000 Message-ID: <974E75E8-0977-41DE-9054-C5E556855D82@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] 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 21 Aug 2014, at 12:10, Thomas Leonard wrote: > On 11 August 2014 14:04, David Scott wrote: >> = >> On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard wrot= e: >>> = >>> Has anyone made any tools for profiling on Xen? >> = >> = >> The closest thing I can think of is xentrace/xenalyse: >> = >> http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenal= yze/ >> = >> This will tell you what Xen can see: eg how the vCPUs map to pCPUs and w= hen >> they block on events etc. > = > Thanks. For now, I've pinned dom0 to CPU 0 and my unikernel to CPU 1. > = >>> I want to see why my network service on Xen/ARM only gets about 5 MB/s >>> (while a Linux guest gets about 45 MB/s). >>> = >>> I tried compiling with profiling on ("true: profile" in the _tags) and >>> wrote a __gnu_mcount_nc function to dump all the results to a buffer >>> [1], plus a script to turn the addresses back into symbols and guess >>> the nesting (a bit unreliable, as it doesn't tell you when the >>> function finishes). >>> = >>> Here's an example CSV of the output (the unikernel waits for a TCP >>> connection and then streams data to it as fast as it can): >>> = >>> http://test.roscidus.com/static/sample-output.csv.bz2 >>> = >>> I haven't checked it carefully to see if it's correct - this is just >>> an example of the kind of output. It shows the call graph and the >>> (cumulative) time spent in each function. Since it doesn't know the >>> end times, it assumes a function runs until one of its parents calls >>> something else. >> = >> = >> 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! The graphs are interesting! IIRC the grant unmap operation is very expensive since it involves a TLB sh= ootdown. This adds a large amount (relatively, compared to modern flash-bas= ed disks) to the request/response latency. I think this is why the performa= nce is so terrible with one request at a time. I suspect that the batching = you=92re seeing with two requests is an artefact of the backend, which is p= robably trying to unmap both grant references at once for efficiency. When = I wrote a user-space block backend batching the unmaps made a massive diffe= rence. There is a block protocol extension called =93persistent grants=94 that we = haven=92t implemented (yet). This does the obvious thing and pre-shares a s= et of pages. We might suffer a bit because of extra copies (i.e. we might h= ave to copy into the pre-shared pages) but we would save the unmap overhead= , so it might be worth it. > 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. Certainly a good start! Cheers, Dave > = > = > -- = > 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 _______________________________________________ MirageOS-devel 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 Aug 21 17:31:09 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 21 Aug 2014 17:31: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 1XKWCZ-0002pL-1F; Thu, 21 Aug 2014 17:31:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKWCU-0002pG-0f for mirageos-devel@lists.xenproject.org; Thu, 21 Aug 2014 17:31:03 +0000 Received: from [85.158.143.35:48489] by server-1.bemta-4.messagelabs.com id 3A/24-05872-5DC26F35; Thu, 21 Aug 2014 17:31:01 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1408642260!12408516!1 X-Originating-IP: [185.25.65.24] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: ,received_headers: No Received headers X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27226 invoked from network); 21 Aug 2014 17:31:00 -0000 Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24) by server-7.tower-21.messagelabs.com with SMTP; 21 Aug 2014 17:31:00 -0000 X-IronPort-AV: E=Sophos;i="5.04,909,1406592000"; d="scan'208";a="24158555" From: Dave Scott To: Thomas Leonard Thread-Topic: [MirageOS-devel] Profiling Mirage on Xen Thread-Index: AQHPtVf2c0doI3AcYU6dkyFwCIGErJvLPXMAgA+XQACAAGpogA== Date: Thu, 21 Aug 2014 17:30:58 +0000 Message-ID: <974E75E8-0977-41DE-9054-C5E556855D82@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] 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="windows-1252" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, On 21 Aug 2014, at 12:10, Thomas Leonard wrote: > On 11 August 2014 14:04, David Scott wrote: >> = >> On Mon, Aug 11, 2014 at 12:32 PM, Thomas Leonard wrot= e: >>> = >>> Has anyone made any tools for profiling on Xen? >> = >> = >> The closest thing I can think of is xentrace/xenalyse: >> = >> http://blog.xen.org/index.php/2012/09/27/tracing-with-xentrace-and-xenal= yze/ >> = >> This will tell you what Xen can see: eg how the vCPUs map to pCPUs and w= hen >> they block on events etc. > = > Thanks. For now, I've pinned dom0 to CPU 0 and my unikernel to CPU 1. > = >>> I want to see why my network service on Xen/ARM only gets about 5 MB/s >>> (while a Linux guest gets about 45 MB/s). >>> = >>> I tried compiling with profiling on ("true: profile" in the _tags) and >>> wrote a __gnu_mcount_nc function to dump all the results to a buffer >>> [1], plus a script to turn the addresses back into symbols and guess >>> the nesting (a bit unreliable, as it doesn't tell you when the >>> function finishes). >>> = >>> Here's an example CSV of the output (the unikernel waits for a TCP >>> connection and then streams data to it as fast as it can): >>> = >>> http://test.roscidus.com/static/sample-output.csv.bz2 >>> = >>> I haven't checked it carefully to see if it's correct - this is just >>> an example of the kind of output. It shows the call graph and the >>> (cumulative) time spent in each function. Since it doesn't know the >>> end times, it assumes a function runs until one of its parents calls >>> something else. >> = >> = >> 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! The graphs are interesting! IIRC the grant unmap operation is very expensive since it involves a TLB sh= ootdown. This adds a large amount (relatively, compared to modern flash-bas= ed disks) to the request/response latency. I think this is why the performa= nce is so terrible with one request at a time. I suspect that the batching = you=92re seeing with two requests is an artefact of the backend, which is p= robably trying to unmap both grant references at once for efficiency. When = I wrote a user-space block backend batching the unmaps made a massive diffe= rence. There is a block protocol extension called =93persistent grants=94 that we = haven=92t implemented (yet). This does the obvious thing and pre-shares a s= et of pages. We might suffer a bit because of extra copies (i.e. we might h= ave to copy into the pre-shared pages) but we would save the unmap overhead= , so it might be worth it. > 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. Certainly a good start! Cheers, Dave > = > = > -- = > 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 _______________________________________________ MirageOS-devel 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 Aug 22 22:43:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 22 Aug 2014 22:43: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 1XKxYF-0003Fw-TV; Fri, 22 Aug 2014 22:43:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKxYD-0003Fr-Tn for mirageos-devel@lists.xenproject.org; Fri, 22 Aug 2014 22:43:18 +0000 Received: from [85.158.143.35:10821] by server-2.bemta-4.messagelabs.com id 9C/04-04525-587C7F35; Fri, 22 Aug 2014 22:43:17 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1408747394!5423941!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20710 invoked from network); 22 Aug 2014 22:43:15 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Aug 2014 22:43:15 -0000 Received: by mail-pa0-f45.google.com with SMTP id eu11so17322954pac.32 for ; Fri, 22 Aug 2014 15:43:14 -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=1QL7FjpMxfm7UO+BpPS1y2x5atumltPnxfFRrEpzWlc=; b=WcjDUERs9tzOhEvuUteeMvohULFm0+HjfpPMhI05fsFeplRYRPgLrSaioVhIMhnkxn acIrRQTAYksjo6kn5+HDH3gh9xzemexUtJk7aiofMXKke2LDKYGb9fP/gMoUDY8nHoT/ /0Tpi3qK9ilX24YoFFopNBg0kjj85anT+bUaMuRvQrfF24beks0AeAFsIUkGWon4FEdS scI6z7miCGHztJGZzAeMlhhgqRR/gXlqgdI8s7u3q822y3nLqtvskrhwPRA9tMWJtkvi f26aydBzl3F1ycs1hkEUWAvoBVtv+qXzaUdKOTalqPnbibaR+P2oa4f7Fwn26VSTICFA ebeQ== MIME-Version: 1.0 X-Received: by 10.66.139.200 with SMTP id ra8mr9865904pab.69.1408747393983; Fri, 22 Aug 2014 15:43:13 -0700 (PDT) Received: by 10.70.65.101 with HTTP; Fri, 22 Aug 2014 15:43:13 -0700 (PDT) Date: Fri, 22 Aug 2014 23:43:13 +0100 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [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="===============4736291353665358776==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4736291353665358776== Content-Type: multipart/alternative; boundary=047d7b5dbcd0ff2bbd05013f8fac --047d7b5dbcd0ff2bbd05013f8fac Content-Type: text/plain; charset=UTF-8 In the last weekly call I agreed to work on conduit + vchan. https://github.com/mirage/mirage-www/pull/219/files#diff-ad18f4983a07ffe4c757b33c537226a1R70 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 implement Lwt_io channels on top of the FLOW exposed by vchan. I've got a prototype 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 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 --047d7b5dbcd0ff2bbd05013f8fac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In the last weekly call I agreed to work on conduit + vcha= n.


Looking at the Lwt_unix conduit API
https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lw= t_unix_conduit.ml

It seems to be using Lwt_io input/output channels. So m= y 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 t= he conduit code is quite new and under heavy development I thought I'd = better ask :-)

A side-benefit is that Lwt_unix app= s 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 base= d, so I can expose the existing vchan implementation there.

<= /div>
Cheers,
--
Dave Scott
--047d7b5dbcd0ff2bbd05013f8fac-- --===============4736291353665358776== 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 --===============4736291353665358776==-- From mirageos-devel-bounces@lists.xenproject.org Fri Aug 22 22:43:26 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 22 Aug 2014 22:43: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 1XKxYF-0003Fw-TV; Fri, 22 Aug 2014 22:43:19 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XKxYD-0003Fr-Tn for mirageos-devel@lists.xenproject.org; Fri, 22 Aug 2014 22:43:18 +0000 Received: from [85.158.143.35:10821] by server-2.bemta-4.messagelabs.com id 9C/04-04525-587C7F35; Fri, 22 Aug 2014 22:43:17 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1408747394!5423941!1 X-Originating-IP: [209.85.220.45] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.11.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20710 invoked from network); 22 Aug 2014 22:43:15 -0000 Received: from mail-pa0-f45.google.com (HELO mail-pa0-f45.google.com) (209.85.220.45) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 22 Aug 2014 22:43:15 -0000 Received: by mail-pa0-f45.google.com with SMTP id eu11so17322954pac.32 for ; Fri, 22 Aug 2014 15:43:14 -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=1QL7FjpMxfm7UO+BpPS1y2x5atumltPnxfFRrEpzWlc=; b=WcjDUERs9tzOhEvuUteeMvohULFm0+HjfpPMhI05fsFeplRYRPgLrSaioVhIMhnkxn acIrRQTAYksjo6kn5+HDH3gh9xzemexUtJk7aiofMXKke2LDKYGb9fP/gMoUDY8nHoT/ /0Tpi3qK9ilX24YoFFopNBg0kjj85anT+bUaMuRvQrfF24beks0AeAFsIUkGWon4FEdS scI6z7miCGHztJGZzAeMlhhgqRR/gXlqgdI8s7u3q822y3nLqtvskrhwPRA9tMWJtkvi f26aydBzl3F1ycs1hkEUWAvoBVtv+qXzaUdKOTalqPnbibaR+P2oa4f7Fwn26VSTICFA ebeQ== MIME-Version: 1.0 X-Received: by 10.66.139.200 with SMTP id ra8mr9865904pab.69.1408747393983; Fri, 22 Aug 2014 15:43:13 -0700 (PDT) Received: by 10.70.65.101 with HTTP; Fri, 22 Aug 2014 15:43:13 -0700 (PDT) Date: Fri, 22 Aug 2014 23:43:13 +0100 Message-ID: From: David Scott To: "mirageos-devel@lists.xenproject.org" Subject: [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="===============4736291353665358776==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============4736291353665358776== Content-Type: multipart/alternative; boundary=047d7b5dbcd0ff2bbd05013f8fac --047d7b5dbcd0ff2bbd05013f8fac Content-Type: text/plain; charset=UTF-8 In the last weekly call I agreed to work on conduit + vchan. https://github.com/mirage/mirage-www/pull/219/files#diff-ad18f4983a07ffe4c757b33c537226a1R70 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 implement Lwt_io channels on top of the FLOW exposed by vchan. I've got a prototype 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 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 --047d7b5dbcd0ff2bbd05013f8fac Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In the last weekly call I agreed to work on conduit + vcha= n.


Looking at the Lwt_unix conduit API
https://github.com/avsm/ocaml-conduit/blob/v0.6/lib/lw= t_unix_conduit.ml

It seems to be using Lwt_io input/output channels. So m= y 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 t= he conduit code is quite new and under heavy development I thought I'd = better ask :-)

A side-benefit is that Lwt_unix app= s 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 base= d, so I can expose the existing vchan implementation there.

<= /div>
Cheers,
--
Dave Scott
--047d7b5dbcd0ff2bbd05013f8fac-- --===============4736291353665358776== 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 --===============4736291353665358776==-- From mirageos-devel-bounces@lists.xenproject.org Tue Aug 26 14:46:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 26 Aug 2014 14:46: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 1XMI0l-0006DV-Hg; Tue, 26 Aug 2014 14:46:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XMI0k-0006D5-Bg for mirageos-devel@lists.xenproject.org; Tue, 26 Aug 2014 14:46:14 +0000 Received: from [85.158.139.211:13588] by server-1.bemta-5.messagelabs.com id E6/86-17892-5BD9CF35; Tue, 26 Aug 2014 14:46:13 +0000 X-Env-Sender: russell.pavlicek@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1409064371!12235293!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 6550 invoked from network); 26 Aug 2014 14:46:12 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Aug 2014 14:46:12 -0000 X-IronPort-AV: E=Sophos;i="5.04,405,1406592000"; d="scan'208";a="166009309" From: Russell Pavlicek To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "xs-devel@lists.xenserver.org" , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Thread-Topic: Xen Project Document Day is tomorrow, Wednesday August 27 Thread-Index: AQHPwTfE5wEy3J9+UUqFFnGFA3VZdA== Date: Tue, 26 Aug 2014 14:46:07 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA276AFD7@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 Document Day is tomorrow, Wednesday August 27 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 tomorrow, August 27, is Xen Project Document Day. Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki. While we know that many people are out taking a well-deserved break this time of year, those of us who remain can still get busy improving our Wiki. 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 in the next week, 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 Aug 26 14:46:21 2014 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 26 Aug 2014 14:46: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 1XMI0l-0006DV-Hg; Tue, 26 Aug 2014 14:46:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1XMI0k-0006D5-Bg for mirageos-devel@lists.xenproject.org; Tue, 26 Aug 2014 14:46:14 +0000 Received: from [85.158.139.211:13588] by server-1.bemta-5.messagelabs.com id E6/86-17892-5BD9CF35; Tue, 26 Aug 2014 14:46:13 +0000 X-Env-Sender: russell.pavlicek@citrix.com X-Msg-Ref: server-6.tower-206.messagelabs.com!1409064371!12235293!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 6550 invoked from network); 26 Aug 2014 14:46:12 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-6.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 26 Aug 2014 14:46:12 -0000 X-IronPort-AV: E=Sophos;i="5.04,405,1406592000"; d="scan'208";a="166009309" From: Russell Pavlicek To: "xen-users@lists.xen.org" , "xen-devel@lists.xen.org" , "xs-devel@lists.xenserver.org" , "mirageos-devel@lists.xenproject.org" , "xen-api@lists.xen.org" Thread-Topic: Xen Project Document Day is tomorrow, Wednesday August 27 Thread-Index: AQHPwTfE5wEy3J9+UUqFFnGFA3VZdA== Date: Tue, 26 Aug 2014 14:46:07 +0000 Message-ID: <55E78A57290FB64FA0D3CF672F9F3DA276AFD7@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 Document Day is tomorrow, Wednesday August 27 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: 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 tomorrow, August 27, is Xen Project Document Day. Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki. While we know that many people are out taking a well-deserved break this time of year, those of us who remain can still get busy improving our Wiki. 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 in the next week, 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