autounattend: use ForceShutdownNow instead of FirstLogonCommands shutdown
I'm not running any custom qemu. I think the build process just picks pkgs.qemu
, or not? Is it the fact that I am running the build in a pure server environment? (GitLab pipeline, Hydra)
autounattend: use ForceShutdownNow instead of FirstLogonCommands shutdown
Unfortunately, due to the change in ec54c9bf9b
, our pipeline fails to run on this:
qemu-system-x86_64: QXL VGA not available
Support for larger install.wim, legacy boot, image selection
Thanks for your speedy feedback! I've made some changes, let me know if there is anything else I should address.
Given that I had some trouble with the driveLetter, it would be best if you could…
f1b52c0da7
autounattend: Revert back to driveLetter D
0becb115f6
win: Use maximum size to split install.wim
84ef1ec7e5
win: cdimage naming, closure shrinking
Support for larger install.wim, legacy boot, image selection
Seems like the drive letters are not the same for legacy and efi, that might be worth a second set of eyes.
1357f493bd
Add support for legacy installations
7da6dfb75d
Add support for legacy installations
Support for larger install.wim, legacy boot, image selection
I'm seeing some failed automated tests in our local systems, I need to have another look.
OpenSSH server component not installing on Windows 10H2
7da6dfb75d
Add support for legacy installations
e8232ab89a
win: Allow for selection specific image
90cc7b14a4
Use q35 and xHCI for more performance
fbd5b97d79
Split install.wim before creating USB image
bc8495789f
Add support for legacy installations
Support for larger install.wim, legacy boot, image selection
bc8495789f
Add support for legacy installations
ea2a1c45ad
win: Allow for selection specific image
b310dfe8e3
Use q35 and xHCI for more performance
2eb4a9aa48
Split install.wim before creating USB image