avsm changed the topic of #mirage to: Good news everyone! Mirage 3.0 released!
philtor has joined #mirage
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
tlam has joined #mirage
mort___ has joined #mirage
argent_smith has joined #mirage
mort___1 has joined #mirage
mort___ has quit [Ping timeout: 246 seconds]
copy_ has joined #mirage
AltGr has joined #mirage
mort___1 has quit [Ping timeout: 255 seconds]
mort___ has joined #mirage
tlam has quit [Ping timeout: 240 seconds]
tlam has joined #mirage
AltGr has left #mirage [#mirage]
AltGr has joined #mirage
mort___ has quit [Ping timeout: 240 seconds]
mort___ has joined #mirage
tlam has quit [Ping timeout: 248 seconds]
aweinstock has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
tlam has joined #mirage
mort___ has left #mirage [#mirage]
AltGr has left #mirage [#mirage]
argent_smith has quit [Quit: Leaving.]
mort___1 has joined #mirage
mort___1 has quit [Quit: Leaving.]
mort___ has joined #mirage
AltGr has joined #mirage
mort___ has quit [Ping timeout: 240 seconds]
AltGr has left #mirage [#mirage]
tlam has quit [Ping timeout: 264 seconds]
philtor has quit [Ping timeout: 248 seconds]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
<aweinstock>
I'm trying to follow along with the mirage tutorial at https://mirage.io/wiki/hello-world, and can't build tutorial/noop; the error involves 'Error: Unbound module OS' in main.ml
<aweinstock>
I have ocaml 4.02.3 installed through debian stretch repo, opam 1.2.2 via 0install, and mirage 2.6.1 via opam
<aweinstock>
any suggestions for what to try next?
<hannes>
aweinstock: you should upgrade your OCaml and then get a newer mirage. 3.x is the current major release :)
<hannes>
aweinstock: since you have opam, you can use `opam switch 4.04.2` to get a new OCaml :)
<hannes>
(or opam switch 4.05.0 if you feel adventourus)
<aweinstock>
"Now compiling OCaml. This may take a while, please bear with us..."
<hannes>
mirage 3.x dropped 4.02 compatibility, the minimum version needed is 4.03 now.
<aweinstock>
(`opam switch` is nice to know about)
<hannes>
it will compile and install into ~/.opam/4.04.2/ -- where it also installs all the packages
<aweinstock>
once I have the new ocaml, opam will automatically get a newer mirage?
<hannes>
no. once OCaml is installed, you need to adjust environment variables in your shell -- by running "eval `opam config env`"
<hannes>
when this is done, "opam install mirage" will get you a new mirage :)
<aweinstock>
noop builds now (main.native runs with no errors)
<hannes>
\o/
<aweinstock>
hello builds too (same directory)
<aweinstock>
s/directory/repo/
<hannes>
depending on your environment, you may want to try mirage configure -t ukvm ;)
<hannes>
to get an actually freestanding unikernel (using kvm)
<aweinstock>
ukvm works with qemu?
<hannes>
it works with kvm from the linux kernel
<aweinstock>
(also, do I need to `make depend` after each `mirage configure -t foo`?)
<hannes>
it does - in contrast to other kvm linux vms - NOT use qemu
<hannes>
yes, make depend installs dependency - and they vary between targets
<hannes>
but of course you can just run make and see whether it fails or not (and if it fails, run make depend)
<aweinstock>
`./ukvm-bin hello.kvm` works (`./hello.kvm` on it's own segfaults)
<hannes>
yes! well, hello.kvm is a ELF binary expecting to be run in kernel context, thus running it as a unix process won't work
<aweinstock>
is it possible to run the .kvm file under qemu?
<hannes>
I guess the virtio stuff can be run under qemu, but the kvm unlikely... not sure... you may want to ask that on the mailing list where more people are active :)
mort___ has quit [Quit: Leaving.]
<aweinstock>
qemu-system-x86_64 -serial stdio -display none -kernel hello.virtio # this seems to work
<hannes>
! :)
copy_ has quit [Quit: Connection closed for inactivity]