This is a follow-up to Running Hyper-V in a QEMU/KVM Guest published earlier this year. The article provided instructions on setting up Hyper-V in a QEMU/KVM Windows guest as enabled by a particular KVM patchset (on Intel hardware only, as it turned out later). Several issues have been found since then; some already fixed, some in the process of being fixed, and some still not fully understood.
This post aims to be an up-to-date list of issues related to Hyper-V on KVM, showing their current status and, where applicable, upstream commit IDs. The issues are ordered chronologically from the oldest ones to those found recently.
|Issue description||Status||Public bug tracker|
|Hyper-V on KVM does not work at all (initial work item)||Fixed in kernel 4.10
|Hyper-V on KVM does not work on new Intel CPUs with PML||Fixed in kernel 4.11
|Hyper-V on KVM does not work on AMD CPUs||Fixed in kernel 4.12 for 1 vCPU
|rtl8139 and e1000 QEMU network cards don’t work with Hyper-V enabled||Not fixed yet||RHBZ 1452546|
|L2 Linux guest in Hyper-V on KVM hangs on boot||Fixed in kernel 4.13
|Windows TSC page does not work with Hyper-V enabled||Fixed in kernel 4.14
|Hyper-V on KVM does not work with OVMF (required for secure boot)||Not fixed yet||RHBZ 1488203|
|Not Hyper-V but prevents virtualization-based security from running||Not fixed yet||RHBZ 1496170