Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Self-hosted Embed: snapshot marked successful crashes on restore

未关闭
#3,659 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 3 天内回复

@svalleru 已经在做这个了。

开始于 2026年9月23日。

评估

这个 Issue 还没有评估数据。

描述

On self-hosted Embed, a snapshot marked success crashes Firecracker on every restore attempt. The previous snapshot of the same sandbox restores normally.

Firecracker panicked at src/vmm/src/devices/mod.rs:34:9:
The number of available virtio descriptors 41919 is greater than queue size: 256!
Verified
  • The runtime logged a successful upload and marked the snapshot build success.
  • Restoring the saved snapshot through Sandbox.create("<env>:default") on a fresh, healthy host with the same binaries produces the same panic 3 out of 3 times. The copied snapshot files and dependencies were hash-verified.
  • The previous snapshot, captured 42 minutes earlier, restores and runs guest commands on that host.

The original host logged repeated No space left on device errors before capture, but these logs do not establish the cause. The tests reproduce the restore failure using the preserved snapshot, not the original capture failure.

Expected result

A snapshot marked successful should be restorable. If saving it fails, report the failure and preserve a recovery path for the sandbox.

Environment
  • Single-node Embed, local file storage; Ubuntu 26.04 ARM64 VM with nested virtualization
  • Orchestrator v0.16.202609130627-59497eb9134; API v0.14.202609170000-908833e4c12
  • Firecracker v1.14-0.2.0 (reports v1.14.4); hugepage-backed sandbox, 2 vCPU / 2048 MiB
  • Compose revision: a065a4ddb3f2c6a4149634d9acb14b62f65839ac

Snapshot artifacts and logs are preserved. Related: #3658 covers losing a sandbox when pause reports an error.

主要语言
Go
星标
1.6k
派生
448
PR 合并指标
30 天内没有已合并 PR

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

e2b-dev/runtime 的其他 Issue

查看 e2b-dev/runtime 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。