Re: [MirageOS-devel] Cannot deploy a Unikernel to a XenServer pool running XS 6.2

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

On 22 Oct 2014, at 00:13, Sergio Visinoni <piffio@xxxxxxxxxx> wrote:

When you have installed all the packages from mirage-dev in order to build MirageOS 2.0, it's not possibe to build the xe-unikernel-upload module, due to some incompatibilities between xen-api-client and the latest Cohttp. Since the xen-api-client [1] doesn't seem to allow for issue reporting in GitHub, I'm reporting here. The workaround I found has bin to build both xe and xe-unikernel-upload on my laptop with the mirage 1.2 modules installed, saved the binaries in a safe location, and moved forward with mirage-dev.

    # File "lib/xen_api.ml", line 40, characters 9-20:

    # Error: Unbound module Cohttp.IO

    # Command exited with code 2.

Should I report this bug on a different list? If so, which one?

If you could report this on https://github.com/mirage/mirage/issues it should be fine.  The patch should just be changing Cohttp.IO to Cohttp.S.IO in the short term.

In the medium term, it would be good to move the POSIX Cohttp backend out of the XenAPI code and into Cohttp, where it can be maintained along with the rest of the library...

-anil

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