firecracker icon indicating copy to clipboard operation
firecracker copied to clipboard

Secure and fast microVMs for serverless computing.

Results 254 firecracker issues
Sort by recently updated
recently updated
newest added

Hi, Firecracker doesn't have fast enough networking for many users. Firecracker networking benchmarks claiming tens of Gbps use TCP and use network offloads (TSO). However, often for real users these...

Roadmap: New Request

## Changes Tidying for https://github.com/firecracker-microvm/firecracker/blob/main/docs/device-api.md ## Reason Minor cleanups for readability and context. ## License Acceptance By submitting this pull request, I confirm that my contribution is made under the...

This is a tracker for investigating improvements in the Firecracker networking stack. We are mainly looking to improve performance (throughput, latency and CPU utilization) of the emulation logic. However, we...

Status: WIP

# Feature Request Add snapshot support for vhost-user-blk devices. ## Describe the desired solution Firecracker implements saving and restoring from snapshot VMs that have block devices backed by vhost-user attached....

Roadmap: Tracked
Type: Enhancement
Type: Performance

# Describe the bug When FreeBSD boots in Firecracker, it disables LRO features because it doesn't want to allocate 64 kB buffers. (Maybe this should change in FreeBSD, but that's...

Priority: Medium

## Changes ... ## Reason ... ## License Acceptance By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license. For...

We have lot of links in our md files which are broken and could be broken due to refactoring of code. We need to add a new CI test which...

# Describe the bug It is expected that up to 96 devices can be used on aarch64, however If more than 64 devices are attached to an aarch64 microVM, only...

Type: Bug
Good first issue
Priority: High
Status: Parked

## Changes This adds a flag to set the parent death signal (SIGUSR2 in this instance) that the process will receive when its parent process exits before the VMM does....

This is a tracking item for dropping the support of static CPU templates in v2.0.0. The deprecation of static CPU templates has been announced and discussed in [this discussion](https://github.com/firecracker-microvm/firecracker/discussions/4135) and...

Roadmap: Tracked