microvm: bump cloud-hypervisor to v54.0

Aperta
  • Qualcosa non va?
#3,250 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
56/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go
Ambito
backend, infrastructure

Direzione di ricerca

Start with the pinned version in hack/microvm-assets/assemble.sh, then read manifests/microvm/sandboxconfig-microvm.yaml.tmpl and the prior upgrade in #3181 to understand the digest and SandboxConfig name changes. Check cmd/ateworker-microvm/internal/ch/prefault.go and the restore path in cmd/ateworker-microvm/restore.go; decide how to handle the new virtio-net offload defaults and update the comment about vhost-user requiring Copy. Done when the v54.0 upgrade accounts for these compatibility and restore details.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/microVM kind/feature

Substrate microVM pins CH_VER="v53.0" in hack/microvm-assets/assemble.sh. Cloud Hypervisor v54.0 ships several fixes and features that affect ateworker-microvm:

What upgrade brings
  • VM Generation ID (vmgenid, cloud-hypervisor#8907): exposes an ACPI vmgenid device by default on x86_64 and aarch64 (acpi=on on aarch64) that updates its GUID and interrupts the guest on vm.restore. This CHv feature is marked as required TODO in cmd/ateworker-microvm/restore.go. This will enable Substrate implement faster entropy initialization for reseedGuestCRNG.
  • Snapshot and restore fixes: fixes short reads and writes that could truncate snapshot files or hang a restore (cloud-hypervisor#8897), preserves virtio queue indices across resume (cloud-hypervisor#8626), fixes a panic when restoring a VM with an unused virtio queue (cloud-hypervisor#8702), and speeds up vCPU state save/restore (cloud-hypervisor#8961).
  • vsock, vhost-user, and TAP fixes: stops replying to vsock RST packets with an RST (cloud-hypervisor#8692), releases vsock local ports only to their owner (cloud-hypervisor#8612), aborts vhost-user reconnect cleanly on teardown (cloud-hypervisor#8759), and drops TX frames instead of exiting the VM when the TAP device returns EIO (cloud-hypervisor#8723).
  • Host scale and seccomp: fixes musl CPU affinity on hosts with 128 or more CPUs (cloud-hypervisor#8972), allowlists missing syscalls in the seccomp filters, and applies a seccomp filter to the main thread (cloud-hypervisor#9062).
Notes
  • Bumping CH_VER changes the cloud-hypervisor digest in manifests/microvm/sandboxconfig-microvm.yaml.tmpl, so the SandboxConfig name should increment (as in #3181) so existing v53.0 MEMORY snapshots fall back to ROOTFS fidelity.
  • v54.0 disables virtio-net offloads (offload_csum, offload_tso, offload_ufo) by default on newly created VMs (cloud-hypervisor#9041); check whether ateworker-microvm wants the new default or explicit offloads.
  • v54.0 rejects OnDemand restore for VMs with vhost-user devices (cloud-hypervisor#9020). PrefaultsUnconditionally in cmd/ateworker-microvm/internal/ch/prefault.go already selects Copy (MemRestoreEager) for >= 53.0.0, so update its comment to note why vhost-user requires Copy.
Lingua principale
Go
Stelle
6.1k
Fork
676
Merge medio
2g 2h
PR unite (30g)
522

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di agent-substrate/substrate

Tutte le issue di agent-substrate/substrate

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.