Re: [MirageOS-devel] Issues with CLOCK on xen

[Len Maxwell <len@xxxxxxxx>]

Hi Toby,

I just built a similar example [1] and it is running OK on EC2 [2]. You might try building and deploying my code from your environment and see if you get any different result.

Note that I am using the mirage-dev OPAM remote, and explicitly calling for a V1.CLOCK "device" (per #289 [3]).

[1]Âhttps://github.com/lnmx/mirage-sandbox/tree/master/http-clock

[2] up temporarily: http://54.145.130.16/Â

[3]Âhttps://github.com/mirage/mirage/issues/289

--

Len

On Tue, Dec 2, 2014 at 10:06 AM, Toby Moore <toby.moore.0@xxxxxxxxx> wrote:

I've just added a github issue (https://github.com/mirage/mirage/issues/333).

I'm on a mac, doing my dev in a linux vm which won't support xen inside Parallels. If I get a chance this weekend I'll try out the OS X hosting that I've seen going past on here.

I have just tried adding `Xen -> ["mirage-clock-xen"] for the ocamlfind stuff on AWS but it doesn't seem to make a difference, compiles fine but again fails at runtime.

Looking more closely at the error and my code, possibly it's the not the time call or a missing dependency but the conversion? My code is doing `Clock.gmtime (Clock.time ())`. I've found this reference here: https://github.com/mirage/mirage-clock/blob/master/xen/clock.ml#L30 but I'm not sure what that gets linked to.

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