firecracker icon indicating copy to clipboard operation
firecracker copied to clipboard

Secure and fast microVMs for serverless computing.

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

Recently, some cpu/memory related benches(lmbench) have been tested on arm baremetal, qemu/kvm VM, and fireracker microvm. A striking difference from the X86 platform is that most of the benches on...

Type: Question
Priority: Low
Status: Awaiting author

Quality: Improvement
Priority: Low
Quality: Technical Debt
Feature: KernelPolicy
Status: Waiting on implementation

# Feature Request Create integration test for testing snapshot restore on CPUs with different TSC frequencies. ## Describe the desired solution Create a integration test to validate this code: https://github.com/firecracker-microvm/firecracker/blob/f2f8802122cf20fa043600290dcc938c96b9611d/src/vmm/src/builder.rs#L482...

Type: Enhancement
Status: Parked

Doing hardware-accelerated inference in a serverless environment is compelling use case. However, adding straight up GPU passthrough means that microVM can't oversubscribe memory, and we need to add PCI emulation...

Type: Enhancement
Status: Parked

This issue is a follow up of https://github.com/firecracker-microvm/firecracker/issues/2783. The bulk of the issue was solved in this PR: https://github.com/firecracker-microvm/firecracker/pull/2806 There are still a couple of loose ends that could be...

Quality: Bug
Contribute: Help Wanted
Contribute: Good First Issue
Priority: Low
Status: Waiting on implementation

We are currently constraining `test_serialization_benchmark` to run only on Intel. We need to gather baselines on AMD and ARM and enable the test on all supported CPUs.

Quality: CI
Status: Waiting on implementation

The test should send multiple successful HTTP requests on the same connection and validate the API server does not close connection even for **error** responses.

Quality: Automated Testing
Priority: Low

At the moment, the current device event handling implementation, for net, block and vsock devices, does not handle errors which might occur on the epoll registered event `fd`s (`EPOLLHUP`, `EPOLLRDHUP`,...

After switching to the event-manager implementation from rust-vmm, we can optimize the process function that is called when events for virtio devices become available. As this code is on the...

Priority: Low
Codebase: rust-vmm
Performance: Misc