On Monday, February 11, 2019 at 3:54:39 AM UTC-5, Nadav Har'El wrote:
>
> On Sun, Feb 10, 2019 at 10:50 PM Waldek Kozaczuk > wrote:
>
>> This patch is not meant to be applied but it serves to illustrate what is
>> left to make OSv boot on firecracker. As you can see it is not a daunting
>>
On Monday, February 11, 2019 at 3:48:20 AM UTC-5, Nadav Har'El wrote:
>
>
> On Sun, Feb 10, 2019 at 10:22 PM Waldemar Kozaczuk > wrote:
>
>> - clean up modern/legacy virtio support (configurability)
>> - add virtio-mmio support including parsing virtio-mmio devices from
>> command line
>> -
On Monday, February 11, 2019 at 2:00:59 AM UTC-5, Nadav Har'El wrote:
>
> On Mon, Feb 11, 2019 at 1:33 AM Waldek Kozaczuk > wrote:
>
>> Here is the scenario:
>> 1) Build image with some app X and httpserver API module.
>> 2) Start app X using REST API /app call with new_program=false (same
>>
On Mon, Feb 11, 2019 at 10:54 AM Nadav Har'El wrote:
> Maybe you can even add to run.py a firecracker hypersor options, so if
> someone just installs this hypervisor he can use run.py?
>
That's a very good idea!
- Pekka
--
You received this message because you are subscribed to the Google
On Sun, Feb 10, 2019 at 10:50 PM Waldek Kozaczuk
wrote:
> This patch is not meant to be applied but it serves to illustrate what is
> left to make OSv boot on firecracker. As you can see it is not a daunting
> amount of work anymore given modern virtio is supported now.
>
> In am not sure in
On Sun, Feb 10, 2019 at 10:22 PM Waldemar Kozaczuk
wrote:
> - clean up modern/legacy virtio support (configurability)
> - add virtio-mmio support including parsing virtio-mmio devices from
> command line
> - enhance boot.S and OSv boot in general to support vmlinux format
> (decompressed ELF
