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

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

> 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