One way to keep this working is to do a live deployment that uses the Unix/tuntap instead of the Xen backend. In general, I think it's time to start load balancing the openmirage.org <http://openmirage.org/> site with all of our supported backends (x86/ARM, Unix/Xen) so that we get bug reports as easy as possible. Let's put it on the next call agenda, but we need to:
- modify the Travis deployment scripts to build all the variants and not just Xen/x86_64 - alter mirage-www to include information on which backend it is using and display it in the HTML - deploy a couple of DNS unikernels that do RR balancing across each of the different backends. -anil > On 2 May 2015, at 18:17, Thomas Gazagnaire <[email protected]> wrote: > >> Should I submit a pull request for the modifications I made to >> mirage-net-unix? > > yes pull requests are always very welcome! > > Thanks, > Thomas > >> >> On Fri, May 1, 2015 at 8:40 AM, Robert Ream <[email protected] >> <mailto:[email protected]>> wrote: >> Hmm, ok I'll try a VM with a different OS to see if I can get it to work, >> maybe Ubuntu 15 is a bit too cutting edge... :-/ >> >> >> On Fri, May 1, 2015 at 6:55 AM, Luke Dunstan <[email protected] >> <mailto:[email protected]>> wrote: >> Actually, I just tried it and I have the same problem with tap0 not >> being persistent on Ubuntu 14.04, and this is because >> https://github.com/mirage/ocaml-tuntap >> <https://github.com/mirage/ocaml-tuntap> hasn't been released yet since >> PR #9. >> >> However, I don't have any "terminating" problem with tap0, so I think >> that problem is most likely unrelated to the persistence. >> >> Luke >> >> On 1 May 2015 at 16:18, Anil Madhavapeddy <[email protected] >> <mailto:[email protected]>> wrote: >> > This sounds like a problem with persistent vs non-persistent tap >> > interfaces. >> > This functionality is unfortunately very non-portable (MacOS X, FreeBSD and >> > Linux) all have different behaviour. The functionality did change between >> > version 2.2.0 and 2.1.0 to support persistent interfaces: >> > https://github.com/mirage/mirage-net-unix/releases >> > <https://github.com/mirage/mirage-net-unix/releases> >> > >> > So I wonder if something needs to be done to keep it around on your >> > particular setup. >> > >> > (This isn't helped by me now using mirage-net-macosx for most of my >> > day-to-day dev, which uses a completely different codepath as tuntap no >> > longer works usefully on OSX as of Yosemite). >> > >> > -anil >> > >> > On 30 Apr 2015, at 23:49, Robert Ream <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > An update: I just cloned the mirage-net-unix repo and ran the tests. This >> > is >> > what I got: >> > >> > sudo ./test.native >> > plugging into tap0 with mac c2:9d:56:19:d7:2c.. >> > Netif: connect tap0 >> > connected >> > Netif: error, terminating listen loop >> > . >> > Ran: 1 tests in: 0.00 seconds. >> > OK >> > >> > And the tun0 interface disappeared as well. >> > >> > >> > >> > On Thu, Apr 30, 2015 at 2:55 PM, Robert Ream <[email protected] >> > <mailto:[email protected]>> wrote: >> >> >> >> Ok, I'm still stumped. >> >> >> >> Two things happen with pretty much all of the network examples when I >> >> build and execute them for unix: 1) they promptly exit with a "Netif: >> >> error, >> >> terminating listen loop" and 2) tun0 disappears and must be recreated >> >> every >> >> time. >> >> >> >> 1) I tracked down the lines of code in mirage-net-unix that cause this >> >> error message: >> >> >> >> let page = Io_page.get 1 in read t page >>= function | `Error _ -> printf >> >> "Netif: error, terminating listen loop\n%!"; return () >> >> >> >> So it is running into an error when reading a page from the network. >> >> It would be nice to pretty print the _ of `Error _ instead of drop it on >> >> the floor. >> >> >> >> 2) I couldn't find anywhere in the code that remotely appeared to be >> >> messing with or deleting the tun0 interface. But I wonder if the error I'm >> >> seeing is due to the tun0 disappearing? >> >> >> >> -Robert >> > >> > >> > _______________________________________________ >> > MirageOS-devel mailing list >> > [email protected] >> > <mailto:[email protected]> >> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > <http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel> >> > >> > >> > >> > _______________________________________________ >> > MirageOS-devel mailing list >> > [email protected] >> > <mailto:[email protected]> >> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > <http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel> >> > >> >> >> _______________________________________________ >> MirageOS-devel mailing list >> [email protected] >> <mailto:[email protected]> >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
