Dmitrii Ustiugov
Dmitrii Ustiugov
@Aneurysm9 thank you for the prompt response. In my understanding, if a module does not work in a recent version of Go by default, it must be considered a bug....
thank you! we are going to try that.
hi @Abhi4010, snapshot support is not yet complete in firecracker-containerd. You can use [vHive](https://github.com/ease-lab/vhive) or the API that we developed `vhive/ctriface` for managing MicroVMs on top of firecracker-containerd.
@Abhi4010 in vHive, we use our fork of firecracker-containerd where we added the snapshot-related functions. These modifications can be viewed [here](https://github.com/ease-lab/firecracker-containerd/pull/24)
hi @kzys sure thing! we are happy to contribute. We hope that this PR can establish the ground for finalizing snapshotting support together. Also, we did quite a few performance...
@kzys Sorry for the late response. We expect that a workflow where an idle VM can be snapshotted followed by freeing its resources with Offload (i.e., killed) on the **same...
@kzys Thank you! Indeed, the scenario that you mentioned makes a lot of sense. We took the easier path, by limiting our scenario to the same physical host, because we...
@kzys I call the disk state the following: 1) the images pulled by firecracker-containerd; 2) the devmapper block devices. According to the current way in which firecracker-containerd manages the VM...
@kzys we merged PauseVM, ResumeVM, and CreateSnapshot into the sdk. what should be our next steps?
@kzys are there any plans on finalizing the snapshots support? maybe, we could start discussing the next steps