00:55 <seangrove> Hey all, I've got a custom site working locally on the unix backend using Drup's No. as a starting point (with a pinned mirage/functoria). Works with the unix setup, but running into an issue under xen. Looks like something to do with Xenstore, so probably has to to do with https://github.com/Drup/No./blob/master/config.ml#L26, but I'm not sure - here's the output https://gist.github.com/sgrove/7bfb82074b4c623ccead

00:57 <seangrove> Drup: Might be better to go over it here

00:57 <seangrove> re: direct_kv_ro transformation, I thought I might have to run a preprocess step

00:58 <Drup> the preprocess should be automatic

00:58 <Drup> (during configure)

00:59 <Drup> (you have the certs and all that, right ?)

01:00 <seangrove> Hrm, should secrets/ also be crunched? I see static1.ml and static2.ml, but don't see anything from secrets crunched (unless they're automatically named that)

01:00 <Drup> yeah, it's named like that

01:02 <seangrove> Hrm, I wonder if the right files are ending up in there https://gist.github.com/sgrove/ebecfee7fa3bed126fe9

01:03 <Drup> you have the secrets generated ?

01:03 <Drup> (you said you just did "git clone", which would mean no :p)

01:03 <seangrove> s@ubuntu:~/No.$ ls secrets/ -> server.key server.pem

01:03 <Drup> right

01:03 <seangrove> (result of running `make secrets`)

01:04 <Drup> you need to configure again

01:04 <seangrove> I thnk that's likely it though, since I don't see server.key/pem listed anywhere in static2.ml

01:04 <seangrove> Ok, let me try6

01:05 <Drup> For me, it's crunched correctly

01:05 <Drup> (in static2)

01:05 <seangrove> Ok, great, seems likely then. I'm just running `mirage configure --xen`

01:05 <Drup> same here

01:07 <seangrove> Ah, that might have done it! Had to remove all generated ml files

01:07 <seangrove> Let's try another round of xen...

01:08 <Drup> The generated build system should rebuild those crunched ml file on demand :/

01:08 <Drup> Could you open a ticket about that ?

01:08 <seangrove> Drup: I will if I can repo, definitely

01:09 <Drup> It should be in the mirage repo directly

01:09 <Drup> (it's the one generating the makefile)

01:16 <seangrove> Hrm, same issue, sadly https://gist.github.com/sgrove/c36c548c5581ba56dac7

01:16 <Drup> :(

01:17 <Drup> This Xs error is really crap

01:17 <seangrove> Would this be appropriate to open as an issue? Don't want to distract everyone with n00b problems

01:17 <seangrove> But difficult to track down

01:17 <Drup> It's not really difficult to track down as much as "Xs_protocol.Enoent("read")" being completely unhelpful

01:18 <Drup> So yeah, open a bug report

01:19 <Drup> and if you feel very adventurous, you can try to add more info to this exception, like, on what it fails to read

01:19 <Drup> (I have no idea how difficult this is)

01:25 <seangrove> I suppose this isn't important, "Unsupported function lseek called in Mini-OS kernel". Seems to be everywhere, even the hello-world tutorial

01:26 <hannes> seangrove: that's what OCaml runtime calls during startup

01:27 <hannes> (I believe it is lseek on stdin/stdout)

05:07 <seangrove> Drup: I just realized that the failure is probably coming from https://github.com/Drup/No./blob/master/dispatch.ml#L16 or line 19

05:07 <seangrove> I'll check tomorrow morning

17:11 <seangrov`> Drup: Checked, but doesn't seem to be. Nothing logged from that function outputs at all (do I have to flush anything when using Printf.ksprintf ?)

17:44 <seangrov`> Drup: Progress! https://github.com/mirage/mirage/issues/488#issuecomment-181059385

19:02 <seangrov`> Drup: And looks like that solved it https://github.com/mirage/mirage/issues/488#issuecomment-181059385

20:00 <Drup> seangrov`: ah, nice !

20:58 <Drup> seangrov`: so, in the end, no modification to No is needed to run on xen ?