Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 10 additions & 3 deletions doc/design/5.5-restore-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,13 @@ In the worker, with every processor stopped, restore:
[rate policy](3.2-clock-and-time.md#324-rates).
14. Restores every state unit while stopped: VM time, chipset and virtio
devices, the time platform, the partition, and every processor, with its
LAPIC timer stopped.
LAPIC timer stopped. A device's restore validates its saved state and
reacquires the host resources that the state refers to, such as the host
files that a virtio-fs device holds open, so a device that cannot restore
fails the restore here. A virtio device's restore starts no queue and
drives no interrupt line: the line of a microVM's virtio devices pulses
only as a device raises its interrupt status, and the pulse for a restored
status was sent before the capture.
15. Freezes the set of instantiated processors.
16. Takes the restore anchor, computes `D`, and writes the same target to
every instantiated processor's TSC at one host instant, never applying
Expand Down Expand Up @@ -135,8 +141,9 @@ with their policies. It may add processor and RAM targets, a gate timeout, a
readiness endpoint, a scratch device or its absence, a storage generation, a
filesystem on the slot that the snapshot left dormant, a local listener on a
disconnected boot console, and a network policy in place of a template's
deny-all. The restored VM stays paused until the client resumes it. That
resume starts the state units and publishes the readiness event as step 20
deny-all. The restored VM stays paused until the client resumes it, and a
device that cannot restore fails the request itself, as step 14 describes.
That resume starts the state units and publishes the readiness event as step 20
describes. A device that fails to start fails the resume and leaves the VM
paused, unless the request added a readiness endpoint: a resume that then
fails for any reason, a failed publication included, tears the VM down.
Expand Down
Loading
Loading