I’ve already written a detailed tutorial on Windows 10 kvm VGA passthrough based on QEMU version 2.11. Years have passed and recent distributions like Ubuntu 20.04, Linux Mint 20, or Manjaro come with QEMU 4.0, 4.2 or 5.1.
A lot has happened since version 2.11. QEMU 4.0 includes numerous changes and improvements such as trim support in the virtio-blk driver, pcie-root-port with PCIe 4.0 support (with Q35-4.0 machine type), as well as improved audio.
It wasn’t easy this time. Don’t get me wrong – the VFIO passthrough part, though challenging in some ways, went quite well. All in all I’m pleased now with the results. Here the Passmark 9.0 benchmark as uploaded onto their database (for more details, click the frame below):
I’ve been contemplating a PC upgrade for more than a year (see my post here). At first I considered staying with Intel and getting an i9-9900K CPU with integrated GPU on a Z390 motherboard.
Along came the AMD Ryzen 9 3900X that topped the benchmarks, including the Adobe Lightroom and Photoshop benchmarks (to be precise, it ranked #4 in the Adobe Lightroom benchmark, and a narrow #1 in the Adobe Photoshop benchmark). These good news about the AMD Ryzen 3900X were soon followed by reports about BIOS issues and VFIO incompatibility. At the very least, it looked like VGA passthrough was more challenging.
More than a year has passed since I’ve posted about building a new PC. So what is holding me back from the upgrade? Time and money are considerations, but not the reason.
On paper, the AMD Ryzen 9 has outperformed Intel in most if not all tasks. The Ryzen 9 3900X beats the Intel i9 9900K as well as the Intel i9 10900X in multi-threaded workloads. The Intel i9 9900K can barely hold its ground on single-threaded tasks. Numerous benchmarks have shown that AMD is a clear winner. Continue reading “Hardware upgrade or what’s holding me back?”
A year ago I wrote about the 2D graphics performance impact of the Windows 10 (1803) update inside a virtual machine. As it turned out, the performance impact was related to the Spectre vulnerability patch that Microsoft had introduced. However, the same patch had practically no performance impact on a Windows 10 bare-metal installation.
Two years ago I wrote a post on S.M.A.R.T., an acronym for “Self-Monitoring, Analysis, and Reporting Technology”. In plain English, I’m talking about technology inside a hard drive or SSD that monitors and reports about the health of the drive. While S.M.A.R.T. can give us clues as to the state of the drive, it’s not always an exact science. Some indicators warrant an immediate drive replacement, others can indicate a higher probability of imminent failure. Continue reading “SSD and S.M.A.R.T.”
For some time I wanted to run a kvm virtual machine with GPU passthrough on a low-end Asus H110M-K D3 motherboard with an i3-6100 CPU and an Nvidia GTX 1060 GPU, but never found the time. Now I finally had a chance to give it a try. While the preparations were easy, I ran into a problem when starting the Windows 10 VM:
Update September 14, 2021: This is a complete revamp, adding new, more robust methods and dropping outdated ones.
When running a VM with GPU passthrough, that GPU should be bound to the VFIO driver. To make this happen, we need to prevent the regular graphics driver from binding to the passthrough GPU and instead bind the vfio-pci driver.
In the past we used to blacklist the graphics driver. This worked in most cases, but what if you need the graphics driver for another GPU, e.g. the host GPU?
Qemu/kvm provides you with a plethora of ways to configure your storage devices. Yet no other type of device shows such a variance in its performance, with disk I/O throughput anywhere from stellar to abysmal using the very same hardware.