<saji>
hannes: for reasons unknown to me, it insists to use mirage-qubes 0.7, which obviously doesnt have the fix.
<saji>
after manual pin-down of ppx_cstruct to 5.0.0 (which is the last version before 5.1.1 afaict) it builds, but the result explodes in a way i have never seen before ... during boot.
<hannes>
saji: sorry no time to look into this, you may be better of opening issues / post to the mirageos-devel mailing list..
<saji>
no hurry at all, reynir said he might look into it later, just wanted to dump it here since its a pile of opam idgi again. :)
<saji>
highlighted you because you commited that fix it isnt using for whatever reason.
<hannes>
saji: your boot issue, is this related to mirage-qubes 0.7.0 vs 0.8.0? i.e. does everything work find if you use an arcane mirage and an old mirage-qubes (opam pin add mirage 3.5.0 && opam pin add mirage-qubes 0.7.0)?
<saji>
can try. this is mirage qubes 0.7 with mirage 3.6.0 ...
<saji>
i dont know how to make it use mirage-qubes 0.8
<hannes>
ah
<hannes>
if it is mirage-qubes 0.7.0, it is at least not the rather lengthy changes for 0.8.0 which broke your boot
<hannes>
i.e. no need to try mirage 3.5.0
<saji>
ok.
<hannes>
(I was for a brief period worried that my 3.7.0 ++ 0.8.0 changes broke your boot)
<saji>
i didnt try to figure out what deps-chain makes it pick 0.7 there
<saji>
(random guess would be it installed cstruct 5.1.1 first, then decided to use qubes-mirage 0.7 because 0.8 says it doesnt like cstruct 5.1.1 ... but i know nothing about the opam deps resolving.)
<saji>
hm. should i try a newer ocaml version? its set to 4.05.0 currently ...
<saji>
ah-ha! that is actualy the reason it picked the 0.7
<hannes>
to minimize your carbon footprint, take 4.08.1 (afair the mirage-ocaml-xen stuff isn't 4.09.0 ready yet)
<saji>
ohgod, you are smoking that developers-for-future stuff, yes? :P
<hannes>
I'm mainly a troll and wanted to save you some time ;)
<saji>
thanks. bootstrapping a new switch _does_ take forever on this chromebook, yes.
<hannes>
...and now you wonder how i'd know ;p
<saji>
nah, i just assume you are running on 2007 hardware for "financial" or "libre" reasons. :P
<saji>
hm. switch init is done, now its on the first batch of modules (mirage + xen) and decided to use cstruct 5.1.1 again ... but it is probably going to downgrade that again in one of the next rounds.
_whitelogger has joined #mirage
<saji>
hehe, yup, its now uninstalling 5.1.1 and installing 5.0.0 ...
<saji>
fails in a way i dont understand, but not in deps hell!
<saji>
(but the whole gui stuff is not needed, so lets see what happens if i remove it...)
<saji>
(build completed, now installing...)
_whitelogger has joined #mirage
<saji>
reynir: i basicly just used the mirage.conf in examples, removed all mentions of firewall and after get-sources changed ocaml version from 4.05.0 to 4.08.1 in Makefile.builder ...
<saji>
(well, and removed all mentions of GUI from unikernel.ml. pesky details.)
<reynir>
Yea, the interface for the gui stuff was changed :/ I'm a bit annoyed I didn't raise this before it was released...
<saji>
i am out of ideas what else i could try
<saji>
(doubt the gui change is a problem beyond "minor nuisance during build")
<reynir>
I have patched for the gui changes somewhere
<reynir>
I should merge that to master...
<reynir>
I'm having a guest over (from Berlin) any minute now
<saji>
i will be afk for the rest of the day too
<saji>
as said, nothing urgent, just that hag this morning is a good reason to make a fresh build.
<saji>
(one hang a year that can be fixed by restarting a stateless vm doesnt bother me, really.)
<reynir>
heh
<reynir>
I've had kernel panics in the linux vms more often ;)
<reynir>
(which is a bit worrying tbh)
<saji>
want a PR for the s/4.05.0/4.08.1/ or can you "apply" that while merging?
<reynir>
hmm what needs to be changed regarding 4.05.0/4.08.1 ?
<saji>
nothing, just the version in Makefile.builder
<saji>
that makes it use the mirage-qubes 0.8.0 (which makes it work around the cstruct issue)
<saji>
but then runs into the GUI change.
<reynir>
ohh, I've completely been ignoring that stuff :/
<reynir>
I would appreciate a PR :-)
<saji>
so the version change itself is "useless" without a fix for the GUI stuff.
<saji>
:P
* saji
goes to look for a dev vm that has access to the right gpg/ssh keys ...
<reynir>
Ah, if it's a hassle I can just do it myself heh
<saji>
going to change the version in README too, because 4.05 really seems to be out and out.
<reynir>
Yea
<reynir>
Thanks!
<saji>
(and i really, really, really need to do these commits-for-pr in separate branches instead of using master and force-pushing...)
<saji>
ouch. actualy i did that version change in august and there is a PR open since then.
<saji>
but the pr _comment_ mentions mirage-xen too, and i dont remember what if anything about that i changed back then. and the change is gone now because of the force push.
<saji>
oooh, that was the s/OS/Os_xen/ thing. confused now.
<saji>
ah. that change is no longer required since you removed the memory_pressure stuff
<saji>
added comment in the existing PR and pinged you.
aedc has joined #mirage
pie_ has quit [Ping timeout: 268 seconds]
aedc has quit [Ping timeout: 268 seconds]
pie_ has joined #mirage
pie_ has quit [Ping timeout: 268 seconds]
pie_ has joined #mirage
pie_ has quit [Ping timeout: 265 seconds]
pie_ has joined #mirage
_whitelogger has joined #mirage
pie_ has quit [Ping timeout: 260 seconds]
pie_ has joined #mirage
<reynir>
saji: Thanks. I don't seem to get notifications on that repo even though I have it enabled!? Drives me a bit mad...