eval aws firecracker

[eyberg]

just from me glancing at the docs it looks very similar to gvisor and it relies on known good kernels which to me implies they are doing guest introspection - meaning it won't work but worth at least looking more into and seeing if it's something that down the road makes more sense

[eyberg]

few more clues from twitter - no pci support which has implications for virtio, et. al

[bneil]

Yeah, looking into https://medium.com/solo-io/unik-is-here-to-help-bring-aws-firecracker-to-serverless-apps-1250d120997d it looks like some work could be done to see how the unik project is working with firecracker

[eyberg]

Afaik they are not deploying unikernels to that, just normal linux bins but waldek from osv hacked osv in

[eyberg]

this uses the same underlying libraries used by firecracker w/out all the framework overhead

https://github.com/intel/cloud-hypervisor

Virtio block device configured. Capacity: 11773 sectors
Failed to find EFI partition
Starting..
Page tables setup
Found PCI device vendor=8086 device=d57 in slot=0
Found PCI device vendor=1af4 device=1042 in slot=1
Found PCI device vendor=1af4 device=1044 in slot=2
PCI Device: 0:1.0 1af4:1042
Bar: type=MemorySpace32 address=e7f80000
Bar: type=MemorySpace32 address=0
Bar: type=MemorySpace32 address=0
Bar: type=MemorySpace32 address=0
Bar: type=MemorySpace32 address=0
Bar: type=Unused address=0
Virtio block device configured. Capacity: 11773 sectors
Failed to find EFI partition
^C
root@Box:/home/eyberg/x# /home/eyberg/cloud-hypervisor/cloud-hypervisor/target/release/cloud-hypervisor --kernel ./hypervisor-fw --disk path=g.img --cpus 1 --memory size=1024M --rng --serial tty --console
off

looks like it wants an efi compatible bootloader

[eyberg]

this isn't really an ops issue but initial support has landed in nanos -> nanovms/nanos#1213