Re: [MirageOS-devel] Mirage on Raspberry Pi 3

["Daniel J Williams" <djwillia@xxxxxxxxxx>]

Joel Hughes <rudenoise@xxxxxxxxx> wrote on 03/07/2016 10:27:51 AM:
> Am I right in thinking that I can create a uni-kernel with solo5 in
> the form of a .iso? And this image could be run by QEMU like this:
> qemu-system-x86_64 -boot d -cdrom image.iso -m 512

Yes, the Makefile for Solo5 is a bit confusing, but you do end up with an .iso that is then run with QEMU.  You will need a few more parameters to make sure you have the network and disk devices for your unikernel: here is the current way I run them:

https://github.com/djwillia/solo5/blob/mirage/Makefile#L47


> So I'd need to build mirage outside the Pi but could then deploy it this way?

I would think it would be easiest to build a MirageOS/Solo5 unikernel outside, then deploy it to the Pi.  It's easiest to build using the solo5-mirage docker image, which has the build environment all set up.  I don't know if Dockerfiles can be used to build Docker images on different architectures, but I do expect it's possible to get the build environment manually set up on the Pi (install cross compilers, etc.).  I have no experience setting it up on a non-x86 environment so can't comment on how easy that would be, though.

Thanks,
Dan




> On 4 March 2016 at 18:47, Daniel J Williams <djwillia@xxxxxxxxxx> wrote:
> > From: Anil Madhavapeddy <anil@xxxxxxxxxx>
>
> > If this doesn't work out though, see if you can get KVM to work with
> > a Linux guest.  The work on Solo5 means that a KVM ARM port is
> > reasonably straightforward if we go down that path...
>
> If you want to go the Solo5/Mirage route, I wouldn't worry about
> KVM for now!
>
> I think you should be able to run Solo5/Mirage out of the box on
> the rPi3 on QEMU if you run QEMU in emulation-only mode.
>
> You should be able to find/install a QEMU package for ARM.  That
> will be able to provide a full system x86 abstraction to
> Solo5/Mirage.  Solo5 does expect an x86 environment (currently
> provided by QEMU in a Linux+KVM+QEMU system), so, as it stands, a
> lot of the virtual hardware initialization code in the Solo5
> kernel is x86 specific.  I think this will prevent you from using
> QEMU with virtualization assist by KVM with Solo5 on an ARM
> without changes to Solo5.
>
> I don't have a rPi3 either, but want to get one!  Then I'd be
> happy to help troubleshooting Solo5/Mirage on QEMU on the Pi!
>
> Thanks,
> Dan
>
> > On 4 Mar 2016, at 16:11, Joel Hughes <rudenoise@xxxxxxxxx> wrote:
> > I have a Raspberry Pi 3 and looking at the specs it seems comparable
> > to the cubieboard/cubietruck and thought that it might be possible
> > to run the Xen Hypervisor and MirageOS unikernels on it?
> > https://www.raspberrypi.org/magpi/raspberry-pi-3-specs-benchmarks/
>
> > Is KVM+Solo5 or U-Boot a good starting point?
> > Is there an effort in progress to work on this, if so I'd love to help out?
> >

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel