hannes changed the topic of #mirage to: https://mirage.io - https://github.com/mirage/mirage-www/wiki/Call-Agenda - this channel is logged at http://irclog.whitequark.org/mirage/ - MirageOS 3.5.0 is released - happy hacking!
_whitelogger has joined #mirage
ansiwen has quit [Quit: ZNC 1.7.1 - https://znc.in]
ansiwen has joined #mirage
Haudegen has joined #mirage
mort___ has joined #mirage
derpeter1 is now known as derpeter
Haudegen has quit [Remote host closed the connection]
<mort___> anyone up-to-date with the state of ipv6 support in mirage please?
<mort___> (and, related, in the qubes firewall which I believe is a mirage implementation now?)
<h01ger> the default qubes firewall uses a linux template. you can also use qubes-mirage-firewall instead.
* h01ger doesnt bother with ipv6 yet, maybe next year
<mort___> ack; does it firewall ipv6 as well as ipv4 yet?
<h01ger> i dunno
<mort___> hm, looking at the code i think the answer is probably no. thanks for the pointer to qubes-mirage-firewall :)
<h01ger> :)
<hannes> mort___: AFAIK not at the moment (IPv6), but mindy and steffi are working on mirage-qubes-firewall improvements which may include IPv6 support.
<mort___> awesome :)
<mort___> if i read mirage-tcpip right, there is support in the stack for it though, and it's more than just the type signatures and address formats, right?
<mort___> (seeing as you and djs55 at least have some commits with relevant looking comments ;)
<hannes> uhm, well, I don't think anyone is running MirageOS-IPv6 network stacks (there's certainly a STACKV6 missing, similar to STACKV4). There are some bits and pieces implemented (NDP/..), but unclear how far that goes.
<hannes> now lunch
<mort___> ackack enjoy!
<mort___> (thanks)
Haudegen has joined #mirage
mort___1 has joined #mirage
mort___ has quit [Ping timeout: 252 seconds]
mort___1 has quit [Quit: Leaving.]
Haudegen has quit [Read error: Connection reset by peer]
_whitelogger has joined #mirage
pie___ has joined #mirage
pie_ has quit [Read error: Connection reset by peer]
<ehirdoy1> With kind support from this IRC, I seem to be able to run distributed ML on Unikernel'ized lightweight actor engine (LwAE) with MirageOS HVT. If you are interested, please try below. Any comment would be really\
<ehirdoy1> appreciated. https://github.com/owlbar
<ehirdoy1> Again:P Here's a link, https://github.com/owlbarn/light_actor/pull/8
<pie___> sounds fancy :D
<hannes> ehirdoy1: nice! :)
<ehirdoy1> well,,,title sounds fancy but implementation is still quite primitive;), thanks!
<hannes> ehirdoy1: for me it would help to also have a run / expected output on unix (or a measurement of a baseline) ;)
<ehirdoy1> Both could run from the same code, which is one of the advantage of MirageOS, right? :)
<ehirdoy1> data && resoruce comparison may be next step....I may need some convenient infra for that....
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
dsheets has joined #mirage
dsheets has quit [Quit: Leaving]
dsheets has joined #mirage
dsheets has quit [Client Quit]
pie___ has quit [Ping timeout: 258 seconds]
pie_ has joined #mirage