Adrian Catangiu

Hi @sheepa, Firecracker does not support automatic reduction of the image size on the host when a file is deleted on the guest. Firecracker emulates raw block devices with fixed...

@lyuyuan92 sounds good! Please do some benchmarking as well to make sure this is an improvement. As an example: check out the [Firecracker demo](https://github.com/firecracker-microvm/firecracker-demo) to see how `iperf` is used...

Also check out https://github.com/firecracker-microvm/firecracker/pull/937 to see another improvement and how it was benchmarked.

@lyuyuan92 indeed, the point of it (if yet possible in rust) is to avoid buffers in Firecracker device emulation code and write from the virtio rings (guest memory as you...

> This being said, I would close this issue without any action. Looks like it. It'd be cool if you could keep that branch around or find a long-term place...

My 2c is this is a valid use-case that `firecracker` could support _in addition_ to existing behavior of creating _new_ snapshot containing just _the diff bits_. There are two different...

I don't think we should unregister in case of any of those events. But all devices do need to gracefully handle them. L.E. apparently the `EPOLLHUP` cannot be consumed and...

+1 on each instance of each component to have its own metrics (so one could see how many packets a particular net device 2 has sent, for example). Unfortunately, on...

Metrics themselves don't need locks since they're atomics, so a solution would also be to decouple the writer from the metric implementation. Then you can use different writers for different...

Hi @cmannett85, we do not have formal requirements for formatting error messages. We do however try to keep them short and clear and also try to reuse the same static...