| ... | @@ -0,0 +1,50 @@ |
| 1 | # Windows presets |
| 2 | |
| 3 | Prepared images live in the VM library's `Presets` directory. Each published |
| 4 | directory is immutable: existing guests retain QCOW2 backing-file references |
| 5 | to it. Publish a new ID with `supersedes` to change the library default while |
| 6 | preserving older bases. Host paths come from the configured VM library root. |
| 7 | |
| 8 | The provisioning contract is [windows-provision.ps1](../guest/windows-provision.ps1). |
| 9 | Prepare an isolated template with its account named `sandbox`, then run that |
| 10 | script with `-Prepare` from elevated 64-bit Windows PowerShell. Preparation |
| 11 | randomizes the template password, removes clone identity and completion state, |
| 12 | and installs the startup task. Shut down normally before capturing through |
| 13 | `vms.save_preset` with `setup=windows-v3`. The dashboard deliberately rejects |
| 14 | ordinary Windows preset capture because it cannot establish preparation. |
| 15 | |
| 16 | Validate fresh clones with different account names before publication. Check |
| 17 | the personalized account and computer name, the `ready` marker, Explorer, |
| 18 | the guest capture process, and the actual dashboard screen and input. Compare |
| 19 | the published disk and NVRAM bytes with the tested candidate, and check that |
| 20 | the disk is standalone with `qemu-img info` and `qemu-img check`. Never replace |
| 21 | an existing base in place. |
| 22 | |
| 23 | ## 2026-10-20 rollout |
| 24 | |
| 25 | The `windows-10-pro-v10` candidate was prepared and tested on HDD storage with |
| 26 | four vCPUs, 4 GiB RAM, and a 64 GiB disk. Both its base and each clone's writable |
| 27 | overlay stayed on HDD. The host's 150 GiB SSD read cache remained enabled. |
| 28 | |
| 29 | Preparation refreshed the 64-bit .NET Framework native-image cache with |
| 30 | `ngen update /force` and installed native images for the assemblies loaded by |
| 31 | Windows PowerShell, then reran the normal `-Prepare` flow. All assembly-install |
| 32 | commands and preparation completed successfully. See Microsoft's |
| 33 | [Ngen documentation](https://learn.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator) |
| 34 | for regeneration after framework servicing. No global CLR switches were added. |
| 35 | |
| 36 | | Candidate | Fresh clone to ready | Account | |
| 37 | | --- | ---: | --- | |
| 38 | | v9 repeat | 455 s | fixture | |
| 39 | | v10 first | 206 s | fixture | |
| 40 | | v10 repeat | 161 s | fixture2 | |
| 41 | |
| 42 | Both v10 clones completed personalization and reboot, started Explorer and the |
| 43 | guest capture process, and received distinct computer names. These are rollout |
| 44 | observations with differing cache warmth, not a controlled measurement of |
| 45 | L2ARC's contribution. Synchronous writes still reach HDDs. |
| 46 | |
| 47 | The published v10 preset supersedes v4. v4 and earlier referenced bases remain |
| 48 | available to their existing guests. Reverting the default requires withdrawing |
| 49 | v10 from discovery while preserving its bytes wherever clones still reference |
| 50 | them; it does not require modifying existing guest disks. |