Results 15 issues of Babis Chalios

# 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...

Contribute: Good First Issue
Feature: IO Virtualization
Performance: IO
Status: Author

## Reason Right now we have one pair of (IdAllocator, AddressAllocator) per device manager (mmio and legacy for x86, mmio for aarch64) and we separate the resources (GSIs and guest...

## Changes TODO: fill up. Use this PR to test CI/CD atm ## Reason TODO: fill up ## License Acceptance By submitting this pull request, I confirm that my contribution...

## Changes This is a WIP rough draft of ACPI support for x86. Opening this PR for testing the PR itself but also the CI artifacts. ## Reason TBD ##...

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

## Changes Introduce ACPI support for x86_64. ## Reason Introducing ACPI will let us do a couple of things: * Get rid of the i8042 (minimal) emulation. We will be...

### Description Currently, parts of our virtio code use usize to describe the lengths of descriptor chains [[1](https://github.com/firecracker-microvm/firecracker/blob/036d9906a09ed759597ee88bab6c1278e4fd7655/src/vmm/src/devices/virtio/iovec.rs#L43)], while other parts use u32, which results in some ugly casts that...

Good first issue

### Description When the guest wants to transmit an ethernet frame over a virtio-net device it places the frame somewhere in guest memory and sends us an interrupt. A single...

Good first issue
Status: Parked

Updated on 05/09/2025: Currently, the logic to create a Vm and a Vmm objects is scattered across vmm/lib.rs and vmm.builder.rs files and it is quite convoluted and some times difficult...

Priority: Low
Status: Parked

## Changes Use AmazonLinux tailored guest configs for our 6.1 guest microVM kernels. Also, split the Kconfig for our CI kernels in a base part which will always be reflecting...