Improve snapshotting functionality#29
Conversation
…ns and restorations Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
…pace Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
…m network namespace Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
…pshots Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
| message FirecrackerMachineConfiguration { | ||
| string CPUTemplate = 1; // Specifies the cpu template. Example: "T2" or "C3" | ||
| bool HtEnabled = 2; // Specifies if hyper-threading should be enabled | ||
| bool TrackDirtyPages = 3; // Specified if dirty-page-tracking should be enabled. |
There was a problem hiding this comment.
please move to the 5th position to allow backwards compatibility.
| // for a microVM should be large enough | ||
| uint32 MemSizeMib = 3; | ||
| uint32 VcpuCount = 4; // Specifies the number of vCPUs for the VM | ||
| uint32 MemSizeMib = 4; |
|
|
||
| // Once the VM is ready, also start forwarding events from it to our exchange | ||
| attachCh := eventbridge.Attach(ctx, s.eventBridgeClient, s.eventExchange) | ||
| if ! s.snapLoaded { |
There was a problem hiding this comment.
refactor for a better code style:
if s.snapLoaded { return }
<...> // everything just like before but without an indent
|
|
||
| // shutdownSnapLoadedVm shuts down a vm that has been loaded from a snapshot | ||
| func (s *service) shutdownSnapLoadedVm() error { | ||
| // Kill firecracker process and its shild processes |
There was a problem hiding this comment.
| // Kill firecracker process and its shild processes | |
| // Kill firecracker process and its child processes |
| DialTimeout: 100 * time.Millisecond, | ||
| RequestTimeout: 10 * time.Second, | ||
| ResponseHeaderTimeout: 10 * time.Second, | ||
| DialTimeout: 1000 * time.Millisecond, |
There was a problem hiding this comment.
is there a reason for this timeout increasing? why to those values?
There was a problem hiding this comment.
I noticed some timeouts when restoring or loading snapshots, as far as I remember especially for larger memory sizes which makes sense. The values are chosen quite arbitrarily.
There was a problem hiding this comment.
try decreasing them (e.g., try 2x vs 10x as of now). large timeouts create issues in the control plane, the system becomes less responsive
|
|
||
| // Offload Shuts down a VM and deletes the corresponding firecracker socket | ||
| // and vsock. All of the other resources will persist | ||
| // and vsock. All of the other resources will persist. Depracated! |
There was a problem hiding this comment.
| // and vsock. All of the other resources will persist. Depracated! | |
| // and vsock. All of the other resources will persist. DEPRECATED! |
Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
d6e4a75 to
aff3d2b
Compare
0e94206 to
032bd10
Compare
Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
032bd10 to
45eba1d
Compare
Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
…cker-containerd into v0.25_reference Signed-off-by: Amory Hoste <amory.hoste@gmail.com>
ec1680b to
19c96c0
Compare
This PR adds the following changes