KVM on Windows #147
Unanswered
startergo
asked this question in
Questions and Support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Shocker KVM works on Windows!
There is a QEMU fork in combination with the AEHD driver, which is providing full CPU passthrough to QEMU on Windows.
The Device Guard and Credential Guard hardware readiness tool released by Microsoft can disable the Hyper-V Windows 10 features along with Hyper-V. You can either run WHPX or HAXM/EAHD, but not both:
HAXM/EAHDand enableWHPXyou have to run the tool in reverse order replacing-Disableswitch with-EnableThe catch:
Can't boot any macOS there. As soon as
AVX2is passed through, theSequoiapanics atcorecryptomodule.Tried booting Mojave with disabled
AVX2, but it panics too.The machines were built with
QuickemuonEndeavourosand they run fine there. See the issue here:MateuszKrawczuk/qemu#2
You can test it like this:
The
EFIfolder whereOpencorebootloader resides is nested like this in themacos-sonomafoldermacos-sonoma\EFI\EFI\boot\bootx64.efiCombine OVMF code and VARS files for Windows:
I can't understand what gives as I can boot
Endeavourosand I can verify that the CPU is passed through andAVX2is definitely there:Any ideas? Why can't I boot macOS, which boots fine in Linux with the same configuration?
Beta Was this translation helpful? Give feedback.
All reactions