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
> namespace)
> 3) OSv loads app library and any dependent ones from disk and executes i
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
namespace)
3) OSv loads app library and any dependent ones from disk and executes it.
4) Start app X again same way as in 2) over and over again (unl
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 what order we should implement the remaining work.
Ideally every pat
- 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 64-bit Linux kernel)
- pass e820 and command line parameters through
From: Waldemar Kozaczuk
Committer: Nadav Har'El
Branch: master
Enhance scripts/test.py to pass extra arguments to run.py
This patch enhances scripts/test.py to allow passing
extra arguments to run.py. This allows executing running
unit tests with different than default parameters.
See example
On Sat, Feb 9, 2019 at 6:31 AM Waldemar Kozaczuk
wrote:
> This patch enhances scripts/test.py to allow passing
> extra arguments to run.py. This allows executing running
> unit tests with different than default parameters.
>
> See examples below how to run tests with different
> virtio configurat