firecracker
firecracker copied to clipboard
Secure and fast microVMs for serverless computing.
# Avoid extra memory copy when writing to tap device in virtio-net TX path Currently, when performing TX, a network frame might be exist in various scattered in various memory...
The snapshot restore operation is slower on AMD than on Intel. We should investigate why and either fix the root cause or change the `test_snapshot_resume_latency` test in order to check...
# Describe the bug We rely heavily on the MMDS in Firecracker for cloud-init with the **nocloud** data source (i.e. `ds=nocloud-net;s=http://169.254.169.254/latest/`). With Firecracker v0.25.2 this works but upgrading our solution...
# Describe the bug Using `tools/devtool build_rootfs` multiple times concurrently results in the rootfs failing to mount. ## To Reproduce 1. Create a loop that runs many times concurrently (I...
# Feature Request It would be nice to support the PVH direct boot API. Guest operating systems which have support for Xen/PVH will find this much easier than trying to...
Not a bug, but not a feature request. It's related to documentation. On [this page](https://github.com/firecracker-microvm/firecracker/blob/main/docs/prod-host-setup.md) in the [Jailer Configuration](https://github.com/firecracker-microvm/firecracker/blob/main/docs/prod-host-setup.md#jailer-configuration) section it states: > For assuring secure isolation in production deployments,...
Signed-off-by: Marco Cali # Reason for This PR Modify the documentation to include explicitly the max number of vCPU supported and other minor grammatical changes. Fixes #3059 ## Description of...
# Feature Request Improve the documentation and give better clarity of how many vCPU are supported into Firecracker. ## Describe the desired solution Documentation should state the max number of...
Install `shellcheck` (or a similar checker) inside devctr and add a python integration test that runs it on the shell scripts we have in Firecracker, like `tools/devtool` and other `.sh`...
# Describe the bug The memory map provided by Firecracker is ``` [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fffffff] usable ``` In other words, the first...