about summary refs log tree commit diff
path: root/users/fcuny (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-06-11repo(containerd-to-vm): remove unneeded filesFranck Cuny2-40/+0
Change-Id: I4d229d0f4a9142e3bd427a8e63733426f5ca5bd9 Reviewed-on: https://cl.fcuny.net/c/world/+/412 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-06-11publish firecracker metrics in a FIFOFranck Cuny1-2/+4
We add a new argument to the CLI to collect the path where we want to publish the firecracker metrics.
2022-06-11Makefile: install binaries and configsFranck Cuny1-6/+23
To help working on this project in the future, let's try to install dependencies and configurations with `make`. For now we know that we need the firecracker binary, the CNI configuration and the CNI plugin for TAP.
2022-06-11rename the variable for the linux kernelFranck Cuny1-7/+7
2022-06-11c2vm: fix kernel boot optionsFranck Cuny1-1/+1
By specifying these options we can speed up the boot process from 0.9 second to 0.15 seconds. Without these options, the linux kernel spends a few milliseconds probing the device, which is useless in our context (see https://github.com/firecracker-microvm/firecracker/blob/main/docs/api_requests/actions.md#intel-and-amd-only-sendctrlaltdel)
2022-06-11readme: update instructionsFranck Cuny1-0/+16
2022-06-11boot the VMFranck Cuny3-4/+256
The binary needs a few more arguments: the path to the firecracker binary, the path to a linux kernel. Using the image that was generated, we can now boot the VM with firecracker. This will rely on a CNI configuration to create the network, and will use the provided kernel to boot.
2022-06-11hack: firecracker binary and CNI configurationFranck Cuny3-0/+35