Boot from an ISO file and install to the QCOW2 image.
qemu-system-x86_64 \
-enable-kvm \
-cpu host \
-smp 4 \
-m 4096 \
-drive file=win8.qcow2,format=qcow2,if=virtio \
-drive file=Win8_ISO.iso,media=cdrom \
-drive file=virtio-win.iso,media=cdrom \
-netdev user,id=net0 \
-device virtio-net-pci,netdev=net0 \
-vga qxl \
-display spice-app
Note: Windows 8 requires the VirtIO drivers (disk and network) during installation. Attach
virtio-win.isoand load the driver when the installer asks for a disk.
There is a darker, more practical reason for the persistence of the Windows 8 QCOW2 image: Malware analysis.
Because Windows 8 is an end-of-life (EOL) operating system, it is unpatched. It is full of security holes that have been fixed in Windows 10 and 11. This makes it the perfect "honeypot" for security researchers.
A researcher can spin up a Windows 8 QCOW2 instance, infect it with a virus, observe the behavior, and then—crucially—delete the entire QCOW2 file. The infection never touches the host machine windows 8 qcow2
Windows 8 QCOW2 images are virtual disk files that combine the legacy Windows 8 operating system with the advanced storage capabilities of the QEMU Copy-On-Write (QCOW) format. This combination is primarily used in enterprise virtualization environments like OpenStack and Proxmox to run legacy applications while maintaining modern storage efficiency. Core Storage Features
Dynamic Allocation: Unlike "raw" images that occupy their full size immediately, a Windows 8 QCOW2 file starts small and grows only as data is written by the guest OS.
Copy-On-Write (CoW): This allows for "linked clones," where multiple Windows 8 virtual machines (VMs) share a single read-only base image. Changes are stored in a separate layer, significantly saving disk space.
Snapshots: Windows 8 QCOW2 images support internal snapshots, allowing you to capture the system state before major updates or software installs and revert easily if issues occur. Boot from an ISO file and install to the QCOW2 image
Compression & Encryption: Data can be stored in a compressed format to further reduce footprint, and the format supports AES encryption to protect the virtual disk. Technical Capabilities Building Windows Cloud Images on OpenMetal
For users of KVM, Proxmox, or QEMU, the Windows 8 QCOW2 combination offers a powerful, snapshot-friendly, and storage-efficient virtualization solution. By utilizing the dynamic allocation features of QCOW2 and pairing them with VirtIO drivers, administrators can ensure that the legacy Windows 8 environment runs smoothly on modern Linux hypervisors.
Have you successfully deployed a Windows 8 QCOW2 image in production? Share your performance benchmarks in the comments below.
Windows 8 QCOW2 images remain valuable for legacy application support, testing, and archival use. However, they require deliberate handling: ensure licensing compliance, use VirtIO drivers for acceptable performance, harden and isolate the guest due to limited support, and follow disciplined image creation and snapshot practices. For production or performance-sensitive use, evaluate whether upgrading to a supported Windows release or moving workloads to containerized or cloud-native alternatives is feasible; when migration isn’t possible, rigorous operational controls around QCOW2-based Windows 8 VMs will mitigate most risks. Note: Windows 8 requires the VirtIO drivers (disk
The Retro-Modern Lab: Windows 8 & the Power of QCOW2 Windows 8—with its bold (and polarizing) tiles—is now a curious piece of tech history. But for enthusiasts and developers, it remains a fast, lightweight OS perfect for testing legacy software in a virtual environment. If you’re running it on a Linux-based hypervisor like KVM/QEMU, the QCOW2 (QEMU Copy-On-Write) disk format is your best friend.
Here’s why Windows 8 and QCOW2 are a "power couple" for your homelab or dev environment. 1. Why QCOW2 for Windows 8?
While "raw" disk images offer slightly better absolute performance, QCOW2 brings high-end features that make managing an older OS like Windows 8 much easier:
Windows 8 is snappy, but a misconfigured QCOW2 image can be sluggish. Here is how to optimize.
| |||||||||||