| ... | ... | @@ -7,7 +7,7 @@ preserving older bases. Host paths come from the configured VM library root. |
| 7 | 7 | |
| 8 | 8 | The provisioning contract is [windows-provision.ps1](../guest/windows-provision.ps1). |
| 9 | 9 | Prepare an isolated template with its account named `sandbox`, then run that |
| 10 | | script with `-Prepare` from elevated 64-bit Windows PowerShell. Preparation |
| 10 | script with `-Prepare` from 64-bit Windows PowerShell running as `SYSTEM`. Preparation |
| 11 | 11 | randomizes the template password, removes clone identity and completion state, |
| 12 | 12 | and installs the startup task. Shut down normally before capturing through |
| 13 | 13 | `vms.save_preset` with `setup=windows-v4`. The dashboard deliberately rejects |
| ... | ... | @@ -25,6 +25,18 @@ sign-out/sign-in so the desktop inherits the selected username, without a second |
| 25 | 25 | OS boot. Each clone still gets a separate password, MAC address, and DHCP lease. |
| 26 | 26 | Published `windows-v3` bases keep their original rename-and-reboot seed contract. |
| 27 | 27 | |
| 28 | ## Development image |
| 29 | |
| 30 | `windows-11-pro-development-v1` adds the C++ build tools and Windows SDK, Rust, |
| 31 | Node/pnpm, Python and Git. Its installed versions, installer hashes and recipe |
| 32 | hash are recorded in `C:\Snowglobe\development.json`. `computer_presets` exposes |
| 33 | the image's recommended resources; its memory and disk values are bytes. |
| 34 | |
| 35 | Run [windows-development.ps1](../guest/windows-development.ps1) from the elevated |
| 36 | desktop account before template preparation. The toolchains use machine-wide |
| 37 | paths and were verified with ordinary desktop privileges and fresh account names. |
| 38 | The development image is a separate family; clean Windows images keep their IDs. |
| 39 | |
| 28 | 40 | ## 2026-10-20 rollout |
| 29 | 41 | |
| 30 | 42 | The `windows-10-pro-v10` candidate was prepared and tested on HDD storage with |
| ... | ... | @@ -72,10 +84,8 @@ identity changes at 1.83 seconds; the host's polling rounds this to 2.08 seconds |
| 72 | 84 | Two Kernel-General boot events confirmed the reboot. Explorer and guest capture |
| 73 | 85 | were running, and the production browser displayed the personalized desktop. |
| 74 | 86 | |
| 75 | | This is a disk template, not a saved-memory resume. `Rename-Computer` in the |
| 76 | | provisioning script is followed by a forced restart; the second boot enables |
| 77 | | capture and waits for the desktop. Avoiding that second boot is the next |
| 78 | | architectural opportunity. Cloning the disk itself is already inexpensive. |
| 87 | The v10 trace used a disk template with `Rename-Computer` and a restart before |
| 88 | desktop capture. Cloning the disk itself was already inexpensive. |
| 79 | 89 | |
| 80 | 90 | By `ready`, QEMU recorded 474 flushes with 46.45 seconds of aggregate duration |
| 81 | 91 | (98 ms per flush), 2.24 GB read, and 105 MB written. These operation durations |