0 Fork 0

Files

T

guofangandClaude Sonnet 5.5 c139c566d0 Use virtio-gpu with viogpudo on Arm64 Windows 11

Replace ramfb with virtio-gpu-pci at 2048x1280 and install the viogpudo
driver from the VirtIO ISO. ramfb has a fixed mode, and keeping both
adapters left Windows with a second, fixed-mode monitor.

Windows Setup and the base image have no viogpudo driver, so on the
launch that creates the system disk the launcher also adds a ramfb ahead
of the config files. The display window shows the first GPU.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-10-18 17:47:48 +08:00

almalinux10

Remove shell VM launchers in favor of the Python ones

2026-09-30 09:22:40 +08:00

debian13

Add a commented ibus-table-wubi package to the Debian seed user-data

2026-10-10 19:47:38 +08:00

fedora44

Remove shell VM launchers in favor of the Python ones

2026-09-30 09:22:40 +08:00

ubuntu2604

Add Ubuntu 26.04 virtual machine

2026-10-15 09:00:15 +08:00

windows11

Use virtio-gpu with viogpudo on Arm64 Windows 11

2026-10-18 17:47:48 +08:00

README.md

Add Ubuntu 26.04 virtual machine

2026-10-15 09:00:15 +08:00

README.md

Cloud-init seed images

Each operating system has an independent NoCloud configuration and generated seed.iso:

seediso/
├── debian13/
├── almalinux10/
├── fedora44/
└── ubuntu2604/

Keeping per-OS metadata separate allows each VM to use a distinct hostname and cloud-init instance-id. Generated ISO files are ignored by Git and are built automatically by the corresponding launcher when missing.