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 7ca29de213 ee146c1c10 9ed38ffad4 1dc35dacc1 |
RHBZ 1326138 |
| Hyper-V on KVM does not work on new Intel CPUs with PML | Fixed in kernel 4.11 ab007cc94f 1fb883bb82 |
RHBZ 1440022 |
| Hyper-V on KVM does not work on AMD CPUs | Fixed in kernel 4.12 for 1 vCPU 405a353a0e and in kernel 4.13 for >1 vCPU |
RHBZ 1440025 |
| 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 2cf0284223 71c2a2d0a8 |
RHBZ 1457866 |
| Windows TSC page does not work with Hyper-V enabled | Fixed in kernel 4.14 72c139bacf and in QEMU 2.11 |
RHBZ 1464412 |
| Hyper-V on KVM does not work with OVMF (required for secure boot) | Fixed in kernel 4.15 0234bf8852 72d7b374b1 21f2d55118 72e9cbdb43 c26340651b 05cade71cf cc3d967f7e |
RHBZ 1488203 |
| Not Hyper-V but prevents virtualization-based security from running | 00663d047f 03877377e3 f130428043 e3531164cc 7516532f9c fda8f631ed |
RHBZ 1496170 TianocoreBZ 727 |
One thought on “Nesting Hyper-V in QEMU/KVM: Known issues”