copy` has quit [Quit: Connection closed for inactivity]
philtor has quit [Ping timeout: 240 seconds]
_whitelogger has joined #mirage
insitu has joined #mirage
insitu has quit [Client Quit]
insitu has joined #mirage
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<reynir>
Nice!
insitu has joined #mirage
<hannes>
haesbaert: nice~
fgimenez has joined #mirage
fgimenez has joined #mirage
fgimenez has quit [Changing host]
<haesbaert>
:D
dmj` has quit []
dmj` has joined #mirage
insitu has quit [Ping timeout: 264 seconds]
insitu has joined #mirage
yomimono has joined #mirage
AltGr has joined #mirage
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
kensan has quit [Quit: leaving]
reet has quit [Read error: Connection reset by peer]
kensan has joined #mirage
yomimono has quit [Ping timeout: 264 seconds]
mort___ has quit [Quit: Leaving.]
yomimono has joined #mirage
mort___ has joined #mirage
abeaumont has joined #mirage
fgimenez has quit [Ping timeout: 240 seconds]
mort___ has quit [Quit: Leaving.]
fgimenez has joined #mirage
carlos has joined #mirage
dstolfa has joined #mirage
<dstolfa>
Hello, I was curious what paravirtualization features you make use of for KVM, and what would be needed in order to support bhyve natively, should one want to not use VirtIO
<hannes>
dstolfa: mato (currently absent here) worked over the last week more on cutting Solo5 into pieces to allow more backends (KVM, Hypervisor.Framework, VMMAPI (the userspace API for the VMM kernel bits in FreeBSD)).
<hannes>
dstolfa: I expect that there'll be patches this month for Solo5 (there's already a PR to support Hypervisor.Framework natively)
<dstolfa>
hannes: Ah okay, Would this be of any help in terms of performance/usability in your design? reviews.freebsd.org/D8100
<hannes>
dstolfa: thanks for the pointer, could you open a GitHub issue at https://github.com/Solo5/solo5 about "native FreeBSD vmm port" and put the link there (otherwise it will likely get lost, and I'm not the one doing low level system design)?
<dstolfa>
hannes: Sure thing, thanks for the feedback
<hannes>
dstolfa: thank you for the pointer. are you by any chance working on bhyve? :)
<dstolfa>
hannes: On-and-off, I'm working with rwatson@ in trying to trace VMs with DTrace, and I'm doing that through bhyve. This is something I needed in the design, but I assumed it'd be useful for mirage too :)
<hannes>
dstolfa: cambridge-based?
<hannes>
(I just returned to Cambridge computer labs from several months in africa)
<dstolfa>
hannes: Sort of, I'm studying in Croatia right now, finished my applications to Cambridge 2 days ago(MPhil already went through the department I think, PhD awaiting)
<dstolfa>
hannes: Ah, I was there 2 weeks ago
<hannes>
dstolfa: nice! :)
mort___ has joined #mirage
mort___ has quit [Ping timeout: 246 seconds]
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
carlos has quit [Ping timeout: 260 seconds]
argent_smith has joined #mirage
insitu has joined #mirage
<argent_smith>
hi ppl. i'm preparing a small MirageOS introduction for my colleagues at work. Question: is there something like a web page listing Mirage success stories/use cases?
<hannes>
argent_smith: parts of the (ISC-licensed) libraries developed under the MirageOS umbrella are nowadays used at docker for mac and docker for windows... but I'm not sure whether they wrote anything detailed about that
<argent_smith>
hannes: in my local speaks i've already mentioned these so my fellows asked me to introduce the whole thing :)
<kensan>
If I may intrude... has nymote been sunset or is it still under development?
<hannes>
kensan: it's vaporware, as described. there has been ongoing work on MirageOS (and porting it to various architectures, such as kvm), on irmin as well (it now has a 1.0 release iirc).
<hannes>
signpost is still vaporware (some prototype, no-longer-working scripts)
<hannes>
dinosaure developed mrmime, a mime encoding and decoding libraries purely in ocaml, which works for 99% of a dataset of 2 million mail (afair, don't quote me on the numbers)
mort___ has joined #mirage
<kensan>
hannes: In the introduction of your BornHack '16 talk about MirageOS you mention "hive". Is that still a blue sky idea or are you actively working on it?
<hannes>
I'm actively working on blue skies.
<kensan>
touché :)
<hannes>
there's no release or source up in the open (yet!?) -- but in the end, MirageOS is a set of libraries, and so will projects on top of MirageOS
<hannes>
atm I should be busy with some more TCP/IP testing, and congestion control.
<hannes>
since nymote.org launched, we at least managed to release a tls library to-be-used with MirageOS. as mentioned, I'm currently working on some TCP/IP things, and will likely afterwards work on higher layers.. but it doesn't make much sense (for me) to build upon this brittle TCP/IP stack that is out there atm
<hannes>
(others are happily using this TCP/IP stack in production, maybe it's me who is a perfectionist here)
<kensan>
hannes: Ah, thats an insightful piece of info, thanks.
<hannes>
kensan: as mentioned, this is my very personal opinion. docker for mac/win ships mirage-tcpip and it seems like they're happy with it.
<kensan>
hannes: I am thinking about building something with MirageOS once the Solo5 Muen port is stable and ready for submission.
* hannes
is on 'modeling TCP throughput: a simple model and its empirical evaluation'..
<kensan>
hannes: Trying to get an idea of the current state of the MirageOS ecosystem that is why I am asking.
<hannes>
kensan: you're lucky. the Mirage3 release is the best/most mature so far! :)
<hannes>
kensan: I run various unikernel (hannes.nqsb.io is a Canopy unikernel, nqsb.io is another unikernel, I also have the authoritative DNS server for nqsb.io as MirageOS unikernel, https://tls.nqsb.io is another unikernel)
<kensan>
hannes: I have been lurking but the 3.0 release and Solo5 work have made me take another, closer look and since I got a basic Muen port done in a weekend it would be a shame to stop...
<hannes>
:)
<kensan>
So far I have not really touched Ocaml, except for the mirage tool adjustements. Writing a unikernel to run on top of Solo5/Muen should be instructive.
agarwal1975 has joined #mirage
<gjaldon__>
hannes: where did you deploy your unikernels?
<hannes>
gjaldon__: private server in a data center
<gjaldon__>
ok :)
<hannes>
but in solo5 there's a google cloud engine script afaics
insitu has joined #mirage
<gjaldon__>
hannes: about Canopy, I still couldn't run it locally on my arch linux I already have compiled it successfully. does it expect a cookie in git jar?
<hannes>
gjaldon__: there shouldn't be a cookie needed, but I remember a similar `read` error in ocaml-git or irmin issue tracker...
<hannes>
gjaldon__: i don't remember to have seen this before, maybe report it to ocaml-git and see whether someone has an idea there (sorry that I don't have a solution)
<gjaldon__>
no prob at all hannes! thanks for your time though
insitu has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]