11:39 <free_beard> Hi, I'm a beginner with MirageOS and was looking to test some demo unikernels on my laptop. The closer I got to figuring it out was https://github.com/mor1/mirage-vagrant-vms . Do you have a better suggestion on how to try it out locally and/or deploy to GCP?

13:11 <hannes> free_beard: depends on your laptop OS -- but generally https://github.com/mirage/mirage-skeleton is a good starting point for examples

13:12 <hannes> if you're using xen, use -t xen and xl to run unikernels, if you're using kvm, use -t hvt and solo5-hvt.

13:12 <free_beard> hannes thanks, I've been through those examples, configuring them with -t unix, but I was trying to get some practice with compiling a kernel and deploying it somewhere

13:12 <hannes> free_beard: as said, it depends on your host OS.

13:13 <hannes> free_beard: for GCP, yomimono wrote some notes at https://somerandomidiot.com/blog/2018/07/16/ditch-aws-build-host/

13:13 <free_beard> I run linux, so I'm guessing your suggestion is installing xen.

13:13 <hannes> free_beard: no.

13:13 <free_beard> oh, thank you for the link, I only found a much older one

13:14 <hannes> free_beard: I said "if you're using xen". on Linux there's as well kvm (another hypervisor) which is more mainstream than xen these days, and that can be used by mirageos with the -t hvt target

13:15 <hannes> you can as well use the -t spt for a sandboxed process tender (using solo5 and seccomp, no hardware virtualization)

13:15 <hannes> you can also use -t virtio and then qemu to run your unikernel locally

13:16 <h01ger> can one run mirageos unikernels in a webbrowser? ;)

13:16 <apache2> h01ger: not yet :)

13:17 <free_beard> I need to look into the -t spt suggestion, but -t virtio with qemu looks very promising. If I do -t hvt, I still need the solo-5 binary wich doesn't get built (the hello mirage tutorial makes it seem like it's supposed to be an artifact of the build)

13:19 <hannes> free_beard: (https://mirage.io/wiki/hello-world#Building%20for%20Another%20Backend discusses some more detail)

13:19 <hannes> free_beard: yes, sorry about that. it recently changed (within the solo5 0.6 release series and mirage 3.6.0).

13:20 <hannes> free_beard: we have not yet announced that change, and have not updated the documentation sufficiently (sorry :/)

13:20 <hannes> these days, solo5-hvt is installed by solo5-bindings-hvt, so not built tailored to the unikernel

13:20 <hannes> instead of ./solo5-hvt hello.hvt, a solo-hvt hello.hvt should work :)

13:21 <hannes> (it is installed to $OPAM_PREFIX/bin/solo5-hvt -- a which solo5-hvt should find the location)

13:21 <free_beard> @hannes ah, silly me

13:21 <free_beard> i have it

13:21 <hannes> free_beard: it is silly us /o\

13:21 <free_beard> it installs it with make depends

13:21 <free_beard> i think I tried it before running make depends and I didn't have it

13:22 <hannes> ic

13:23 <free_beard> I can make a PR to the website if this helps and it doesn't require a more thoughtful change of the docs

13:25 <hannes> free_beard: thanks, I think it requires mainly a grep for ./solo5-hvt, and an adjustment to the solo5 version required (>= 0.6, mirage >= 3.6.0). of course a PR would be welcome! :)

13:37 <mato> free_beard: yes, the docs have not been updated for 3.6.0, sorry about that

13:38 <mato> i'm working on it, but got distracted with various issues with the tools (mirage-www)

13:38 <mato> given that the docs aren't updated, this is also why i've not yet sent out a release announcement

13:41 <free_beard> No problem, I was happy to figure it out - https://github.com/mirage/mirage-www/pull/656 if it makes sense

13:49 <mato> free_beard: without going into explanations, there are two other things that changed relevant to that tutorial

13:49 <mato> free_beard: wherever it says --disk=disk.img, it should say --block:storage=disk.img

13:50 <mato> free_beard: and wherever it says --net=tap100, it should say --net:service=tap100

13:50 <mato> (in the solo5-hvt invocations, that is)

13:50 <free_beard> thanks! I'll update

13:51 <mato> ta