Repository navigation
Conversation
… virt GCE nested-virtualization VMs expose a KVM that cannot reliably restore Firecracker device state, so memory-snapshot resume (the normal POST /sandboxes path) yields a running guest whose virtio-net is dead: envd is unreachable and the sandbox is marked stopping ~15s after create. Cold boot (filesystem_boot) works on the same node because it initialises devices from scratch rather than restoring them. This is a platform (nested KVM) limitation, not a runtime bug — pristine upstream Firecracker on the same GCE instance fails even earlier, exiting the moment a VM is paused. Document it in the GCP module README so operators reach for cold boot (or a bare-metal instance) instead of chasing a resume that cannot work there. Refs e2b-dev#3745.
AdaAibaby
requested review from
ValentaTomas,
dobrac and
jakubno
as code owners
October 29, 2026 02:10
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #3745.
Adds a Limitations on nested virtualization section to the GCP Embed module README: on GCE nested virt, cold boot works but memory-snapshot resume does not — the restored guest comes up with a dead
virtio-net(vCPU + lazily-faulted memory fine,envdunreachable, sandbox marked stopping ~15s after create).This documents a platform (nested KVM) limitation, not a runtime bug — confirmed in #3745 by the reporter running pristine upstream Firecracker v1.17.0 on the same instance, which exits the moment a VM is paused. Steers operators to the cold-boot path (
filesystem_boot) or a bare-metal instance instead of chasing a resume that cannot work on nested virt.