Babis Chalios

PRs #4428 and #4487 added support for ACPI and VMGenID, respectively, on x86 platforms. Once we add support for kernel 6.1, Firecracker will officially support VMGenID on x86 platforms. For...

Hi @dush-t, you need Linux KVM to test this.

Thanks for raising this up @howard0su. I'm trying to understand what is that you are worried about here. Is it the amount of memory (heap size) or the time overhead...

Hey @CuriousGeorgiy? Is this still an issue? I think you found out that you can patch the drivers after loading a snapshot and before resuming the microVM (not considering the...

So, the resource renaming approach is what the `PATH /drive` API does. Unless @roypat referred to something else, I 'm missing?

Oh, I see now. You and Patrick are right. As Patrick said, this is a limitation the snapshot API has at the moment. FYI not just for block devices, net...

Hi @jseba, Thanks for the contribution. I have some questions to understand a bit more the context: You send `SIGUSR2` to let Firecracker know that its parent process died. Please,...

Thanks for the explanation @jseba. > I used SIGUSR2 as the signal that firecracker gets from the OS on its parent's death Just to clarify, the signal does not arrive...

> No, the signal comes from the kernel directly, no other management process is involved. That's why I selected a different signal to differentiate it since otherwise it is indistinguishable...

> Linux by default sends nothing. The PR_SET_PDEATHSIG option tells it to send the designated signal to the calling process when the calling process's parent dies. Thanks, I didn't know...