10,939
edits
Changes
Jump to navigation
Jump to search
m
→Type 1 Hypervisors
With Windows host and "QEMU + WHPX" [https://www.youtube.com/watch?v=T43ni7mssww&lc=Ugw2qKkJVn3eSW7ZJ0p4AaABAg.9g4VM28d9_o9kUveV6vMMD it will be much slower performance wise compared to Linux host and QEMU + KVM]. You will have to stay with QEMU TCG entirely until you manually switched to 'ACPI PC' kernel. The starting 'ACPI Uniprocessor' kernel does not boot on QEMU WHPX.
QEMU VirGL '''only for Linux guests''' [https://wiki.archlinux.org/title/QEMU#virtio "with 4.4=> kernel with mesa (>=11.2) compiled with the option gallium-drivers=virgl"] at the moment. Plans are to target GL2.1 + GLSL 1.20 as the possible lowest GL interface to support. The guest would then expose the same level of GL. This project will [https://docs.mesa3d.org/drivers/virgl.html#future-scope eventually support Direct3D and Windows guest] but there is none at the moment. Currently the renderer is GLSL 1.30 based, and requires some extensions from later GL levels. Current developer only really tested on the open source nouveau driver exposing GL3.0/GL3.1 core profile, and the binary nvidia driver exposing GL 4.3. Future plans to add a capabilities system will be required to work make things work across more systems. The capabilities system will expose different guest GL levels dependant on the host GL level, this could allow for a GLES2 specific interface etc. The current guest driver exposes GL2.1 and GLSL 1.20. Also there is a [https://github.com/virtio-win/kvm-guest-drivers-windows/pull/943 pull request: Windows Virtio GPU 3D acceleration for QEMU]. For more information about VirGL3D [https://virgil3d.github.io/questions.html use this link].
[https://github.com/jamesstringerparsec/Easy-GPU-PV#prerequisites "Hyper-V + GPU-Passthrough" exclusive to Windows 10/11 host and guest systems at the moment]. So you don't have any option other than "QEMU-3dfx with WHPX" OR "Type 2 hypervisors" for current Windows hosts at the moment.
