Re: [MirageOS-devel] Mirage on Xen/ARM status

[Thomas Leonard <talex5@xxxxxxxxx>]

I've been going through mirage-skeleton trying all the examples on ARM
(Cubietruck running Xen). Here are the results:

console: works (I also patched it to try reading from the console, and
that works too, after a minor patch to mirage-console; now merged)

network: works
block: works

dns: fails to build
Error: No implementations provided for the following modules:
         Lwt_unix referenced from
/root/.opam/4.01.0/lib/dns/lwt-core.cmxa(Dns_resolver)

ethifv4: seems to work (except for TCP: it shows "TCP retransmission
on timer seq = 452901213" instead of connecting)

io_page: works
kv_ro: works (prints YES! a lot, anyway)
kv_ro_crunch: works (as kv_ro)
ping: works (note: reports UDP traffic as "TCP" due to a bug)
stackv4: works (HTTP on 80, TCP on 8080 and UDP on 53)

static_website: works, after adding re.str. Otherwise you get:
Error: No implementations provided for the following modules:
         Re_str referenced from dispatch.cmx


So, it's looking pretty good :-)


A few random notes:

- Lack of progress reports from mirage is a problem on x86, but it's
worse on ARM because it's so much slower.

- opam got very confused at one point, somehow uninstalled mirage and
then wouldn't bring it back (no error shown). Here's a sample:

root@softbuild:~# mirage
-bash: mirage: command not found
root@softbuild:~# opam reinstall mirage
[ERROR] mirage is not installed.

'opam reinstall mirage' failed.
root@softbuild:~# opam install mirage
root@softbuild:~# mirage
-bash: mirage: command not found
root@softbuild:~# opam reinstall mirage
[ERROR] mirage is not installed.

Installing "aspcud" sorted it all out (and makes it faster!).

- I was using the system ocaml, which lacked ocamlopt.opt, slowing
down the builds. Using "opam sw 4.01.0" sorted that out.

- mirage-console's install rule has some problems at the moment. Use
"ocamlfind remove" to remove the various bits manually and try again
if it happens.

https://github.com/mirage/mirage-console/issues/17

- direct_stackv4_with_default_ipv4 is a bit annoying. It contains an
IP address hard-coded into mirage, but it makes it difficult to see
how to change it for your own network. It might be better to use
direct_stackv4_with_static_ipv4 for the examples.


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