ShadowCurse

Closing this issue. The fix is present in the new Linux kernels. If anyone sees it again, please reopen it.

Hi all, sorry for the delay, unfortunately we were not able to make progress regarding this issue. We are still tracking the problem and will provide an update once we...

I have been looking through our usage of snapshots and I think we can remove `Write`/`Read` traits and use plain old `&[u8]` for `load` and just return a `Vec` for...

@roypat The `mmap` thing is basically: - open snapshot file - get the length (`file.metadata().size()`) - `mmap` the file with correct length The way we can keep it within Rust...

I haven't explored the idea throughout, but what if we combine all "device managers" (`pio_device_manager`, `mmio_device_manager`, `acpi_device_manager`) into 1 `DeviceManager`? This way it can contain all resource allocators and will...

Don't think returning errors makes a lot of sense here. There are 2 paths: panic and abort the process, or log the error and continue execution. In case of `read_config`...

@kornelski Also please fix compilations/stylistics errors from here: https://buildkite.com/firecracker/firecracker-pr/builds/9248#_

Hi @bduffany. We are still working on the root cause of this issue. We will update you as soon as possible.

@bchalios Basically with `rand` you can compile firecracker only using rust tool chain. It makes development easier, because it can eliminate container requirement.

Hi @lebron8dong, we recently updated [network setup doc](https://github.com/firecracker-microvm/firecracker/blob/main/docs/network-setup.md) with correct `MAC` address usage. If you use default `rootfs` from [getting started](https://github.com/firecracker-microvm/firecracker/blob/main/docs/getting-started.md), can you check if this update fixes your issue?