<hannes>
sorry for confusion, and great that it becomes more clear :)
<dmj`>
nice!
<reynir>
thanks, my picture of the diagrams were super blurry!
<hannes>
[pic credit goes to mato, I only took the photograph]
<dmj`>
it’s very nice
<dmj`>
so interesting there is a mirage-posix-xen w/ mini-os, but doesn’t seem like there is an equivalent for solo5
<haesbaert>
hannes: I had no idea that came from topkg
<hannes>
dmj`: the mirage-posix-xen does not contain posix, only stubbed out symbols to get the ocaml runtime to compile (getenv, lseek, stdout, ...)
<hannes>
haesbaert: np.. imho it is a very nice feature of topkg
<haesbaert>
yeah, except that it is a bzip
<haesbaert>
but getting the stuff from changes and replacing the watermarks is indeed awesome
<dmj`>
hannes: ahh sure, so it’s a runtime failure. HaLVM is similar `getEnvironment` is always an empty list.
<dmj`>
hannes: so is mirage-3.0 encompassing of both mini-os and solo5? Or is mirage-3.0 more just about solo5
<hannes>
dmj`: it's not a runtime failure, it just returns null ;)
<dmj`>
hannes: haha :) sure sure
<hannes>
dmj`: MirageOS 3 has various backends: -t unix --> unix elf binary; -t xen --> uses mirage-xen and mini-os; -t ukvm --> uses solo5+kvm; -t virtio --> uses solo5+virtio (e.g. for FreeBSD bhyve, or qemu)
<haesbaert>
btw, do I need any cpu support for solo5+ukvm ?
<hannes>
(and there are more, -t qubes which includes boilerplate for running on qubes somehow, -t macosx to select macosx specific packages (I think network device))
<hannes>
haesbaert: yes. vt-d/x?, ept
<haesbaert>
aww :(
<haesbaert>
think my old turion doesn't have it
<hannes>
haesbaert: get a new one ;)
<dmj`>
haesbert: are you running xen? If you’re inside dom0 w/o nested virtualization enabled, it might incorrectly report you don’t have it
<haesbaert>
hannes: NEVAH ! costed me 90eur the whole machine
<haesbaert>
dmj`: the host says I don't have it at least
<haesbaert>
I'll keep running xen on it then
<dmj`>
haesbert: have an nvidia gtx on this linux box, can’t get the nvidia drivers to work for it, so am trying to install windows 10 on qemu w/ kvm to play overwatch. Since xen was installed, my machine incorrectly said I was missing the extensions.
<dmj`>
hannes: so is rumprun any part of mirage? Or is rumprun old tech?
<haesbaert>
dmj`: that's a lot of willpower for playing overwatch :D
mort___ has left #mirage [#mirage]
<dmj`>
haesbaert: I know right :) it’s like that garfield comic where he nails the TV to the ceiling and John says, “I’ve never seen someone work so hard at being so lazy"
<dmj`>
hannes: Ah… that’s interesting
<dmj`>
hannes: so, if I can ask this, is the new docker basically a wrapper around the mirage-solo5-kvm/qemu backend
<haesbaert>
hannes: do you know the tar incantations topkg uses ? I'm trying to create the tarball and make the digest match
<haesbaert>
dmj`: I was a decent mccree :D
<dmj`>
haesbaert: “like sittin’ ducks"
<dmj`>
;)
<haesbaert>
heheh pretty good game
<haesbaert>
hannes: never mind the tarball I can't really add it to github since I didn't do the releases properly, mindy did it, so I can add to 0.4 at least
<haesbaert>
oh turns out I can
<hannes>
haesbaert: look in the (topkg) source, luke ;)
<hannes>
dmj`: no clue. ask docker people about docker stuff. I'm employed by University of Cambridge
<hannes>
dmj`: I think they don't use the mirage tool itself, but only a fine selection of OCaml libraries which were developed under the mirage umbrella
<haesbaert>
hannes: I did, took me more than 5min and I decided to ask :P
<yomimono>
hannes: because I didn't see it until I'd already cut stuff, sorry -- we can do a 3.0.2
<yomimono>
or I can rescind the PR to opam-repository for 3.0.1
<yomimono>
I'm keen to get something in because right now there's not a `mirage` that is compatible with the released tcpip (3.1.0) - I'm about to walk into the lab, if you have time to merge + release a mirage 3.0.2 please feel free to do that, otherwise I'll do it this afternoon
yomimono has quit [Ping timeout: 260 seconds]
tomboy64 has quit [*.net *.split]
dudelson has joined #mirage
tomboy64 has joined #mirage
yomimono has joined #mirage
mort___ has joined #mirage
dudelson has quit [Ping timeout: 260 seconds]
mort___ has quit [Ping timeout: 260 seconds]
dudelson has joined #mirage
fgimenez has quit [Ping timeout: 258 seconds]
fgimenez has joined #mirage
dudelson has quit [Ping timeout: 240 seconds]
<copumpkin>
I'm poking at hyperkit some more and am wondering why mirage_block_ocaml.ml specifically is in ocaml vs. mirage_block_c
<copumpkin>
(don't get me wrong, I want more of it to be in ocaml, not less, but it's still odd to see a single .ml file in a sea of .c)
<yomimono>
we had a few asks from hannes during the hack retreat that are lingering: a request that people write up their experiences, and a request for folks to exchange keys for for conex
<yomimono>
I haven't done either of those things D: but I hope to do both of them soon.
<amirmc>
+1 to write ups. It would be great to get something up on the website :)
thomasga has quit [Ping timeout: 246 seconds]
<yomimono>
sounds like not much more to say about that?
<djwillia>
hannes sent me a mail saying the next one is in the works?
<djwillia>
for the end of November?
<yomimono>
yes! the hostel in marrakesh is reserved for early December/end of November
<yomimono>
I don't recall the exact dates, but I expect hannes will send mail once it's sufficiently confirmed
<yomimono>
other questions/comments?
<yomimono>
hearing none! I stuck an agenda item up for some releases I did early this week: mirage 3.0.1 (and 3.0.2 with a better color fix), also tcpip 3.1.0
<yomimono>
all contain a lot of work from the hack retreat and I was delighted to note new names in the changelogs :D
<talex5>
Great! These will simplify the installation of mirage-firewall nicely :-)
<yomimono>
djs55: tcpip 3.1.0 contains your mtu changes, notably
<yomimono>
we should release mirage-nat and mirage-firewall soon as well, which got a lot of hack retreat work
<yomimono>
if anyone else has major work in the pipeline which they expect to see released soon, please shout :)
dudelson has joined #mirage
thomasga has joined #mirage
<yomimono>
...moving on then ;)
<yomimono>
we've gotten a lot of GSoC interest on the mailing list lately
<yomimono>
particularly if you have smaller wishlist stuff
<yomimono>
or if you have grand plans for which you require assistance!
<amirmc>
Also if you can no longer act as mentor right now. We should try to keep that list fresh for folks who are browsing for projects :)
<Drup>
I should really freshen up the stuff I wanted to post on functoria
<amirmc>
Drup Yes, please!
<amirmc>
Druo: D'you have anything written up anywhere public? I don't see any functoria items in the current list.
<Drup>
There is an thread on the mailing list
<Drup>
Where I detail things a bit. It seemed like anil wanted to rework things a bit. The process to add projects was not extremly clear, and I got busy with other things
talex5 has quit [Quit: Leaving]
talex5 has joined #mirage
<yomimono>
the canopy maintenance mentioned last meeting is still an issue, as far as I know
<yomimono>
I haven't had time to invest in that bit of infrastructure this week and don't think I will in the next few :(
<Drup>
amirmc: the name of the thread is "Pioneer project propositions"
<amirmc>
As a side-note, I'm curious about adding a project to re-do how we manage such projects. Basically, each project would be a GitHub Issue (tagged appropriately) and we'd generate a page based on those issues. It'd need tooling but would be more generally useful. Old issue is at: https://github.com/Unikernel-Systems/unikernel.org/issues/30
<dudelson>
From a GSoC applicant's perspective, I think using github issues would be very convenient
<dudelson>
that way we could have a thread where we could ask for clarification on the projects, etc.
<amirmc>
Indeed. You get a number of benefits, including a (kind of) ready-made mailing list
<amirmc>
It's also a lot clearer what progress has been made on a given project and if anyone is already working on it (e.g. via assigning it)
<Drup>
Yeah, I think it would be better to just list all the issues that are tagged "junior job" or something like that
<dudelson>
also being able to cross-reference other tickets nicely
<amirmc>
I dislike the term 'junior' but in principle, yes it would make things a lot easier.
<amirmc>
It's a project itself to build the tooling though. We still need an aggregate view for applicants to look through.
<amirmc>
Those issues would be across multiple repos too.
<amirmc>
Any takers? ;)
<yomimono>
rudenoise's dashboard would be a reasonable starting point for that project
<dudelson>
Please correct me if I'm wrong, but that tooling would also enable you to generate a page of "mirage starters", right?
<dudelson>
Since I'm new to the project I wanted an easy ticket so I could get familiar with the codebase
<amirmc>
dudelson: What does 'mirage starters' mean?
<amirmc>
dudelson: Oh, I see what you mean
<yomimono>
dudelson: that would be part of the goal, yeah
<amirmc>
My guess is that 'getting familiar' might itself be repo-dependent. :)
dudelson has quit [Ping timeout: 258 seconds]
<amirmc>
Anyway, I'm happy to help anyone who' like to tackle a project to redo how we manage the pioneer projects. It'd likely involve using the github libs (and that's assuming those libs and the API provide enough of what we need).
mort___ has quit [Quit: Leaving.]
<yomimono>
that's great amirmc :) we should make an addition to canopy-data for that!
<amirmc>
I'll write something up and add it later today.
<yomimono>
awesome! thank you!
<yomimono>
if there are no more words on that...
<yomimono>
...last item is "MeetBot, can someone set this up?" which would require me to say "any last words" less frequently
<yomimono>
there has been a TODO for this on the call agenda wiki for quite some time.
<amirmc>
It needs someone to set it up so we can start using it. I notice that our own camelbot isn't pushing logs anymore so we're directing people to logs that someone just happens to be keeping :)
<yomimono>
yes, the log situation has gotten even more dire recently; previously we had the raw meeting logs and now the best I can link to is the entire day's traffic :(
<yomimono>
gjaldon's summary of the last-but-one meeting was great but requires some manual labor and doesn't seem too sustainable
<yomimono>
I can't commit to having it ready for the next meeting in two weeks, but I can at least give it a shot since it seems there's no extremely-keen volunteer
<yomimono>
best-effort bot delivery, I guess.
<hannes>
morning
<hannes>
(sorry, was in a meeting till now)
<yomimono>
o hai!
<amirmc>
Thanks yomimono :)
<yomimono>
we were just moving on to the final item: GSoC/Outreachy candidates
<hannes>
[the mail was already sent, the dates are there: 29th nov - 6th dec]
<yomimono>
aha, thanks!
<amirmc>
That final item was me just checking that the candidates had received responses, to see where things stood, and also figure out how many we have interested.
<yomimono>
I've counted 3 interested GSoC students from the mailing list so far. I haven't heard from anyone directly about this Outreachy round yet.
<yomimono>
FWIW if anyone has questions about either program, lars_kurth and I are co-administrators. If you see anyone who's asked a question that's gone unanswered, feel free to nudge or cc me.
<yomimono>
If you have questions that you'd like to ask more privately, please also feel free to contact me - I was also an Outreachy participant with Mirage/Xen in 2014.
<yomimono>
(I can't speak for the GSoC student experience directly, unfortunately.)
dudelson has joined #mirage
strykerkkd has joined #mirage
<amirmc>
I guess that was the last item then?
* yomimono
refreshes wiki page
<yomimono>
so it would appear! any other business?
<yomimono>
HEARING NONE
* yomimono
pounds gavel
* hannes
just has to thank everyone participating the retreat.
<hannes>
(was overwhelmed to see so many nice people working on various topics, and opening so many PRs)
<amirmc>
*thanks hannes/hana for setting it all up*
<yomimono>
+100
amirmc has quit [Quit: Leaving.]
talex5 has quit [Quit: Leaving]
dudelson has quit [Ping timeout: 256 seconds]
mort___ has joined #mirage
thomasga has quit [Quit: Leaving.]
thomasga has joined #mirage
djwillia has left #mirage ["ERC Version 5.3 (IRC client for Emacs)"]
fgimenez has quit [Remote host closed the connection]
TImada has quit [Quit: Page closed]
<contrapumpkin>
anyone know about the lone .ml file in hyperkit?
<hannes>
contrapumpkin: if I were you, I'd open an issue on docker/hyperkit repo asking that question... it does not seem to be mirage related (and I have no clue)
<contrapumpkin>
fair enough :) I just asked a few weeks back if this was the place to ask about hyperkit and some people said it was!