Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

runtime-adapter: a_clone_refuses_a_scratch_image_whose_upper_an_earlier_clone_used fails intermittently

Chiusa
  • Qualcosa non va?
#1,020 0 commenti 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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
linux, rust
Ambito
infrastructure, operating-systems

Direzione di ricerca

Start with tests/runtime-adapter/tests/vm_clone.rs, then trace graceful stop through nvx-rs/src/guest/root.rs and nvx-rs/src/guest/sys/port.rs. Check whether every stop path syncs or unmounts the scratch filesystem before power-off, including failures when another mount namespace holds the root. Done when graceful stop leaves a copied scratch image with its expected entries and the intermittent clone test passes.

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

Descrizione

a_clone_refuses_a_scratch_image_whose_upper_an_earlier_clone_used (tests/runtime-adapter/tests/vm_clone.rs) failed twice in CI on the Linux KVM runner (Guests and sandboxes), and passed on each rerun: run 40852461399 (attempt 1) and run 40943638955 (attempt 1). Both times the second start, over a copy of the earlier clone's scratch image, started (exit 0, sandbox=started) instead of ending with CLONE_FAILED (8) and unusable-root.

The guest's check_fresh (nvx-rs/src/guest/root.rs) accepts an upper whose upper and work directories are missing or empty. So the copy held none of the entries that the earlier clone wrote there: the overlay's work directory, and the file of the contents probe, which the test had checked reached the upper. Yet the test copied the image only after a stop that reported graceful, success 0 and complete.

Likely cause: the earlier clone's writes to the scratch's ext4 file system had not all reached the image when its VM powered off. ext4 commits its journal every 5 seconds by default, a clone reaches its probe and its stop within seconds, and the guest powers the VM off through the control port (power_off in nvx-rs/src/guest/sys/port.rs), which flushes nothing itself. To check:

  • whether the stop unmounts or syncs the scratch's file system before the power-off, on every path, and whether an unmount that fails (for example, while another mount namespace still holds the root) goes unreported;
  • if it does not, sync the scratch (syncfs) or unmount it before the power-off, so that a graceful stop leaves the scratch image complete. A scratch that is kept across boots needs the same.

Found in #957 (5102663a added the test), and seen again while validating stacked PRs on dev. Related to #833.

Lingua principale
Rust
Stelle
758
Fork
48
Merge medio
18h 27m
PR unite (30g)
446

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 microsoft/nvx

Tutte le issue di microsoft/nvx

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.