After installation, you can run to "generalize" the image if you plan to use it as a template for multiple virtual machines. Run C:\Windows\System32\Sysprep\sysprep.exe .
By default, QEMU emulates a generic virtual CPU. Change this to in your processor configurations. This allows the Windows 10 guest to directly access your physical CPU instruction sets (such as AVX, AES-NI, and virtualization extensions), drastically boosting performance for compiling code, encoding video, or gaming. Managing QCOW2 Images via Command Line
Start the VM and follow the Windows prompts until you reach . windows 10qcow2
What kind of are you using? (NVMe SSD, SATA SSD, or mechanical HDD?)
You can create a "base" Windows 10 qcow2 image (fully activated and updated) and then create dozens of "overlay" images for individual users or tests. Each overlay is just a few MB initially and only stores differences. This is a game-changer for labs. After installation, you can run to "generalize" the
qemu-img convert -O qcow2 windows10.qcow2 compact-windows10.qcow2 Use code with caution. Conclusion
Before we begin, make sure you have:
Locate the storage driver directory: viostor -> w10 -> amd64 .
The drive list will appear completely blank because Windows cannot see the VirtIO virtual hard drive. Click →right arrow Browse . Change this to in your processor configurations
Once Windows 10 boots to the desktop, open the VirtIO CD-ROM inside File Explorer. Run the virtio-win-gt-x64.msi installer. This installer deploys all remaining paravirtualized drivers, including: : Paravirtualized network driver for low latency.