Skip to content

Add Windows snapshots and forks - #433

Draft
sjmiller609 wants to merge 4 commits into
hypeship/windows-networkingfrom
hypeship/windows-snapshots
Draft

Add Windows snapshots and forks#433
sjmiller609 wants to merge 4 commits into
hypeship/windows-networkingfrom
hypeship/windows-snapshots

Conversation

@sjmiller609

@sjmiller609 sjmiller609 commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

summary

  • enable Windows standby, restore, stopped snapshots, and forks
  • preserve disk, Secure Boot NVRAM, TPM state, and QEMU configuration for same-instance restores
  • assign fork identity according to memory-restore versus cold-boot semantics
  • require forkable Windows images to declare bitlocker=disabled
  • guard captured VioSock CIDs and rotate them on cold starts
  • reduce final Windows KVM coverage to one comprehensive guest/network/standby/memory-fork lifecycle scenario plus one stopped-fork scenario
  • document snapshot identity, TPM, VioSock, and BitLocker decisions in the instance README

targeted tests

  • Windows image-policy, fork-identity, and hypervisor-config unit tests
  • final lifecycle and stopped-fork integration test compilation/skip paths

Long-running KVM and full CI suites were not run for this review pass.

@sjmiller609
sjmiller609 force-pushed the hypeship/windows-snapshots branch 3 times, most recently from ddd1d35 to 7886185 Compare August 20, 2026 14:14
@sjmiller609
sjmiller609 force-pushed the hypeship/windows-snapshots branch from 7886185 to 2723b54 Compare August 20, 2026 19:26
@sjmiller609
sjmiller609 force-pushed the hypeship/windows-snapshots branch from 2723b54 to 19ab53d Compare August 20, 2026 20:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant