Support arm64 hosts in the Windows 11 launcher
Pick qemu-system-aarch64, the AArch64 UEFI firmware and a per-architecture QEMU config (NVMe disk, virtio-net, ramfb, USB installation media) on arm64, render the answer file for the target architecture, and move the q35-only disk and NIC devices out of the shared config. Update vm-images to match arm64 Windows ISO names. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5feed51c61
commit
c13ebc7d11
6 files changed
+124
-49
No files matched your search
@@ -0,0 +1,27 @@
|
||||
# arm64 part of the Windows 11 QEMU configuration; read after windows11.ini.
|
||||
|
||||
[machine]
|
||||
type = "virt"
|
||||
|
||||
# The "virt" machine has no IDE. NVMe and USB mass storage (used by the
|
||||
# installation media of --install-from-iso) both have inbox Windows drivers.
|
||||
[device "system_disk-dev"]
|
||||
driver = "nvme"
|
||||
drive = "system_disk"
|
||||
serial = "win11disk"
|
||||
bootindex = "1"
|
||||
|
||||
# Windows has no inbox driver for virtio-net; the guest tools installed by
|
||||
# Configure-Windows.ps1 provide it.
|
||||
[device "nic0"]
|
||||
driver = "virtio-net-pci"
|
||||
netdev = "net0"
|
||||
|
||||
# Unlike q35, "virt" has no default GPU or keyboard. ramfb is used rather than
|
||||
# virtio-gpu because the firmware's virtio-gpu output freezes at the Windows
|
||||
# boot manager; Windows drives either one through its basic display driver.
|
||||
[device "gpu0"]
|
||||
driver = "ramfb"
|
||||
|
||||
[device "kbd0"]
|
||||
driver = "usb-kbd"
|
||||
Reference in new issue
Block a user