If running on KVM/Proxmox, install the guest agent from the VirtIO ISO to enable clean shutdowns and memory ballooning from the host.
Security & maintenance recommendations
Windows 7 与最新版 VirtIO 驱动存在兼容性问题。解决方案是使用 v0.1.173-4 版本的 VirtIO 驱动，并在安装过程中禁用 SPICE Agent 服务。
Walk through the standard Windows 7 graphical installation. windows 7 qcow2 image install download
Why 40GB? Windows 7 with updates and a few apps can easily exceed the official 16GB minimum. Sparse allocation means it uses only real space as needed.
Although Microsoft ended support for Windows 7 in 2020, it remains a heavily used operating system for legacy software, network testing, and specialized IT environments. For users running KVM, QEMU, Proxmox, or EVE-NG, utilizing a qcow2 (QEMU Copy On Write) image is the most efficient way to deploy this operating system.
Test the converted image by booting it with QEMU. You may need to install VirtIO drivers after the first boot if the original VM used different virtual hardware. If running on KVM/Proxmox, install the guest agent
Use SFTP (like WinSCP) to transfer the file to your host (e.g., /opt/eve-ng/qemu/win7-xxxx/ if using EVE-NG).
Windows 7, despite reaching its end of support in 2020, remains a vital operating system for running legacy applications, testing, and supporting older hardware. When utilizing virtualization technologies like KVM (Kernel-based Virtual Machine) or QEMU, the (QEMU Copy On Write) format is the preferred, flexible, and efficient disk image format.
The safest route is to start from a Microsoft-distributed ISO: Windows 7 with updates and a few apps
Set the to VirtIO in your virtual machine manager. Set the Network Adapter to VirtIO/virtio-net-pci.
For production legacy needs, consider upgrading to Windows 10 LTSC or Windows 11 with compatibility layers. For retro computing, enjoy your isolated Windows 7 VM.
The file size expands only when data is added inside the VM.
| Issue | Likely Cause | Solution | |-------|--------------|----------| | “No disk found” during install | Windows 7 lacks VirtIO drivers | Load the disk driver from the VirtIO ISO during the “Load driver” step | | Very slow performance, high CPU usage | QEMU is emulating without KVM | Verify that KVM is loaded ( lsmod | grep kvm ) and add -enable-kvm to your QEMU command | | Network does not work after boot | Missing VirtIO network driver | Install the NETKVM driver from the VirtIO ISO; if already installed, check that the NIC model is virtio | | QXL/SPICE features not working (no clipboard sharing) | SPICE agent not installed or outdated | Inside the Windows 7 VM, run the VirtIO installer and explicitly install the SPICE guest tools. For Windows 7, you may need an older version (v0.1.173‑4 or earlier) | | 64‑bit Windows 7 is extremely slow even with KVM | Not enough RAM or CPU cores | Increase memory to at least 4 GB and assign 2–4 cores; also disable Aero effects (right‑click desktop → Personalize → Windows Classic theme) | | Activation fails after converting a physical PC | Hardware signature changed | You may need to perform telephone activation. Prepare your product key and call the Microsoft activation hotline |
virt-install --connect qemu:///system \ --name win7-vm --ram 4096 --vcpus 2 \ --disk path=/path/to/windows7.qcow2,format=qcow2,bus=virtio \ --cdrom /path/to/windows7.iso \ --disk path=/path/to/virtio-win.iso,device=cdrom \ --network network=default,model=virtio \ --vnc --os-type windows --os-variant win7 Use code with caution.